Shipment Not Being Built Due To Rate Geo Seq Number Being Too Big
(Doc ID 2513422.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Transportation Management Cloud Service - Version 18 and later
Information in this document applies to any platform.
Shipment not being built due to rate geo seq number being too big
When creating Rate Record from UI, the Sequence Number is set to high value. Because of this, when OTM is trying commit shipment, it is failing at shipment cost level where error indicates that sequece number is too high
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