Order Release Fails to Create with Transaction Code of II with Exception: "The sequence null for rule is exhausted"
(Doc ID 1594510.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.2.8 to 6.3.4 [Release 6.2 to 6.3]Information in this document applies to any platform.
Symptoms
When uploading an Order Release XML into and using a transaction code of II, OTM it is not generating the ship_unit ID as per the BNG rule, to include the Order Release ID. Instead it is being created simply as "-001", "-002", etc...
As more order releases are created, eventually the ship unit sequence is exhausted (once the iD reaches "-999") and the XML begins to fail with the follwoing Exception:
The sequence null for rule <BNRule:DOMAIN.SHIP_UNIT_XID.DEFAULT,SHIP_UNIT_XID.DEFAULT> is exhausted
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |