Skip to Content
0

Wrong PIR is getting picked in PO.

Jan 31, 2017 at 12:03 PM

61

avatar image

PIR is created for Plant, Material and Vendor, now if I have extended one material to a new plant and try to create the PO with this material and plant, Old PIR is getting picked without the net price, and allowing me to enter the price manually and save the PO without any error.

When I have checked the conditions tab

Instead of picking the our condition type it is picking the standard condition type PBXX and showing message as "Condition has been found (without condition record)"

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

1 Answer

Jürgen L
Jan 31, 2017 at 12:22 PM
0

How do you differentiate old and new?

An info record has a unique number for material / vendor combination. So there is nothing old / new if you extend the material master to a new plant.

If you have 2 info records for the combination of material / vendor in table EINA then you might have a bug from a wrong data migration.

If you maintain conditions at plant level in the info record, then you have to extend the info record too to the plant for which you extended your material master.

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

Hi Jurgen,

Thank you for your reply,

we maintain conditions at plant level, I have not extended this PIR to the newly created Plant and still the PIR number for previous PIR which was created for same material vendor but different plant is getting picked, and allowing me to enter the price manually.

0

as I wrote before, you cannot have 2 PIR numbers for the combination of the same vendor and material number. If you have it then it is a bug.

If you have not extended the info record to your new plant then it probably has conditions at purchasing org level, but I seriously doubt that SAP takes the conditions from another plant. This is technically pretty impossible, as a qualified access would be needed and from where should it take the plant number of the wrong plant?

If you have evidence for that then you should open an incident at SAP Support to get a bug fix.

0