SAP Knowledge Base Article - Preview

3227538 - Workflow background steps are not getting completed after system copy

Symptom

  • The background workflow step stays 'In process' status even though the tRFC appears to have been executed successfully
  • The user SAP_WFRT is not getting called to process the step, the processing happens under the user that started the workflow
  • There is no tRFC error 
  • There is no short dump in ST22
  • The Top level work item is not available in SWPC 
  • MDG Change Request submitted but no workflow started. In SM58, LUWs with error "The ASSERT condition was violated" can be found for workflow RFC destination.


Read more...

Environment

  • SAP Business Workflow
  • SAP NetWeaver
  • SAP Web Application Server for SAP S/4 HANA
  • ABAP PLATFORM - Application Server ABAP

Product

ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions

Keywords

WF_GDPR, SWF_WORKFLOW, WFMSTD, Message server, application server, SWU3, Reference, WORKFLOW_REFERENCE_XXX, WORKFLOW_EVENT_XXX, WORKFLOW_LOCAL_XXX, WORKFLOW_LOCAL_, WORKFLOW_REFERENCE_, WORKFLOW_EVENT_, Event, Local, RFC Destination, Automatic, Auto, Customizing, Flag, Green, Red, The ASSERT condition was violated , KBA , BC-BMT-WFM-RUN , Runtime , BC-MID-RFC , RFC , BC-MID-RFC-QT , Queued RFC (qRFC) and transactional RFC (tRFC) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.