Invoice Quantity Incorrect for Sales Order Line Entered In Secondary UOM
(Doc ID 1121404.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Inventory Management - Version 12.0.0 and later
Information in this document applies to any platform.
Executable:WSHINTERFACE - Interface Trip Stop
You have a Product Item which is set up as Dual Unit of Measure Controlled, and for which a Deviation Tolerance between the Primary and Secondary quantities is allowed.
You enter a Sales Order Line for this Item, and the Ordered Quantity is entered in the Secondary Unit of Measure (UOM).
The Primary Quantity on the Sales Order Line is correctly defaulted as the Ordered Quantity times the standard UOM conversion factor.
At shipment time you find that although the Primary Quantity of the shipment remains the same, the Secondary Quantity has varied for some allowable reason (for example evaporation, expansion, spillage).
On the Move Order for the shipment you therefore modify the Secondary Quantity but leave the Primary Quantity unchanged.
After Ship Confirm you find that while Trip Stop has passed the correct Primary and Secondary quantities to the Sales Order Line and the Delivery Detail, the information passed to the RA_Interface_Lines table for use by AutoInvoice was incorrect.
What has happened is that Trip Stop has taken the Primary Quantity from the Shipment, and has recalculated the Secondary Quantity using the standard UOM conversion.
The Invoice Quantity (remember that the SO Line was originally entered in the Secondary Unit, so the Invoice is also in that Unit) is therefore incorrect because it does not reflect the user-entered quantity actually shipped.
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