Shipment Stop Screen Does Not Convert TimeZone Properly When the Date Field Is Blank Initially
(Doc ID 2212261.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle Transportation Management - Version 6.3.6 to 6.4.3 [Release 6.3 to 6.4]
Information in this document applies to any platform.
Shipment Stop screen doesn't convert timezone properly when date field is blank initially.
Edit a Shipment Stop via the Shipment Stop screen > updates the "Actual Departure Time" or "Actual Arrival Time" with 2016-10-25 14:57:50 (America/Los_Angeles) for example > then click "Finished"
When you open the Shipment Stop, the date drops three hours as if it is saving it in EST timezone, so it shows as 2016-10-25 11:57:50 (America/Los_Angeles)
01. The User Preference has no Timezone defined. So the default is EST. The Timezone on the Shipment Stop comes from the Stop Location which is (America/Los_Angeles)
02. This issue only happens when adding the date when the field is NULL. If it happens to update the field that already has a date saves, you will not see the issue
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