Timezone Offset Is Not Considered While Processing Inbound ShipmentStatus Message (Doc ID 1551472.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Transportation Management - Version 6.2.0 to 6.2.0 [Release 6.2]
Information in this document applies to any platform.

Symptoms

On OTM version 6.2 when passing the following (see below) the 11:00 is seen as 11:00 for the timezone the stop location is in and not teh Universal Time Zone OTM is set to use as default:


20130501110000
+02:00


EXPECTED BEHAVIOR
-----------------------
It is expected that the time zone used will be the Universal Timzone (UTC) OTM is set to use as default and the ofset will be used to convert the time into a time for the location.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Send in the XML with the following:

20130501110000
+02:00


2. Note that the stop has a tiems of 11:00 and not 13:00 (11+2)

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