My Oracle Support Banner

Order Releases With Different Priorities do not Consolidate into Single Shipment to Use Equipment Capacity Optimally (Doc ID 2074209.1)

Last updated on AUGUST 12, 2022

Applies to:

Oracle Transportation Operational Planning - Version 6.3.3 and later
Information in this document applies to any platform.

Symptoms

While Bulk Planning Order Releases with Different Priorities are not Consolidated into Shipments to use the Equipment Capacity optimally. Consider the Following Example

Following is the Order Release Data setup

OR 1 (44000 LB, Priority 600)

OR 2 (44000 LB, Priority 1)

OR 3 (8800 LB, Priority 1)

OR 4 (44000 LB, Priority 600)

OR 5 (44000 LB, Priority 1)

OR 6 (8800 LB, Priority 1)

Use of Priority is enabled in both ORDER BUNDLE and CONTAINER OPTIMIZATION in Planning Parameters

On Bulk Planning, the Shipments are planned in the following way

Shipment 1: OR 1 (High Priority/Big) with OR 3 (Low Priority/Small)
Shipment 2: OR 2 (Low Priority/Big) with OR 6 (Low Priority/Small)
Shipment 3: OR 4 (High Priority/Big)
Shipment 4: OR 5 (Low Priority/Big)

The Expectation is the Order Releases of different Priorities are to be consolidated into Shipments so that Equipment Capacity is used completely( As shown below).

Shipment 1: OR 1 (High Priority/Big) with OR 3 (Low Priority/Small)
Shipment 2: OR 4 (High Priority/Big) with OR 6 (Low Priority/Small)
Shipment 3: OR 2 (Low Priority/Big)
Shipment 4: OR 5 (High Priority/Big)

 

Cause

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
Symptoms
Cause
Solution
References


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