Skip to Content

How to set Release Strategy for a PO on Hold?

May 12 at 01:52 PM


avatar image

Hi All,

We have a requirement to put the Purchase Order on hold during creation/change by logging an error at Header level when a certain custom validation fails which we have written in the BADI - ME_PROCESS_PO_CUST.

Now when this happens, we also need a Release Strategy to be applied to the PO which is put on hold. The problem we have here is, the Release Strategy is not getting triggered when the PO is put on hold. It's triggering only if we remove the custom logic which logs the error.

Is this a Standard SAP behavior and cannot be overridden by some enhancements? Because I found an SAP note (1981241) addressing this issue saying this is the standard design, but still wanted to know if anyone had come across a similar requirement and was successful in achieving so.

Could someone please share some idea on this?



10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
PRASOON AK May 12 at 06:30 PM


Logically, a PO will be on hold only if some data is missing or there is an error in the PO. In such cases, there is no meaning in triggering the release and if it triggered, the approver has to check and correct the PO before release, which is not logical.

If you have lot of such cases where users mis-using the hold function, you may check the feasibility of deactivating the hold option in the PO as mentioned in the same note shared by you. Please check and revert back.



Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Prasoon,

Thanks for the suggestion. Yes, even I had the same understanding that if a release strategy is applied on a PO there is no necessity to put the PO on hold. We have now changed our approach related to this.