Secondary Shipped Quantity Not Fully Invoiced When Greater Than Over Shipment Tolerance
(Doc ID 1940268.1)
Last updated on JUNE 13, 2021
Applies to:Oracle Order Management - Version 12.1.3 and later
Oracle Shipping Execution - Version 12.1.3 and later
Information in this document applies to any platform.
Secondary Shipped Quantity not being invoiced fully when the Over Shipment Tolerance has been exceeded.
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 OM System Parameter "Overshipment Invoice Basis" value is set to "Invoice Shipped Quantity".
The OM Implementation Manual defines this parameter as:
"If this value is Shipped, the actual shipped quantity up to the Over Shipment Tolerance limit will be used for invoicing."
So, for the above example, 23.50 KGS was physically shipped, but the over shipment of 20% calculates to a maximum of 22.44 KGS.
This is the reason then that the invoice will show the invoiced quantity as 22.44 KGS.
However, customer is shipping meat and the invoice is billing by secondary quantity, but it needs to invoice the complete quantity.
The application raises a message and does not allow the user to ship more than the Over Shipment Tolerance when the primary quantity is shipped.
Expect the application to give the same message so secondary quantity does not exceed the Over Shipment Tolerance or expect that the full shipped quantity is invoiced.
The issue can be reproduced at will with the following steps:
1. Order Management Super User Responsibility
2. Enter and book orders
3. Pick and ship the secondary quantity greater than the Over Shipment Tolerance
4. Invoice is generated 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!
In this Document