Tracking Event "Re-Drive" Action Not Using Event Datetime (Doc ID 858225.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 6.0 to 6.0.1
This problem can occur on any platform.

Symptoms

-- Problem Statement:
On 6.0, Find that the Re-drive based on a Tracking Event does not use the Event Date/Time to Re-drive the shipment whereas it looks like the Planned Time on the Shipment is used

EXPECTED BEHAVIOR
Expect that the Event Date/Time is used to re-drive the Shipment

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Set up an agent to Listen for a Shipment Event with the action to Run Recalc Estimated Stop
Times with Late Threshold set to 0 D, Oh and 0 Minutes, Re-drive Ticked and the Update Results Set
to Actual Departure
2. Add a tracking event on the shipment that is 1 hour later than the Planned Departure of the
Shipment
3. See that the Actual Departure on the Shipment Stop 1 is changed but the second stop time is not
changed

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