cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with workflow Task00008075

Former Member
0 Kudos

Hi Team,


We recently had SPS upgrade in the production box. After SPS upgrade , we found there are two workflows getting generated when the order response comes to system. One workflow is the correct one which contains the Purchase order number and other one is the incorrect one which contains the idoc number in the work item text. Only one workflow should get triggered which contains the Purchase order number in the work item text.

I have checked the settings in SWE2 and also tried trace option but no luck.

Is there any other way to check why two workflows are getting triggered ? (May be some configuration or other setting in SPRO)

Thanks,

Chetan Taori

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member186746
Active Contributor
0 Kudos

Hi,

You should check transaction WE46 and WE47 most likely they are triggerd from settings in these transactions.

If you don't need them, you could also disable the starting event of this task, or put a condition on it.

Kind regards, Rob Dielemans

anjan_paul
Active Contributor
0 Kudos

Hi,

First check the triggerin event of the wrong workflow.

Also check any change document configure in SWEC for any Business object IDOC, which may used in the workflow.

Former Member
0 Kudos

Hi Suresh,

i checked both the workflows the correct one and the incorrect one. Both are generated with task instance ts00008075 ans same event INPUTERROROCCURRED. Both the workflows are generated at the same time.

Hi Jocelyn,

I checked the tcode for process code ORDR. Do you want me to check any specific setting over there?

Thanks,

Chetan T

suresh_subramanian2
Active Contributor
0 Kudos

Hello Chetan !

          What is the event that triggers the IDOC as you see in SWEL transaction ? Is it INPUTERROROCCURRED ?

          Have a look at the triggering tab of the task TS00008075.

          Is that event INPUTERROROCCURRED that triggered is seen in triggering tab ? If so, just undo the binding i.e., uncheck the check box under binding column for the event INPUTERROROCCURRED and save it.

         That's it ! No more instances for the event INPUTERROROCCURRED would be created.

Regards,

S.Suresh.

Jocelyn_Dart
Product and Topic Expert
Product and Topic Expert
0 Kudos

Yes but Suresh that would stop all of those tasks which may not be what Chetan intended? Unless you can live with that Chetan? Lots of sites have IDOC workflow tasks turned on and never actually use them

Chetan  if its starting with an event, you should be able to see some info in the event log and or event browser (in SWEQADM) if you have those turned on. The Event Browser should at least let you see if there is any difference in the event container content when the event is triggered.

But I defer to those with greater IDOC knowledge that WE46/47 and SWEC would also be worth checking. BTW - just check if there is more than ORDR that may be triggering ORDRSP - e.g. ORDR_SUS ?

Jocelyn_Dart
Product and Topic Expert
Product and Topic Expert
0 Kudos

Yes but Suresh that would stop all of those tasks which may not be what Chetan intended? Unless you can live with that Chetan? Lots of sites have IDOC workflow tasks turned on and never actually use them

Chetan  if its starting with an event, you should be able to see some info in the event log and or event browser (in SWEQADM) if you have those turned on. The Event Browser should at least let you see if there is any difference in the event container content when the event is triggered.

But I defer to those with greater IDOC knowledge that WE46/47 and SWEC would also be worth checking. BTW - just check if there is more than ORDR that may be triggering ORDRSP - e.g. ORDR_SUS ?

suresh_subramanian2
Active Contributor
0 Kudos

Hello Jocelyn !

          You've stated that unbinding the event at triggering event tab for the task TS0008075 will stop all those tasks.

          But, in my understanding, unbinding the event at task TS00008075, will affect only this task and not all tasks where this event is used. May be I could have misunderstood your suggestion.

          Please have your say, if my understanding is incorrect.

Regards,

S.Suresh.

Jocelyn_Dart
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Suresh, Yes thanks for correcting me.  Of course I mean stop all work items based on task TS00008075.  The question is whether you want to stop the work items entirely (in which case unbinding would be appropriate) or just stop the duplicates (in which case further investigation of the source of the events is needed).

Clearer?

Regards,

Jocelyn

suresh_subramanian2
Active Contributor
0 Kudos

Hello Jocelyn !

             Thank you so much for the reply. It's clear now.

Regards,

S.Suresh.

suresh_subramanian2
Active Contributor
0 Kudos

Hello Chetan !

           Is the workflow log shows that one instance of TS00008075 generates purchase order number and the other instance generates IDoc number ?

           Please verify which task number in workflow log has generated the purchase order number and IDoc number.

Regards,

S.Suresh.

Jocelyn_Dart
Product and Topic Expert
Product and Topic Expert
0 Kudos

Try the IDOC configuration... they tend to trigger standalone tasks directly

Think its buried somewhere in transaction WE42 - you'll need to know the relevant inbound process code.