Urgent Issue in PR Release Strategy- Not getting released Problem

[vignesh_ramesh]

Hello Experts,

We have implemented a WF and a BADI Enhancement for PR Release Strategy long before 2010 and it was working smooth till last week.

In our Release Strategy process every approver must release their respective releases on ME52N transaction which is being called on WF Decision step.

We are using SAVE event to trigger and re-trigger the WF from different release levels.

Example : ( R8 -> R2 -> R3 )

R8 Approver Approves it and the decision went to R2 Approver.

R2 Approver was busy so he forwarded the WorkItem to his subordinate and this is very common process they follow.

Both the R2 Approver and his Subordinate has same role configured.

The issue arrises when the subordinate tries to release it.

She has released it with a 'Tick' icon indicating successful release and saved the PR.

Note: SAVE is an event which updates the current Workitem in WF , releases that particular strategy and completes the flow and re-triggers a new one for next approver.

The issue is this, the Subordinate user has saved it and the WF has sent new Workitem to the Next approver R3.

But this dint not get updated at all. For the Next Approver in R3 Level it shows R2 Release strategy is still pending so he is not able to approve it even though the previous approver has approved it.

This scenario works smooth for 5 yrs and then this issue.

I thoroughly checked all possible ways of error but everything seems to be fine.

Even the User has created a similar PR again and it works well as expected. Duh !

Now im more confused where the hell the problem is ?!!?

If anyone has come accross something similar pls help me resolve this.

Thanks,

Vignesh R.

[vignesh_ramesh]

Thanks everybody for your usefuls uggestions.

I found the root cause of the issue.

Since the user selects the respective WI, the decision step is still IN-PROCESS which i totally dint see. So whatever happens it happens in that step. Later i came to find that there were Modal and Amodal Methods assigned for that decision step which was restricting the release strategy.

They have set a program exit too where a memory id is being set on a condition.

IF that PR has an attachment it creates a pop-up window to go to the ME54N t.code.

The users are forced to check those attahccmnet by downloading or opening it. Funny they have not attached documents for any PR before.

Only then the release strategy will be released, else its skipped and further there should be a error handling which was not done in the exit.

As all these things happen in the background , none of us were able to seee it even when we tried to replicate the scenario.

Now im handling those errors.

Once again THANKS A LOT.

Cheers.