PO not going for re-release after addition of freight charges

[Former Member]

Hi all,

I have a po which has already been released, but MIGO is not done. I am adding the the freight charges in the header condition after the release of PO, which changes the total amount of PO. After addition, the PO is not going for re-release. The release indicator used is 6. Kindly suggest.

Regards

[Former Member · Accepted solution]

Hi,

In standard SAP, PO release will consider only basic price as amount and it will not consider other condition types.

You can achieve your requirement through version management and need to create one more characteristic for version update. One you update the version in PO, the system will trigger new release.

There is an user exit also to achieve the requriement.Please check with ABAPer...With this user exit, if there is any change in PO then it will trigger new release.

Regards

Kumar.

[BijayKumarBarik]

Hi,

You need to check how is your release procedure design for your purchase order.

Cross check  level of release of purchase order with values and how many release strategies set up!

In standard -Net purchase order value increases and the new value in the purchase order is next level of release,then new release strategy  will triggers and if the new value in the purchase order is same level of release which is within same release strategy,so no new release strategy  will triggers.

If any BADI or User exits is used for designing of purchase order release strategies, then new release strategy  triggers based on design and development.

Regards,

Biju K

[Former Member]

Hi,

     In standard SAP, PO release is based on the base price changes and not on the other price conditions.

So, please check whether the characteristics defined in the release are changed or not.

Thanks & Regards,

Vinay

[former_member192897]

Please search the forum and you get the desired links. System doesnot consider the freight cost condition value into the release value. Go to Badi or User exits have written the code as per your requirement.

User exit EXIT_SAPLEBND_002 will work in your case.