My Oracle Support Banner

Actual Shipment Stop Times Does Not Get Updated Based on Shipment Stop Location Time zone (Doc ID 2121732.1)

Last updated on AUGUST 12, 2022

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.

For example

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)


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.