Restricting PO Price Change (ME22/ME22N)

[Former Member]

Hi Guys,

Restrict Purchase Order Price Change:

We want to restrict buyers from changing the price on the purchase order/Contracts after it has been created. So basically restrict them from making any change to the PO price within transactions ME22/ME22N/ME32/ME32K. We would like to provide the buyer with flexibility to change the price within a given tolerance level, if possible.

Has anyone instituted this type of practice? If yes, what are all the different methods which could be used to achieve this? What are the Pro/Cons for each of the methods?

Any guidance would be appreciated.

Thanks.

Shobha.

[Former Member · Accepted solution]

You can do it in following manner

1) make the field selection of pricing field for all transaction you want as a display in spro-mm-po- define screen layout for po

here for AKTV field selection make the price uint display then you will see in pochange display but at the item detail level condition will be open that you can make display in M/06 tcode.

but you can put the price change tolerance here

2) either you can create the release strategy so whenever user change the price it will go agian for approval

3) use the user exit to control this kine of issue MM06E005

4) you can use the functional authorization for buyer where you can use your own filed selection

[Former Member · Accepted solution]

Hi Charlie,

Thank you for such a quick response, but I need to clarify something you stated:

<i><b>"you can make display in M/06 tcode but you can put the price change tolerance here" .</b></i>

Did you intent to say that ""you can make display in M/06 tcode but you can <b>NOT</b> put the price change tolerance here"?

Additionally, I haven't found anywhere else where the price change within tolerance can be set, beside the user exit option. Do you agree?

Please respond...

Thanks..

Shobha.

[Former Member · Accepted solution]

Yes you can't do w/o user exit

in M/06 you can make the PB00 display

[Former Member · Accepted solution]

Thanks Charlie...