on 2011 Aug 30 11:09 PM
We are running SRM 7.0 with Process Controlled Workflow and have configured N-Step approval process for PO.
When the PO is ordered for the first time, the approver determination and the approval process work as expected. However, after the PO has been ordered, and the user makes changes to the ordered PO and re-orders it, the PO's approver list does not get refreshed, and the PO header shows the following staled information in "Approval" tab with "current status" = "Finished" -
Process Step Status Processor
SRM Purchase Order Approval Approved <approver user name>
And the PO would go into "Awaiting Approval" status but the PO work item does not appear in anybody's UWL.
Any hints regarding the possible cause of this behavior are appreciated.
Thanks.
Request clarification before answering.
Hi,
What do you see in SLG1?
what is the workflow log shows and status ?
Can you please give some more details..
Saravanan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
check in the BBP_PD the changed version po generated. there you will see if any WFL started or not. Or take the PO change version GUID and go at SWI6/swi1 to check the WFL log.
At SLG1 should appear also, check if at table /SAPSRM/C_WF_CST you have the trace level set to 1. This will make slg1 take all logs (green and red).
You can also always force a restart via BADI /SAPSRM/IF_EX_WF_PROC_RESTART
Thanks,
Melina
Hi,
As Melina said, goto BBP_PD and enter the PO number. System will automatically take you to the change version PO history. Scroll all way the down. you can see 'Workflow Item:' and row as Workitem-ID. take the id . Follow the Melina instruction. Now you can see the workflow log.
could you please share the workflow log details to analysis further.
Saravanan
Both of you are on the right track - the changed PO is not created in a change version. In our normal process, the changed PO would be a change document, so the approver (re)determination is done properly (and no RESTART BADI implementation is required as we don't want to overwrite the system behavior). But this particular issue occurred when we "assign Open PO as Source of Supply" (a PPS functionality) in SOCO for an SC item. I believe this could be due to an error in this function. So I will close this thread for now as it is not really a workflow issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.