Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.2.7 to 6.3.2 [Release 6.2 to 6.3]
Information in this document applies to any platform.
On OTM version 6.2.7
If an event is added after the planned date and time on the Shipment has passed OTM incorrectly populates:
1 - 'Estimated Departure' field is populated with the date and time the event was added, which is not a shipment related time.
2 - The Shipment End date is updated to the date and time the event was added, which is not a shipment related time.
3 - Duration is calculate from Shipment Start time to the new and incorrect End time.
4 - Wait Time at the stop level is twice that of the weight time (which itself is incorrect).
Expect OTM to calculate these fields correctly.
The issue can be reproduced at will with the following steps:
1 - Log onto an internal OTM system.
2 - Use and existing Shipment ID: 02207
Dates on the Shipment are:
Start: 16/11/2012 05:49:24
End: 16/11/2012 08:49:44
Stop times are:
Planned Arrival: 16/11/2012 05:49 Europe/London
Estimated Arrival: 16/11/2012 05:49 Europe/London
Planned Departure: 16/11/2012 06:49 Europe/London
Planned Arrival: 16/11/2012 07:49 Europe/London
Estimated Arrival: 16/11/2012 07:49 Europe/London
Planned Departure: 16/11/2012 08:49 Europe/London
3 - Add an Event.
(Actions > Shipment Management > Events > Add Shipment Event > Add Shipment Event.)
Status: Estimate Arrival / Estimated Delivery
Event Date/Time: 16/11/2012 07:59:00
Event Location: Use stop 2.
4 - Click 'Save'.
5 - Edit the Shipment and the following now shows:
Start Time is unchanged.
End time is now: 03/12/2012 14:47:18
Duration has changed from 3 hours to 17D 8H 57M
6 - Stop 2 now has the following times:
Planned Arrival Time
16/11/2012 07:49:44 (unchanged)
Estimated Arrival Time
16/11/2012 07:59:00 (as entered by the event)
Planned Departure Time
16/11/2012 08:49:44 (unchanged)
Estimated Departure Time
(This time is the time the event was physically typed in during this test case and has no relation to any shipment times, therefore it is incorrect and misleading.)
34D `11H 36M
This seems to be the time from the 16th Nov to today the 3rd Dec, which is 17 days, times 2.
This figure is of no use and is incorrect.
Conclusion, the times are not being updated as expected and hold misleading values.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms