SAP Workflow is a tool to automate complex business processes where there is more than one user involved.SAP Business Workflow enables the design and execution of business processes within SAP application systems: Workflow processes are delivered as content in the SAP Business Suite. Additionally, customers can not only enhance those workflows provided by SAP, but they can also create their own workflows.
Workflow is not getting triggered even when the event is triggered and event linkage is active after system refresh. The event is successfully triggered by the transaction but the workflow hasn’t started.
We had switched on the event trace in Transaction SWELS to check for the event . The following screenshot, it is evident that the event is triggered and the receiver workflow is correctly identified.
Now select the event and click on detail (magnifying glass).
From the screenshot above , it is clear that the error is “Password logon no longer possible – too many failed attempts”. This looks like the issue is with RFC Status. We need to verify the RFC destination status in the workflow configuration in Transaction SWU3 – Automatic workflow customization
From the above screenshot, it is clear that RFC destination is broken. This might be for the following reasons: Someone has changed the password of WF-BATCH or WF-BATCH might have been locked or deleted.
The process of Synchronize the password in the Workflow customization. – SWU3.
Click on ‘Execute’.
If this process doesn’twork, check if the user WF-BATCH is either locked or deleted.
If the issue still occures even after following the above two process, please delete the rfc WORKFLOW_LOCAL_XXX and recreate it. This will fix the issue.