Last updated on JULY 09, 2014
Applies to:Oracle Transportation Management - Version: 4.5 to 5.5 - Release: 4 to 5.5
Information in this document applies to any platform.
Checked for relevance on 23-Aug-2010
-- Problem Statement:
Defined a location in Oracle Transportation Management, OTM, and set the time zone using the US/Central, US/Eastern, etc. time zone formats.
Create a shipment using the new location with the time zone defined as mentioned above and then assign an Appointment Time to the stop. When OTM stores the data to the database it correctly calculates the appropriated GMT time offset, however the OTM UI's Shipment Stop screen is displaying time zone as CDT and EDT instead of CST and EST.
-- The issue can be reproduced a number of ways, the following is only one example:
Setup Locations using the US/Central, US/Eastern semantic for Time Zone
Bring in an Actual Shipment setting Appointment Delivery and Appointment Pickup at the stop level
View Shipment Stop level Details
-- Business Impact:
The data is correctly stored in the database, but the incorrect time zone name can be confusing to users.
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