Workflow Deactivating

[Former Member]

Hi Experts,

We upgraded SAP system recently from 5.0 to 6.0. We are using standard PO workflow WS20000075. It is always deactivating. I have gone through SCN but unable to find a solution for this.

my observations are

1. There is no wrong in passing mandatory parameters in binding.

2. Too many workflows are not triggering in the same time.

I have found one difference in tcode SWE2 when comparing the new system (6.0) with old system(5.0)

In new system, "Event Delivery" is mentioned as "using tRFC (default)", there is no "Event Delivery" option in old system.

Please find the attached screen shots and help me.

Regards,

Murali.

[anjan_paul · Accepted solution]

Hi,

   Also check your SWU3 configuration done properly. share screenshot.

After that you check in SWEL, the trrigein event is trigger or not after PO created. And also check Release strategy are same or not

[Former Member · Accepted solution]

Hi Anjan,

Please find SWU3 screen shot and it is same as my old system.

[anjan_paul · Accepted solution]

Hi,

  ok check your release strategy is this define properly. Also take trace in SWEL share screenshot.

[Former Member · Accepted solution]

Anjan,

Release strategy configurations are correct,there is no problem in that.

In SWEL, message showing "any obligatory elements missing", but compared with old system workflow there is no changes in Binding in new system workflow.

Message was edited by: MURALI KRISHNA

[Former Member · Accepted solution]

Hi Murali,

Check Event to Workflow binding in Workflow Header.

Check syntax check in Binding.

Regards,

Ragav

[Former Member · Accepted solution]

Hi Raghav,

Event to workflow binding and syntax check doesn't have any errors.

Regards,

Murali.

[anjan_paul · Accepted solution]

Also check with MM consultant about the release strategy

[Former Member · Accepted solution]

Anjan,

I checked Release strategies with MM consultant also... everything is fine there like my old system.

Thanks

Regards,

Murali.

[former_member16044 · Accepted solution]

Hi,

Can you attach the event to workflow binding?

And also,in config, the workflow option should be '1' for the this case.

Regards,

Rahul

[Former Member]

Thank you all.

we found that The event linkage is activated in SWEC and in SWE2 transactions, so it is going to error.

Regards,

Murali

[Former Member]

Hi Murali,

1. Check workflow basic config in SWU3.
2. In the same event linkage screen in bottom down

          Behavior upon error feedback : Give DO not change linkage

Regards,

Ragav

[Former Member]

Thanks Raghav,

But, in the old system, Behaviour upon error feedback is "system defaults" and it is  same for both systems.

So, any other solutions ?.

Thank you.

Regards,

Murali.

[Former Member]

Hi,

You didn't reply for my first point.

Check Release strategy functional config done or not.Particularly agent assignment against Release code.

Regards,

Ragav

[Former Member]

Hello Raghav,

I attached SWU3 screen shot in the below post and Release strategy configurations are done properly .

Agent assignment against release code is also the same as in old system,,,

Thank you.

Regards,

Murali.

[suresh_subramanian2]

Hello Murali !

          You mentioned as follows:

But, in the old system, Behaviour upon error feedback is "system defaults" and it is  same for both systems. 

          As far workflows are concerned, system default settings should be overriden, atleast now in your case. Change the above default setting as "Do not change linkage" in SWE2 or SWETYPV and SWEQADM transaction(Basic data tab - under "Receiver error feedback).

       For more details, please refer vanilla is a nasty flavour.

       In addition, for the problem you face, test your workflow from SWUE. If it works fine, check any change document configuration is missing.Because the mandatory parameter release code is not passed.

Regards,

S.Suresh.