The GMT Conversion is Not Happening when Entering the Date Through Shipment Stop User Interface. (Doc ID 988575.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 5.5.04 to 5.5.04 - Release: 5.5 to 5.5
Information in this document applies to any platform.

Symptoms

On OTM version 5.5.04 when an existing stop has its times changed via the UI the time is seen to be entered for the time zone of the location and converted to GMT (the UTC) in the database. When a new stop is entered the times are not seen as for the time zone of the location and are not converted to GMT in the database, resulting in the times being converted incorrectly when displayed in the UI.



EXPECTED BEHAVIOR
-----------------------
Expect the times to be saved to the database and converted to GMT when doing so.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1 - Log onto an OTM 5.5 CU4 system

2 - Create an Order Release (Using locations tat are not in the GMT time zone) and plan it onto a Shipment.

3 - Edit the Shipment and navigate to the stop details for stop 1.

4 - Set the Estimated Arrival Time and Planned Arrival Time to 11-11-2009 11:00:00

5 - The stops tab shows the times with the time zone, for example MST.

6 - Via SQL run an SQL statement to find the times saved to the database:
     Select * from shipment_stop where shipment_gid = 'LEE.01125'

7 - For stop 1 the following is shown:

PLANNED_ARRIVAL = 2009-11-11 18:00:00.0
ESTIMATED_ARRIVAL = 2009-11-11 18:00:00.0

8 - The times have correctly been converted to GMT and the UI in view mode shows the times as entered in MST.

9 - Navigate to: Transportation Planning and Execution > Shipment Management > Buy Shipment

10 - Search for and Edit the Shipment.

11 - Click on the Stops tab.

12 - Click on the New Stop button.

13 - Set the following:
    Stop number: 3
    Location ID: USBOS (This is the Port of Boston and has a USA time zone of EST.)
    Planned Arrival Time: 13-11-2009 11:30:00
    Estimated Arrival Time: 13-11-2009 11:30:00
    Planned Departure Time: 13-11-2009 12:00:00
    Estimated Departure Time: 13-11-2009 12:00:00

14 - Click Save, then click Finished.

15 - Log on to the database via the backdoor and run the following SQL

16 - Select * from shipment_stop where shipment_gid = 'LEE.01125' and stop_num =3

17 - The details for stop 3 are:
    Planned Arrival Time: 13-11-2009 11:30:00
    Estimated Arrival Time: 13-11-2009 11:30:00
    Planned Departure Time: 13-11-2009 12:00:00
    Estimated Departure Time: 13-11-2009 12:00:00

18 - The times entered have not been converted from EST (timezone of the location) to GMT (which is the UTC).

19 - View the shipment in the UI and the times for Stop 3 were shown as EST BUT are now shown as follows:

    Planned Arrival Time: 13-11-2009 06:30 EST
    Estimated Arrival Time: Not shown in view
    Planned Departure Time: 13-11-2009 07:00 EST
    Estimated Departure Time: Not shown in view

Conclusion :-

In steps 5 to 7 the time of an existing stop was changed to 11/11 11:00 and was converted to GMT in the database,. When the UI displayed the time the GMT time was taken from the database converted to MST and the UI displayed the correct time as previously entered of 11/11 11:00 MST.

With the new stop the time entered in the UI is not being seen as EST (time zone of the location used) it is being seen as GMT and saved to the database as such. Then when looking at the UI the time is taken from the database as GMT and being converted to EST. Because the time was never converted from EST to GMT when saving to the database the result is an incorrect time is displayed.


Cause

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