Redrive of DayDuration Shipment Due to Event Occuring on Non-Working Days Results in a Departure on this Non-Working Day
(Doc ID 1924412.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.3.1 to 6.3.4 [Release 6.3]Information in this document applies to any platform.
Symptoms
A shipment/tracking event for an "Arrival" is entered for a Shipment planned with DayDuration. This event has a time that is not within the "working days" defined on the calendar associated with the DayDuration rate. OTM is assigning the "Arrival" with this time, but then also updating the "Departure" to be this same time. It is instead expected to have OTM find the next "working day" and set the departure to be that date.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |