Transaction History Mismatch Between Primary And Transaction Quantity But Primary Unit of Measure (UOM), Results In Onhand Quantity Mismatch
(Doc ID 2462114.1)
Last updated on APRIL 04, 2022
Applies to:Oracle Inventory Management - Version 12.1.3 and later
Information in this document applies to any platform.
Find a mismatch where transactions done in the same Primary Unit of Measure (UOM) but the primary and transaction quantity do not match.
For example, the item's primary unit of measure (UOM) is Each and the transaction was done in Each but the primary quantity is 5 Each and the transaction quantity is 10 Each. The two should match.
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