Description
A bulk-material order requests one thousand units, but the final truck brings the cumulative shipped quantity to nine hundred sixty. The warehouse closes the remainder because the result falls within an agreed under-delivery range. In a course catalog, “Fusion SCM Online Training” is a useful label for the cross-functional discipline this case demands: shipping arithmetic alone cannot settle it. Closure also affects fulfillment status, the quantity sent for invoicing, the customer's return entitlement, and the evidence retained for reconciliation. A shipment can be operationally valid while still creating a commercial question if users assume that ordered, shipped, fulfilled, and billed quantities must always be identical.
A Tolerance Defines a Range, Not a Forecast
Shipment tolerances accommodate products whose exact final quantity is difficult or inefficient to control. Bulk solids, cable, fabric, liquids, and variable-yield output can finish slightly above or below the requested amount. An under-delivery percentage establishes the lowest acceptable cumulative shipment, while an over-delivery percentage establishes the highest. These percentages do not change the customer's original request or predict what production will make. They create boundaries within which shipping may complete the line. Treating the upper figure as a production target encourages excess; treating the lower figure as an automatic shipping plan can reduce service unnecessarily.
The calculation starts from ordered quantity, but execution may occur through several shipment lines. That distinction matters when a first truck carries six hundred units and a second carries three hundred sixty. Looking at the second load alone makes the quantity seem far below any reasonable minimum. The relevant comparison is the cumulative result for the connected fulfillment line and its splits. Reviewers need the original quantity, both tolerance percentages, all confirmed shipment quantities, any open releases, and the final-shipment indication. Without that lineage, a valid closure can look like an unauthorized cancellation, or an actual shortfall can be hidden among splits.
Shipping and Order Management Share the Decision
The Oracle Help Center: Guidelines for Setting Up Shipment Tolerances describes a cross-functional sequence: the order sends a shipment request containing tolerances, shipping enforces the boundaries and returns shipment advice, order management decides whether to continue or split fulfillment, and the resulting transaction proceeds toward receivables. It also explains that shipping cannot close a line below the minimum tolerance; the remaining line requires action in order management. This division prevents a warehouse action from silently rewriting a commercial commitment. It also means that troubleshooting must follow messages and states across functions rather than stopping at ship confirmation.
Over-delivery introduces another control. Shipping must have enough picked quantity before it can ship above the request, and the result cannot exceed the maximum boundary. Yet physical permission to ship does not settle what should be invoiced. A governing parameter can direct invoicing to use actual shipped quantity or ordered quantity for an over-delivery. That choice has consequences for revenue, customer expectations, costing, and later returns. Teams should document the commercial policy before enabling the range. Otherwise, the warehouse may celebrate a valid shipment while finance investigates why units moved without an apparently matching invoice quantity.
The Last Forty Units
Consider an order for one thousand kilograms with five percent under-delivery and eight percent over-delivery permitted. Two shipments total nine hundred sixty kilograms. The lower boundary is nine hundred fifty, so the cumulative result sits within range. If shipping marks the second movement as final and communicates that state correctly, fulfillment can complete without another forty kilograms. This is not the same as losing forty kilograms or deleting demand arbitrarily. The accepted range was part of the executable order, and the actual quantity must remain visible to downstream functions. The customer communication should describe the shipped amount, not merely say that the order is complete.
Now suppose the two shipments total nine hundred forty kilograms. The result is below the minimum, even though the difference from the accepted boundary is only ten. Shipping should not use tolerance to close the remainder. A responsible review asks whether another shipment is feasible, whether the customer agrees to a formal order change, or whether the open quantity should be canceled through the authorized process. Manually forcing a final state would erase the distinction between an agreed operating range and a new commercial decision. Small numerical differences still matter when they fall on opposite sides of a configured boundary.
Defaults Need an Effective-Date Mindset
Tolerance defaults may come from central parameters, item settings in a validation organization, a rule, or an extension. The source and precedence should be explicit. More importantly, changing a default does not guarantee that existing submitted lines inherit the new value. A copied order, a newly added line, and an old line carried through a revision can therefore display different behavior even when they reference the same item. Investigation should capture when the line was created and submitted, where its value originated, and whether later configuration was expected to affect it. Current setup alone cannot explain every active order.
Some fulfillment patterns and item structures do not support the feature in the same way as an ordinary shippable sales item. Configured items, kits, services, returns, transfers, drop shipments, and other specialized flows require attention to documented limitations. A broad default should not be interpreted as universal permission. Before rollout, classify order types by product structure and fulfillment route, then test only supported combinations. Where a range is commercially needed but the standard flow does not enforce it, define a separate approved process rather than assuming a tolerance value will travel through every downstream application.
Reconcile Four Quantities
A useful control report places ordered, shipped, fulfilled, and invoiced quantities side by side, with lower and upper boundaries calculated from the original line. It should preserve split relationships and identify whether open releases remain. Exception rules can then distinguish an accepted under-delivery from an unresolved shortfall, an accepted over-delivery from an excessive shipment, and a billing policy difference from a true interface error. Returns deserve the same discipline because the quantity eligible for return can derive from what was actually fulfilled. Reconciliation becomes clearer when each quantity is named instead of compressed into a single idea of completion.
Conclusion
Shipment tolerance is a bounded fulfillment rule, not permission to improvise around order quantity. Reliable use requires cumulative evaluation across splits, correct final-shipment signaling, explicit treatment of quantities below the minimum, and a deliberate policy for invoicing an over-delivery. Teams must also preserve the configuration source and timing that produced each line's values. Within a curriculum described by the exact catalog phrase “Oracle SCM Online Training,” paired scenarios can compare identical physical loads under different tolerance and billing policies. The useful outcome is not a rehearsed procedure but a reconciliation of order, shipment, fulfillment, invoice, and return quantities that explains whether the line closed correctly and where any remaining commercial decision belongs.
Managed by
Tech Leads IT
