Secondary Shipped Quantity Not Fully Invoiced When Greater Than Over Shipment Tolerance
(Doc ID 1940268.1)
Last updated on AUGUST 14, 2018
Applies to:Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Shipping Transactions form
Have an issue with the Secondary Shipped Quantity not being invoiced fully when the over shipment tolernace is exceeded.
Sample Order 48557
Order line 1.1 has the following:
Ordered Qty = 18.70 KGS
Shipping Qty = 10 UNI (Conversion: 1 UNI = 1.87 KGS)
Shipped Qty = 23.50
Fulfilled Qty = 23.50
Invoiced Qty = 22.44
==> The Tolerance Above = 20
The value for the OM System Parameter "Overshipment Invoice Basis" is set to "Invoice Shipped Quantity".
The OM Implementation Manual states the following for this parameter:
If this value is Shipped, the actual shipped quantity up to the Overshipment Tolerance limit is used for billing.
So, for the sample order 48557, customer physically shipped 23.50 KGS, but the overshipment of 20% calculates to a maximum of 22.44 KGS.
This is why the Invoice was for 22.44 KGS.
However, customer is shipping meat and the invoice is billing by secondary quantity and they need to invoice the complete quantity
They cannot have a loss of control of what is sent with values that are truncated before interfacing to AR for the invoice.
The system gives a message and does not allow the user to ship more than the over shipment tolerance when the primary quantity is shipped.
Either the system needs to give the same message so the secondary quantity does not exceed the over shipment tolerance or the full shipped quantity needs to be invoiced.
The issue can be reproduced at will with the following steps:
1. Create order
2. Pick and ship the secondary quantity greater than the over shipment tolerance
3. Invoice is created but is maxed out at the over shipment tolerance.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!