cancel
Showing results for 
Search instead for 
Did you mean: 

PR can be changed after PO created from the PR(by adopting) .. need to stop

Former Member
0 Kudos

Dear experts,

In our current system PR can be changed after PO created by adopting the PR. How can i block this change.

Kindly help

Regards,

Zusen

Accepted Solutions (1)

Accepted Solutions (1)

JL23
Active Contributor
0 Kudos

you can add message 06 608 in OME0 with error, then it will not be possible to change the quantity if the requistion is already ordered full.

Answers (3)

Answers (3)

Former Member
0 Kudos

ok

pankaj_singh9
Active Contributor
0 Kudos

Hi,

If required, system can be configured in such a way that after PO creation w.r.t. PR, user will not be able to amend the PR Quantity. In this case system will issue an error Message no. 06608 saying that Requisition already converted into purchase order & &.

This will be done under path: - SPRO > MM > Purchasing > Environment Data > Define Attributes of System Messages > System messages

Former Member
0 Kudos

Hi

Thank you for your reply.

I have set message 06608 as error but problem still is there. After creating a PO 4500013405 w.r.t a PR 100018999 and can add new line in PR 100018999. How can i stop this..

Kindly help.

Thanks and regards,

Zusen

Former Member
0 Kudos

Hi Zusen,

You have 2 choices; either implement my first solution or put your logic to BADI ME_PROCESS_REQ_CUST like if EBAN-STATU <> N then give an error.

Regards

JL23
Active Contributor
0 Kudos

Hi

>

> Thank you for your reply.

>

> I have set message 06608 as error but problem still is there. After creating a PO 4500013405 w.r.t a PR 100018999 and can add new line in PR 100018999. How can i stop this..

>

> Kindly help.

>

> Thanks and regards,

> Zusen

Is that really a problem? the second item has has the same PR number. but if you look at the technical structure of the purchase requisition table, then this table does not have a header table and no item table, it is just one table --> EBAN

if you create a second item, then you have the same PR number but different item number

otherwise

you have a different PR number but same item number.

It is really just one field which is different.

And 06608 message prevents the change of the item which is already used in a PO.

Former Member
0 Kudos

If you use release strategy for PRs you can use the field selection key to additionally determine whether certain fields in a purchase requisition may or may not be changed once it is released.