Plannedshipment XML Contains an Invalid Date Format where the Seconds Part of the Date Shows as 60, Which is One Minute and Seconds Should be 00. (Doc ID 1145214.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 5.5.05.04 and later   [Release: 5.5 and later ]
Information in this document applies to any platform.

Symptoms

On OTM 5.5.05.04 finding that a PlannedShipment XML is sending out time stamps with the seconds set to 60, this should not arise and the minutes should have gone up by one because 60 secodns is a single minute.

EXPECTED BEHAVIOR
-----------------------
Expect the seconds to reach a maximum of 59 before increasing the minute by one and the seconds moving to 00.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a Shipment in OTM
2. Add an Event.
3. Send from OTM an PlannedShipment XML and not the time has 60 representing the seconds.


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