Load Configuration Setup Is Ignored On Ship Unit That Is Not Listed First On Order Release
(Doc ID 2454444.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Transportation Management - Version 4.5 to 6.4.3 [Release 4 to 6.4]
Information in this document applies to any platform.
A Load Configuration Setup that is Stackable is used on the ship unit that is listed first on the ship unit tab of an Order Release, the second ship unit has a Load Configuration Setup that is not Stackable. The results of the Load Config using this setup is expected where the ship units on the front of the equipment are stacked and the non stackable ship units are not stacked.
If this is changed so that the ship unit with the Load Configuration Setup that is not Stackable is listed first on the ship unit tab then none of the ship units on the equipment are stacked.
The expectation is that the stackable ship units will be stacked regardless of how this is listed on the order release.
The following issues are occurring due to this:
1. 2 shipments are being built when 1 is possible, because the ship units that should be stacked are not being stacked.
2. The stackable ship units that are put onto the second shipment are able to be stacked but not the stackable ship units that are on the first shipment.
View Load Config from the navigation Shipment > Actions > Operational Planning > View > Load Config
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