A WF after completion triggers the same WF

[former_member184495]

Hi,

strange requirement but need to solve it.

PO created, 2 levels of approval. 1st approver approved, 2nd approver rejects, WF completed.

Now since Rel code is reset while rejecting, this in turn triggers RELEASESTEPCREATED again and triggers WF and sends workitem to 1st approver again which is not required.

I feel its at Release Strategy that this could be maintained.

How to solve this issue, thru any terminating events, change documents or anything else?

Thanks,

Aditya V

[former_member186746]

Hi,

why would you reset the release codes when rejecting, this is causing the problem? Normally PO is rejected, user changes the PO significantly, which will reset the release codes and this retriggers the approval flow again.

Kind regards, Rob Dielemans

[former_member184495]

Hi RD,

thanks for response.

and thats how the requirement is.. 🙂 as there are other intricacies too as user-exit is managing the whole RS.

however I feel it has to be handled in the user-exit.

Aditya V

[former_member186746]

Hi,

I still have difficulties in understanding the requirements. Why does resetting the release codes after a rejection add a benefit to the Purchase Order data?

If this is the case and you don't want to retrigger the PO then you need to prevent the approval flow from retriggering. You can check table EKKO if there is a field that you can use to differentiate between new PO and rejected but release code reset PO. Then delegate business object BUS2012, add the database attribute and use it in the event-->Wf condition.

Kind regards, Rob Dielemans