Shipment Start Time and End Time Planned Incorrectly Into the Future Instead of Closer to Early Pickup Date on the Order Release
(Doc ID 2065960.1)
Last updated on AUGUST 12, 2022
Applies to:
Oracle Transportation Management - Version 6.2.8 to 6.4.2 [Release 6.2 to 6.4]Information in this document applies to any platform.
Symptoms
An Order Release is created where only the Early Pickup Date is provided (all other dates, such as Late Pickup, Early Delivery and Late Delivery are null). Order Release has TIME WINDOW EMPHASIS set to BOTH, HOLD AS LATE AS POSSIBLE set to FALSE, MINIMIZE WAIT TIME IN SERVICE TIME CALCULATION is set to TRUE.
If this Order Release is planned to a Shipment, If Rate Service associated with the relevant itinerary has Drive Time Penalty populated, Shipment Start Time and End Time are calculated based on the value set in the Parameter ORDER WINDOW TIME SPAN. If ORDER WINDOW TIME SPAN has the value of 365, Shipment Start time and End Time is calculated to last possible Time Window of next 365 days. The excepted behavior is to calculate the Shipment Start time and End time as close to Early Pickup Date as possible.
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 |