Planning Parameter "Hold As Late As Possible" Is Ignored During Merge Shipments With Optimize Option
Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.2.6 to 6.4.2 [Release 6.2 to 6.4]
Information in this document applies to any platform.
When merging two shipments with Optimize option, the Service Time is not calculated as the latest possible time even with Parameter "HOLD AS LATE AS POSSIBLE" set to TRUE.
-- Expected Behavior/Solution:
The latest possible Service Time should be applied to the merged shipment according to Parameter "HOLD AS LATE AS POSSIBLE" being set to TRUE.
An Order has the following dates:
Early Pickup Date = 26-April 00:00:00
Early Delivery Date = 27April 00:01:00
Late Delivery Date = 28-April 23:59:00
Assuming that the Transit time is 1 day and the Activity Time at the Drop Off Location is 1 hour, when the two shipments are planned the Start/End time calculation is as below:
Start time is calculated as 27-April 23:59 (Late Delivery date of Order (28-April 23:59) - Transit time)
End time is calculated as Start time + transit time (1 day) + Activity Time of Loc = 01 May 00:59
When merging the Shipments (Actions -> Operational Planning -> Change Shipment Route -> Merge Shipments) and selecting the Optimize option, the planning logic applies
the Best Service Time result on the Shipment, even though the same planning parameter is used for merging.
Start time is calculated as 26-April 00:01:00 (Early delivery date of Order - Transit time)
End time is calculated as Start time + transit time (1 day) + Activity Time of Loc = 27 April 01:01:00.
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