Pir price updation in SCHEDULLING AGREEMENT

1. FSD for Inforecord PriceDetermination in PO / SA(User Exit)
AS IS: Purchase Info record Price determination in business process transactions ME31, ME32
considers the Scheduling agreement creation date to match with the Purchase Info record
validation start. If PIR is created after scheduling agreement creation date, the systemdoes not
pick the price.
TO BE: Enhancement (User Exit) for Info record price determination in PO/SA to satisfy
business process (Scheduling agreement) transactions ME31, ME32. Price determination in
business process transactions ME31, ME32 going to be consider the current date with Purchase
Info record validation date range.
Pass EBELN (Purchasing Doc. / SA) in table EKKO to fetch KDATB (Validity Start).
Pass MATNR (Material) LIFNR (Vendor) and EKORG (Purchase organization) in table A018 to
fetch DATAB (Valid From) to DATBI (Valid to).
Then
User exit going to fetch the ME31, ME32 current date with the Purchase Info record (PIR)
validation date range.
Validation:
Scheduling agreement KDATB (Validity Start) falls on PIR validation date range DATAB (Valid
From) to DATBI (Valid to).

2. FSD for Inforecord PriceDetermination in PO / SA(User Exit)
As per business requirement Screen exit created for ME31, ME32 Transactions Scheduling
Agreement (Validity Start) KDATB falls on the DATAB (Valid From) to DATBI (Valid to) to fetch
the info record price
Pass process Purchase info record (INFNR) Scheduling agreement (EBELN) Item (EBELP) in the
table EIPA to fetch Net Price (PREIS).
By validating validation date range.
If PREIS (Net Price) = 0 (NULL).
If PREIS (Net Price) showing multiple values then check with current date KDATB (Validity Start)
PIR validation date range DATAB (Valid From) to DATBI (Valid to). (Validation date range also
check the subsequent month and years respectively)
If there is no price in the purchase info record throw error like “Price Not Maintained in
Validation Date Range”.
------x------