Last updated on MARCH 29, 2016
Applies to:Oracle Transportation Management - Version 6.3.6 and later
Information in this document applies to any platform.
When Tracking Events are processed into OTM, based on the Tracking Event Code Shipment Stop Times are Updated using the Shipment Agent Action RECALCULATE SHIPMENT STOP TIMES. Time Zone ID used is "Local" and SSStopSequenceNum is included in the Inbound Shipment Status XML. Event Date on Tracking Event is updated as expected. The Time is updated to Actual Arrival Date and Departure Date incorrectly.
Property glog.integration.ShipmentStatus.findTimeZoneByTEStopNum is set to TRUE
Consider a Shipment Stop on a Location with Time Zone - GMT-6
A Shipment Status Message is processed as following
Tracking Event UI Displays the following Values
UI - ON Shipment Tracking Events - 2016-03-09 10:00:00.0 - Time Zone ID Displayed as Local
Shipment Stop UI Displays following Values
ON Shipment Stop - Actual Arrival time is Updated as - 2016-03-09 04:00:00.0
Since the the Time Zone ID in the Inbound Shipment Status XML is Local, the Actual Arrival Time on Shipment Stop should be Updated to 2016-03-09 10:00:00.0 (same as the Time in the Shipment Status)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms