OTM Is Changing The Timezone ID For Outbound Tracking Event Transmission.

(Doc ID 1525024.1)

Last updated on MARCH 11, 2013

Applies to:

Oracle Transportation Management - Version 6.2.7 and later
Information in this document applies to any platform.

Symptoms

Timezone not kept when sending out Tracking Event via integration.

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

01. Create an Agent:
Event: TRACKING EVENT - CREATED
Action: match to shipment ID
Send Integration: use an external system

02. Create an Order and plan a shipment.

03. Send in a shipment status xml.
On the xml, the element: (for example)
EventDT has the date/time of 20121207020000 with a timezone of CET..

04. As a result of the XML, the agent is triggered and the tracking event is sent out.
When I look at that xml via the outbound transmission, the EventDT has a date/time of 20121207020000 but a timezone of UTC and not CET.

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