cancel
Showing results for 
Search instead for 
Did you mean: 

Wrong release code in PR workflow once release strategy is reset

suman16992
Explorer
0 Kudos

Hello folks,

I am facing an issue, my PR has 2 level approval say L1 and L2. Once L1 has approved its into L2 approver, at this time i deleted line item and then undeleted it. After i undelete, release strategy resets and in PR release tab it shows that PR is in L1 stage for approval. But when workflow restarts, it picks L2 as release code and hence show L2 approver which is incorrect.

So how do i correct this ?

Regards,

Suman Verma

keohanster
Active Contributor
0 Kudos

Hi Suman,

Are you using custom workflows or SAP-delivered ones? Can you post a screen shot of the Event Log at the time you delete and then undelete the line, as well as when the workflow restarts?

Sue

arghadipkar3013
Contributor
0 Kudos

Please make sure the SignificantlyChanged event is used as a Terminating event of the Workflow or Approval Task. Ideally if the Line is deleted and the amount falls in a different Release Code level SignificantlyChanged event gets triggered and a new Workflow or new Approval task is triggered.

Thanks

Arghadip

Accepted Solutions (0)

Answers (1)

Answers (1)

suman16992
Explorer
0 Kudos

Thanks Susan and Arghadip,

As in Picture 1 attached, my PR is released for L1 code and it is at C1 level. Now when we delete and undelete PR line item then, workflow should start from begin i.e from release code L1. But what is happening here is in workflow we can see release code as C1 and hence it is going to wrong approver. Hope this information helps.

picture1.png

Regards,

Suman Verma

keohanster
Active Contributor
0 Kudos

Could you post a screen shot of the Event Log (transaction SWEL) for the relevant times?

suman16992
Explorer
0 Kudos

event-log.png

HI Susan,

I have attached event log screen.

1.)1st SIGNIFICANTLY CHANGED event triggered when we delete PR line item and the PR.

2.)When we undelete PR line item, release step is created and event RELEASESTEPCREATED is triggered.

3.)When 1st level approval is done for release code L1 then RELEASE event is triggered.

4.)Then in next level approval for release code C1, when it is rejected then event SIGNIFICANTLYCHANGED is triggered with release code C1 and goes to RR creator.

5.)Again when PR creator makes changes in PR then, RELEASESTEPCREATED event is triggered but with release code C1 not L1.