Workflow not active in test environment

[#1]

Hi All,

I developed a Workflow but it doesn't activate in the test environment. I executed the SWU_OBUF and SCC1 transaction even so the Workflow does not activate. Can someone help me?

Dev Environment

Test Environment

[Dominik_Tylczynski · Accepted solution]

Hello clima

You may want to check out the notes on event linkage transportation first e.g.

908414 - Incoherent behavior regarding transport of event linkage

885812 - Event linkages are not activated after transport

They are already quite old, so most probably they are not relevant anymore to your system. Just wanted to be sure.

Then, you need to realize that workflow definition and event linkage are development objects. Whereas event linkage activation is a customizing setting. As such they are assigned to two different transport requests - a workbench request and customizing one. You should see the pop up requesting a transport request while activating the event linkage in the DEV environment. So while moving the workflow to the TEST box, you need to import both requests - first the workbench one (with workflow definition and event linkage), then the customizing one (with even linkage activation). To me, it looks like you haven't transported the customizing settings of event linkage activation to the TEST environment.

What I like to do when developing workflows is to put all the settings into one transport requests, so the event linkage activation piece is not left out. You can merge customizing request with a workbench one in SE09, menu Utilities -> Reorganize -> Customizing Request -> Append to Workbench Request.

Best regards

Dominik Tylczynski

[former_member231406 · Accepted solution]

Hi Dominik,

Thanks for the answer. There is no need for transport for this test environment.

[Dominik_Tylczynski · Accepted solution]

clima

I didn't quite get your comment. You said in your original question that you transported the workflow with SSC1. So you need to transport the same way event linkage activation.

[former_member231406 · Accepted solution]

Resolved, there was an inactivation of an object in the request.

Thanks.