'RECALC ESTIMATED STOP TIMES' Agent Action Recalculates Completed Shipments
(Doc ID 2663690.1)
Last updated on APRIL 27, 2020
Applies to:Oracle Transportation Management Cloud Service - Version 19.3 and later
Information in this document applies to any platform.
When having a shipment with multiple legs, when adding Freight Arrival event for the third leg, the dates for the following legs are being changed accordingly, even though the one of the shipments in the middle is Completed.
It is expected to recalculate Start/End Times until one Shipment Completed was found in the route.
The issue can be reproduced at will with the following steps:
- Order Release planned in 5 shipments:
- Secured Resources for them
- Added a Tracking Event to the Shipment in the middle - Arrived at Stop, Second Stop, Event Time: 2019-12-17 20:00:00. This was added successfully. End Time was changed to 20:00:00 and the next shipments start time and end time recalculated as expected. The Status was changed to ENROUTE_COMPLETED.
- Added a Tracking Event to Shipment number 2 - Arrived at Stop, Second Stop, Event Time: 2019-12-17 19:00:00. This was added successfully. End Time was changed to 19:00:00 and the next shipments start time and end time
recalculated. However, the start time and end time of the next shipment which was ENROUTE_COMPLETED was modified to the original values. Actual Arrival is still populated as per the event date.
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