Tracking Event Number Is Larger Than Internal OTM Code Can Handle
Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.1.5 and later
Information in this document applies to any platform.
Agent updates utilizing an 'out of box' OTM action are failing because the code cannot handle the size of the TE numbers.
(TRACKING EVENT TO SHIPMENT) - COPY RECEIVED FIELDS TO SHIPMENT - Update Ship Unit Information
The tracking event numbers have reached the max value.
The Stack Trace received in the logs: "Error is obtaining ie_s_ship_unit and ie_s_ship_unit_line for shipment SNI/IM.SI103333240/transaction_no 2147485254 java.sql.SQLException: Numeric Overflow"
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms