How to close PO CV from SRM GUI?

[Former Member]

Hi Experts,

We are running SRM5 ECS. We keep getting issues on PO change version workflow getting stuck or in error and not able to process the PO anymore, sometimes insignificant change in PO is supposed to be auto-approved but due to workflow goes into error, system is unable to execute SETRELEASE for the PO CV.

As SRM support team, we are not authorized to delete PO CV from portal. I would like to know, is there any standard FM or report that can close PO CV and complete/delete associated workflow? After this PO's active version will be retained.

Regards,

Karthik

[Former Member]

Hi Karthikeyan,

Yes there is an option to SETRELEASE for the PO which is stuck. We use the t-code SWO1 to manually close the active version so that the PO can be processed further.

The steps to use the t-code is as follows

Step 1: Go to t-code SWO1

Step 2: Specify the Object Type as BUS2201

Step 3: Click on Test

Step 4: Click on Instance and specify the corresponding GUID

Step 5: Execute the SETRELEASE Method

Step 6: Specify the Initiator basically the creator of the version

Step 7: Execute. The PO should be approved for the version which is not closed

We had used the above method when we used to have an active version for the PO which refused to close.

Before you try on a production play around with the above steps and then once comfortable with the same then use it on the production PO.

Regards

Pramod

[Former Member]

Thanks for this workaround Pramod. SRM support is not authorized to execute transaction SWO1 even in FireFighter.

Actually, I would like to delete the change version of PO from SRM backend by executing FM and retain PO active version. It should be similar to the process followed by a purchaser opening the PO change version on portal in edit mode and clicking delete button at header level.

It deletes change version and resets change_lock to space on active version.

Regards,

Karthik

[Former Member]

Hi Karthikeyan,

Can you check whether the FM BBP_PD_PO_DB_DELETE is of any help. This is used to delete the PO itself. You can check whether it is possible with this FM to delete the change version.

Try to give the GUID of the change version and delete the same.

Just a try with this workaround. Not sure whether it will actually work out.

Regards

Pramod