Bulk Plan Fails Using a Multi-Leg Itinerary Where Carrier Capacity Limit Is Defined for a Specific Leg
Last updated on OCTOBER 28, 2016
Applies to:Oracle Transportation Management - Version 6.3.6 and later
Information in this document applies to any platform.
A multi-leg shipment is being planned with the first leg tied to a ground schedule for the first leg and a regular shipment for the final leg. The ground Schedule for the first leg has scheduled planned shipments for every 2 weeks (ex: every other Tuesday). A carrier capacity limit of 2 per week is defined for the second leg. If orders are planned separately, 2 orders are planned onto a shipment on the first available ground schedule to the intermediate location and an additional 2 shipments are created for each order from the intermediate location to the final destination. This takes up the full capacity for this week. When the 3rd order release is planned, the order is planned onto a shipment 2 weeks later. This is the desired and expected behavior.
The issue arises when bulk planning 3 or more orders all at once. The bulk planning fails although it is expected that 2 orders are planned for the next available Tuesday and the 3rd order is planned on a shipment 2 weeks later on the next available Tuesday, as what happens when you plan the orders separately.
It is expected that the bulk plan runs successfully with 2 orders planned for the next available Tuesday and the 3rd order planned on a shipment 2 weeks later on the next available Tuesday, as what happens when you plan the orders separately.
The issue can be reproduced 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 2 weeks).
b. The second leg is a dynamic leg between location y and z.
2. Create a carrier capacity limit of 2 per week for the second leg.
3. Bulk plan three order releases with a starting location of x and destination location of z. Ensure the order releases are constrained to use the itinerary from step 1.
4. The bulk plan will fail.
5. Plan each order release separately. The orders will be planned successfully.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms