Cannot Save Requisition When Using Item Setting UOM For Current and Future Date
(Doc ID 2427787.1)
Last updated on JANUARY 04, 2021
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 9.2 and later
Information in this document applies to any platform.
Cannot save requisition when using item setting UOM for current and future date.
Getting an issue when add a future dated effective unit price row on the UOM Price Attributes area.
Add the new date, new price, and update the "Standard Price Update Status" to 'To Be Upd'.
When creating a new requisition, get an error that the UOM coming across is not a valid value.
If we delete the new effective dated row, the issue is corrected.
"This is not a valid unit of measure for the item. (10150,222) Please select a valid unit of measure from the prompt."
The issue can be reproduced at will with the following steps:
1. Added an additional UOM (CS) created an original unit price with an effective date of 01/01/1901 and saved.
Go back into the page and added a new effective dated row for 08/01/2018 with a lower price
2. Create a Requisition. Clear UOM and lookup UOM. Select the UOM created above.
Got the message: "This is not a valid unit of measure for the item. (10150,222) Please select a valid unit of measure from the prompt.”
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document