Incorrect Dates for Multi-Leg Shipment When Using "HOLD AS LATE AS POSSIBLE" and "PLAN SHIPMENTS WITH CARRIER COMMITMENT" Parameters (Doc ID 2118791.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Transportation Operational Planning - Version 6.3.0 to 6.4.2 [Release 6.3 to 6.4]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------

Customer has observed that when planning a multi-leg shipment using planning parameter HOLD AS LATE AS POSSIBLE which is set as TRUE, and PLAN SHIPMENTS WITH CARRIER COMMITMENT set to TRUE ,the dates for the first leg are incorrectly being assigned based on the current system date instead of being calculated based on the 2nd leg dates which are set correctly from the Late Delivery Date on the Order Release. The same is not happening when the customer uses "Show Routing Options" for the order release. When using Show Routing Options, the dates assigned for both legs are correctly set. Also if the customer sets PLAN SHIPMENTS WITH CARRIER COMMITMENT to the default of FALSE, the dates are assigned correctly. The customer cannot switch off the CARRIER COMMITMENT, as the clients uses this in their business.

EXPECTED BEHAVIOR
-----------------------
The customer expects that the dates on the first leg will be based off the delivery dates for the second leg and not on the current system date. The customer is upgrading to 6.3.7 and in their existing 6.3.1 instance, the dates are assigned correctly.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

Select the Order, go to show Routing Option, select the Itinerary, optimize. Check the dates on The Shipment.

Select the Order, go to Bulk-Plan-BUY, select the same Planning Parameter and click on OK. Check the dates on The Shipment.
1. Select Order
2. Go to Show Routing Options and select multi-leg itinerary and optimize. Notice the dates on the first and second legs.
3. Using the same order, Bulk Plan the order using the same Parameter Set and notice that the dates for the first leg are based on the system date, not back dated based on the dates of the second leg which are based off the late delivery date on the order.

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