Bulk Plan Chooses Wrong Ground Schedule In Multi Leg Itinerary When A Calendar Is Used to Close a Location Temporarily

(Doc ID 2106884.1)

Last updated on FEBRUARY 16, 2016

Applies to:

Oracle Transportation Management - Version 6.3.6 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
When planning a multi-leg shipment that starts with a ground schedule for the first leg and a regular shipment for the final leg, the bulk planning engine chooses the last chronologically available ground schedule when a calendar entry, closing the final destination, is applied.

EXPECTED BEHAVIOR
-----------------------
It is expected that the bulk planner will choose the next available ground schedule that coincides with the final destination being open in respect to the location calendar, instead of choosing the last available ground schedule.

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

1. Create an itinerary with 2 legs (with locations x, y, and z):
a. The first leg is tied to a ground schedule with planned shipments all in future dates between location x and y (for this example, the ground schedule has planned shipments every week for 5 weeks).

Note: For this example, week 1 signifies the first instance of this ground schedule planned shipment in the future up until week 5.

b. The second leg is a dynamic leg between location y and z.

2. Create a calendar that closes location z for week 1.

3. Bulk plan an order release with a starting location of x and destination location of z. Ensure the order release is constrained to use the itinerary from step 1. Ensure that the order release has a pickup/delivery window that encompasses all planned ground shipments that are in the future

4. The bulk plan will execute and plan a shipment tied to the last available ground schedule planned shipment. For this example, the shipment will be planned for week 5 instead of the next available planned shipment of week 2.

Note: Ensure that the rate service being used does not have a max wait time that exceeds the location z calendar closure. Also ensure that the max freight idle time at location y does not exceed the location z calendar closure.



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