5/23/23, 3:48 PM Document 888113.

1
Copyright (c) 2023, Oracle. All rights reserved. Oracle Confidential.

Why are Delivery Numbers appearing with gaps, or not in sequence? (Doc ID
888113.1)

In this Document

Goal
Solution
References

APPLIES TO:

Oracle Shipping Execution - Version 11.5.10.0 to 12.1 [Release 11.5.10 to 12.1]

Oracle Shipping Execution - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

GOAL

Why when using the "Auto-Create Deliveries" button on the Shipping Transaction Form does the
system assigns a delivery name to selected lines, but this delivery name/number is not in sequence?

SOLUTION

Delivery Number sequencing and your observations of "missing" or random allocations of new numbers
could be the result of either,

1. Your application environment residing on a RAC (Real Application Cluster) type environment.
In this manner, potentially individual application users can be assigned to individual server
nodes and these individual nodes will have their own/unique sequences caching. Thus depending on which node the
application user is assigned to the resulting Delivery Number (sequence) is likely to be unexpected in comparison to
another application node.

This behaviour can be resolved, however, if the Delivery Number sequence is defined with the
"ORDER" caveat, as outlined in Note 382755.1. This will however have a deterimental affect on Delivery creation
performance.

2. Alternatively out-of-sequence Delivery Number generation is caused by delivery details being

back-ordered due to insufficient inventory quantities as outlined in additional Note 315615.1

When "Auto-Creating Deliveries" it is the deliveries that are being created and deleted which causes the gap in the delivery
number sequence assignment. The delivery is created before Allocation (for Autocreate Deliveries as 'Yes') for the delivery
details. If there is insufficient quantity, the detail(s) is backordered and unassigned from the auto-created delivery. At the
end of the Pick Release process, all such empty auto-created deliveries are deleted. Some mechanisms to "work-around"
this behaviour is also outlined in Note 315615.1, but none of these are particularly appealing from an implementation point
of view.

Still Have Questions?

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a
discussion in the My Oracle Shipping Execution Community.

REFERENCES

NOTE:315615.1 - In a Pick Release Batch, Delivery Numbers are not being Created and Assigned Sequentially
NOTE:382755.1 - Why Are Delivery Numbers Generated Not In Sequential Order?
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=qg1wcrno_102&id=888113.1 1/2
5/23/23, 3:48 PM Document 888113.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=qg1wcrno_102&id=888113.1 2/2