SHIPMENT.DEST_LOCATION_GID Field is Updated to Non Delivery Location When Adding Tracking Event
Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.3.2 to 6.4.2 [Release 6.3 to 6.4]
Information in this document applies to any platform.
The database field SHIPMENT.DEST_LOCATION_GID is is set to the last delivery of a shipment (i.e. last stop_type='D') when initially planned. This is true even if the shipment includes a Depot stop as it's last stop.
When a Tracking Event is added and the action "RECALC ESTIMATED STOP TIMES" is executed, this DEST_LOCATION_GID is being reset to be the Depot Location ID.
This only occurs if the "redrive" option on the agent action is not checked.
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