cancel
Showing results for 
Search instead for 
Did you mean: 

Lock changes to PO if it is linked to a PR with release strategy

0 Kudos

Dear all,

my client has request to unable the changes to PO when it is linked to a PR already released. I'would like to know if there is a standard way to achive this through a warning or error message when user try to change this kind of PO

Please advise me

Thanks a lot

Accepted Solutions (1)

Accepted Solutions (1)

JL23
Active Contributor
0 Kudos

there is nothing specific to PR with release strategy.

If the fields are accessible for changes is depending on the field selection per document type.

so you would at least need a different document type for purchase order to control that

in general you would have these situations:

PO created without PR

PO created with PR with strategy

PO created with PR without strategy

And the last one needs then an extra document type to have an individual field selection.

Quantity changes can be controlled with a standard message

See this old older discussion it has all kind of suggestions which would be applicable here too: https://archive.sap.com/discussions/thread/3500082

0 Kudos

This is a good solution

Thanks!

0 Kudos

Dear Jürgen,

I have defined a new screen Layout so quantity and price are now locked at Item level on PO. However, the price remain still modificable in the conditions tab (by change the condition PB00). There is a way to completely prevent the price change on PO item?

Thanks a lot

JL23
Active Contributor
0 Kudos

see this KBA with 2 options : 2007094 - Prevent price being changed by the Conditions Tab

if they can't be used then you have to consider own programming in a BAdI or exit.

Answers (1)

Answers (1)

JL23
Active Contributor
0 Kudos

A PO without having a PR released in not at all possible.

Before you can even change a PO you have to create it where it is already possible to add information and to change proposed information. About what fields are you actually talking?

0 Kudos

Dear Jürgen,

thanks for your answer. I try to explain better what I mean with an example:

1) I have a release procedure based on PR total value

2) I create and then release the PR with an amount of 100 € for example

3) Now it is possible to proceed with PO creation --> my requirement is at this point.. the user should not be able to change the PO quantity and value considering that the PR has been released only for 100 € and a change could result in a violation of the PR's release strategy parameters