Shipment Stops Planned Times Unexpectedly Redriven on Order Unassign Based on Shipment Stops Actual Times (Doc ID 2677992.1)

Last updated on JUNE 05, 2020

Applies to:

Symptoms

When you have an actual time on a multistop stop shipment and you remove any order from shipment (just not the one with stop with actual), see that planned arrivals/departures will be redriven based on the actual times.
Expected result is that planned times will retain as they were and shipment will be driven with planned times and actual times will not be taken into consideration.

EXAMPLE:
---------------
Parameters:

CURRENT TIME SHIPMENT STOP REDRIVE CONFIG GID - REDRIVE STOP=FALSE
STOP ACTUAL SHIPMENT STOP REDRIVE CONFIG ID - REDRIVE STOP=FALSE
ETA SHIPMENT STOP REDRIVE CONFIG GID REDRIVE STOP=FALSE
MAX REDRIVE COUNT=0
IGNORE ACTUAL TIMES DURING ADD OR UNASSIGN ORDERS=TRUE

Shipment Stops before the unassign.

1 P (Planned Arrival: 2020-05-27 18:00), (Estimated Arrival: 2020-05-27 18:00), (Planned Departure: 2020-05-27 18:00)
2 D (Planned Arrival: 2020-05-27 20:37), (Estimated Arrival: 2020-05-27 20:37), (Planned Departure: 2020-05-27 20:37)
3 D (Planned Arrival: 2020-05-27 22:12), (Estimated Arrival: 2020-05-27 22:12), (Planned Departure: 2020-05-27 22:12)

01. Edit Stop #1 and (Actual Departure Time: 2020-05-27 20:00) > Save the shipment
02. Now unassign the order that has stop #3, that will remove stop #3 and leave Stop #1 and #2

Shipment Stops after the unassign.

1 P (Planned Arrival: 2020-05-27 18:00), (Estimated Arrival: 2020-05-27 18:00), (Planned Departure: 2020-05-27 18:00)
2 D (Planned Arrival: 2020-05-27 22:37), (Estimated Arrival: 2020-05-27 22:37), (Planned Departure: 2020-05-27 22:37)

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.