The workflow event linkage from an IDoc inbound error to the custom workflow mysteriously becomes "deactivated" in production. We have to then force a transport to reactivate the linkage. How can we determine the root cause of the linkage breakdown, and how can we prevent future "deactivations?"
I would check which user is set up as the Workflow Administrator. What happens is when an event linkage is deactivated an e-mail is sent to the Workflow Administrator notifying him/her of the error including the reason for the deactivation. To see who the current Admin is you can execute transaction SWDC.
To prevent future deactivations you can
- Execute transaction SWE2
- Find the event linkage that is being deactivated
- Change the value of the field Behavior upon error feedback and set it to Do Not Change Linkage
- Transport this change to the target environment
I would focus on why the event linkage is being deactivated.
Dig Deeper on SAP workflow development
Related Q&A from Alon Raskin
Find out how to configure clients so that the same version of an SAP workflow item is used when the workflow is triggered in separate clients. Continue Reading
An SAP user has created a user decision step in an SAP workflow item and wants to know how an end user can send an attachment to other users. Continue Reading
A SearchSAP.com reader wants to know how to hide the forward button in an SAP Business Workplace toolbar. Continue Reading