The Shipment Stop 'Transit Time' And 'Activity Time' Are Removed After Receiving Tracking Event That Runs 'RECALC ESTIMATED STOP TIMES' Agent Action
(Doc ID 2434139.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.4.2 to 6.4.2 [Release 6.4]Information in this document applies to any platform.
Symptoms
The activity time and drive time on the shipment stops are getting removed when an agent with 'RECALC ESTIMATED STOP TIMES' agent action is run after adding a Tracking Event on the shipment.
Example:
========
Required Agents:
---------------------
Agent ID: SHIPMENT EVENT TRACKER
Agent Type: SHIPMENT
Agent Event: SHIPMENT STATUS - TRACKING
Agent Action: RECALC ESTIMATED STOP TIMES
Agent ID: LEGACY SHIPMENT MATCHING
Agent Type: TRACKING EVENT
Agent Event: TRACKING EVENT - PROCESSING REQUEST
Agent Action: LEGACY SHIPMENT MATCHING
Required Shipment:
------------------------
A shipment with Transit and Activity time on a stop
On stop 2:
Transit Time = 1 M
Activity Time = 1 H
Required actions on the shipment:
------------------------------------------
Secure resources the shipment.
Actions > Secure Resources
Add the Tracking Event.
Actions > Events > Add Tracking Event > Add the following info
Responsible Party: Carrier
Status: Delivered
Completed Unloading at Delivery Location
Event Date/Time: 2018-05-10 16:46:00
Shipment ID: xxx
Shipment Stop: 2
Click Finished
Result:
----------
Now on stop 2:
Transit Time = null
Activity Time = null
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |