SRM PO Workflow Issue

[Former Member]

Hi,

The issue is about PO workflow in extended classic scenario (SRM 7.0, support pack SAPKIBKV16) and it is occurring sometimes (not very often).

• n-step badi has been implemented in SRM.
• PO in SRM goes for approval. Approver is yet to approve the PO.
• Meanwhile the PO is changed by the user and the changed version (C1) creates the new workflow. But it didn't delete the previous PO workflow and the old work item is still in approver's inbox. The C1 version is getting approved completely and the PO is in ordered status now.
• When the approver of the original PO version tries to approve, the system is creating a changed version of the PO (say C2). But the work item is not getting completed and is again coming back to the same approver's inbox. If he tries again, it is creating another changed version say C3 and the work item is again back to approver's inbox.
• But the PO is in ordered status and the system is not changing anything in the PO.

We are able to remove the stuck work item manually from the approver's inbox. But it is causing the confusion for the users.

Any suggestion is highly appreciated.

Warm regards,

Aswini

[laurent_burtaire]

Hello Aswini,

what is your SRM workflow type (ACW oor PCW)?

Aswini Kumar Sahoo wrote:

(...)

PO in SRM goes for approval. Approver is yet to approve the PO.
Meanwhile the PO is changed by the user and the changed version (C1) creates the new workflow....

(...)

Do not remember in ACF, but in PCW, this is not possible: during workflow, if any other user than the approver is in change mode in the PO, the WI is recalled (revise status).

Indeed, you cannot have a change version PO generation during approval. If so, there is a standard bug or you made standard modification.

Regards.

Laurent.

[Former Member]

Hi Laurent,

Many thanks for your suggestion!

We have ACW and we have not done any changes in the standard code.

The issue is occurring once in a while and not for all the POs.

Warm Regards,

Aswini

[laurent_burtaire]

Hi again,

check if OSS note 2245995 - Purchase order approval does not lock the purchase document could solve your issue.

If not, raise an OSS message.

Regards.

Laurent.

[Former Member]

Thank you Laurent!

Will check this and will come back with the findings.

Warm regards,

Aswini