Default UOM on Requisition is Not What is Defined as Primary UOM for the Item
(Doc ID 304948.1)
Last updated on MARCH 23, 2023
Applies to:
Oracle Purchasing - Version 11.5.9 to 11.5.10.4 [Release 11.5]z*OBSOLETE: Microsoft Windows 2000
Oracle Solaris on x86 (32-bit)
z*OBSOLETE: Microsoft Windows XP (64-bit Itanium)
IBM AIX on POWER Systems (64-bit)
Red Hat Enterprise Linux Advanced Server Itanium
SUSE \ UnitedLinux x86-64
Red Hat Enterprise Linux Advanced Server x86-64 (AMD Opteron Architecture)
Linux x86-64
Oracle Solaris on SPARC (64-bit)
IBM AIX on POWER Systems (32-bit)
z*OBSOLETE: IBM AIX 4.3 Based Systems (64-bit)
Oracle Solaris on SPARC (32-bit)
Linux x86
HP-UX PA-RISC (64-bit)
HP Tru64 UNIX
Microsoft Windows (32-bit)
POXRQERQ.fmb
Symptoms
The primary unit of measure of item 'XX' and is the expected default UOM for this item for all requisitions; but when the Requisitions are created for the item, the UOM is defaulting some other UOM 'YYY'
How do we change the default for the item in creating or importing new requisitions?
Cause
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
| Symptoms |
| Cause |
| Solution |