My Oracle Support Banner

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 FEBRUARY 03, 2019

Applies to:

Oracle Inventory Management - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Find a mismatch where transactions done in the Primary Unit of Measure (UOM) but the primary and transaction quantity do not match.

Example
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.

Changes

 

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.