The new purchase order picks up the price from the last purchase order.

[Santosh__Gangurde]

Prerequisite.

1. For the test, here I have created a material master with nothing special in it—just a normal material master with Basic data 1, Purchasing, Plant data 1 and account 1 view. 
2. Supplier master with nothing special as well. 
3. Configure SSCUI - Define Default Values for Buyers - 103909 as below. 

You can select A or B, or C, depending on business need. 

Step 1: Create a PO and mark the info update tick in the PO as below. Either ME21N or the Create Purchase Order app.

Save PO. and reopen PO to check the purchasing info record number in PO. 

Step 2: Open PIR in ME13 and validate prices. 

Here price will be zero if your PIR is created from the PO. 

In case if your PIR was created before, then go to ME12 in PIR.
Then, in the condition tab in PIR, remove the price from it and make it zero. So that condition will look like below in ME13. 
Don't worry about the price in the Purchasing view. 

Save PIR. 

Step 3: Run a background job to update the PIR price from purchasing documents.  (Job Program - RM06INP0).The 
Fiori app is - Schedule Update of Price for Purchasing Documents. For on-prem, it can be tested in SE38 as well. 
If it's cloud, use the Fiori app if its On-prem use the Program. Here i will use Fiori app.

Then decide on recurrence depending on how frequently you want the job to update PIRs with new prices from PO. 
If it's not very frequent, once a day is fine, but if it's too frequent, then maybe 10 min or so, depending on business need. 
I will use it once only, as I am just testing it. 

Select the right options that suits you and schedule a job. 

Then wait until the job is finished. 

Step 4: ME13 - Check if PIR net price updated in purchasing org data 1 view. 

So every time the job runs, it will check if a new document and new price is there, if new price idedntified then the system will update PIR for the combination. 

Step 5: Create a new PO and validate if the price is coming. 

Now for the test again, change the price to let's say 15 in the PO and check if the info update is active. 

Again background job will run if you have set a recurrence. Once the job runs, it will update the price.
Here, I will show in the backend how it updates in SE38 with the program RM06INP0 for understanding. 
Run the SE38 update program RM06INP0 and execute. 

Depending on the job selection criteria below, selection will happen. Here I am taking the material and supplier as well just for testing. 

Job will update the info record with the new price as shown, here I did in the front end only to understand, but in real time job will do it in background everytime job runs. 

Step 6: test again new PO in ME21N. 

New price will come again from last PO. 

Note that - If the background job is not executed between two PO creations, then the new price will not come, so select a background job run frequency appropriately.

This method only works if you do not use conditions and an access sequence. If you have value in conditions, this method will not work; in that case, you have to update the price manually for conditions in MEK2. 

Steps summary 

1. PIR must be without condition.
2. Mark PO with info update tick.
3. Run job to update PIR prices - RM06INP0  or  Fiori - Schedule Update of Price for Purchasing Documents.
4. Check the new price in ME13.
5. Create a new PO and test.