Appointment Time Window Fields Are Not Respecting The Timezone Of The Stop Location
(Doc ID 2122613.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.3.7 to 6.4.2 [Release 6.3 to 6.4]Information in this document applies to any platform.
Symptoms
User has a preferred Time Zone associated. When the User edits the Appointment Time Window for a Shipment Stop (on a Location which is in a different Timezone), User Preferred Time Zone is used to convert the Time entered into UTC to persist in the database and later Location's Time Zone is used to display the Time on the Shipment Stop. This is causing the Appointment Times on the Shipment Stops being different from the previously entered ones.
Actual Behavior
Time Entered on UI
07/02/2016 05:00:00
07/02/2016 07:00:00
Time Saved in Database
07/02/2016 04:00:00
07/02/2016 06:00:00
Time displayed on UI later
07/02/2016 04:00:00
07/02/2016 06:00:00
Expected Behavior
Time Entered on UI
07/02/2016 05:00:00
07/02/2016 07:00:00
Time Saved in Database
07/02/2016 04:00:00
07/02/2016 06:00:00
Time displayed later (converting back to Location TimeZone)
07/02/2016 05:00:00
07/02/2016 07:00:00
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |