Last Price Paid is Incorrect, because Putaway Process Puts Items Away in Random Order

(Doc ID 2156708.1)

Last updated on JUNE 30, 2016

Applies to:

PeopleSoft Enterprise SCM Inventory - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


Last Price Paid incorrect (because putaway process puts items away in random order)
First when "x" order qty of the good A has the "y" price, second "z" qty ordered of the same item A has "n" price and so on.
There are situations when the vendor sends a receipt that overlaps two or more qty/price tiers and the cost accounting is affected by the wrong value in the Last Price Paid field for the item that is being purchased

The issue can be reproduced at will with the following steps:

1. Create a PO with multiple lines for the same item – this tiered down pricing has no specific rule, the vendor is selling the goods as follows based on the quantity
2. In the DEMO environment, on each distribution of each schedule, designate in which Inventory Business Unit should be the item received
Line 1 Schedule 1 Distribution 1
Line 2 Schedule 2 Distribution 2
Line 3 Schedule 3 Distribution 3
3. Dispatched the PO, then created a receipt as follows:
First two lines fully received
Third line partially received (just 10 units out of 50)
4. The RECV_01 job kicked in at save
5. After the jo finished, the last transaction is actually the receiving of the first PO line
6. The receiving price on line 1 is 50 so that is the last price paid
The perpetual average cost shows the cost as starting at 30, then evolving towards 45.6863 when it should be the other way around – from 50 to 45.6863




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms