Ask the Expert

Workflow event linkage becomes "deactivated"

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?"

    Requires Free Membership to View

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
The reason the linkage is deactivated is usually (but not always) due to some sort of binding issues (mandatory importing parameters of the workflow not being populated). The workflow event linkage is deactivated to prevent further errors occurring.

I would focus on why the event linkage is being deactivated.

This was first published in July 2004

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: