My Oracle Support Banner

Since CU4: Bulk Planning Multistop With Different Originating Leg Only Possible With Default Planning Parameter Set (Doc ID 602494.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Operational Planning - Version: 5.5.04
This problem can occur on any platform.


With <> a solution was implemented into CU4, that when bulk planning 2 Order Movements that have different original itinerary legs, instead of 1 multistop shipment 2 individual
shipments are created.

The consequence is, that when bulkplanning Order Movements that don't have the same original leg
ID, they don't get multistops even if this is the desired result. This constraint can be ignored
on the ACTION of the Order Movement, so it does build into one multistop shipment but this means
the shipment can only be built with the default Planning Parameter set.

In other words, there are either two shipments when using a custom Planning Parameter, or being
forced to use the Default Planning Parameter, when one multistop shipment is desired.


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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

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