Last updated on FEBRUARY 01, 2017
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 9 and later
Information in this document applies to any platform.
The PO Price Update process is picking the wrong row of data from VNDR_UOM_PR and using this as the Standard Price on the Purchasing Item Attributes page.
Steps to recreate the issue:
When 2 items are involved and the effective dated prices are between the other price structure.
Item > Define Items and Attributes > Define items:
Item A - Vendor UOM - add 2 new prices in the UOM Price Attributes
01/01/2011 price of $10, no update(Jan 1)
01/02/2011 price of $20, no update(Feb 1)
Item B - Vendor UOM - add a new price in the UOM Price Attributes
15/01/2011 price of $15, no update(Jan 15)
SQL to update the flag on the item to 'to be updated'
Run PO Price Update: Item A will have a standard price of $10
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms