"MULTISTOP MAX TIME BETWEEN DELIVERIES" Parameter is Being Exceeded
(Doc ID 810596.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Transportation Operational Planning - Version: 5.5.04 to 5.5.05.06
This problem can occur on any platform.
The parameter MULTISTOP MAX TIME BETWEEN DELIVERIES is configured on the Multistop Logic Configuration ID to a specific value (e.g. 12 Hours). This Multistop Configuration ID is assigned to a Parameter Set and used to Bulk Plan two Order Releases. The order releases have Delivery Dates that are forced to exceed more than the value set by this parameter (e.g. the Late Delivery Time for one of the Order Releases is more than 12 hours earlier than the Early Delivery Time for the second Order Release.)
The result of the Bulk Plan is a single Multistop shipment. This is unexpected as it violates the Parameter setting. It is expected that the orders should be planned onto individual shipments.
It is found that if the Multistop Configuration Parameter "MULTISTOP USE LEGACY FLOW" is set to TRUE, then the "MULTISTOP MAX TIME BETWEEN DELIVERIES" is adhered to and the expected result is achieved. The problem only occurs when the "MULTISTOP USE LEGACY FLOW" parameter is set to FALSE.
-- Steps To Reproduce:
1. Create a Multistop Logic Configuration ID that includes the following parameters:
MULTISTOP USE LEGACY FLOW=FALSE
MULTISTOP MAX TIME BETWEEN DELIVERIES=<some value> (e.g. 12 Hours)
2. Create a Parameter Set that uses the above Multistop Logic Configuration ID (set on Parameter: MULTISTOP CONFIG ID)
3. Create two order releases where the first order release's Late Delivery Time is more than the value for MULTISTOP MAX TIME BETWEEN DELIVERIES earlier than the Early Delivery Time for the second Order Release
4. Bulk Plan these two order releases using the above Parameter Set.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.|