Link Shipment Action is Not Honoring the Primary Shipment Planning Parameter
(Doc ID 2078789.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Operational Planning - Version 6.3.7 to 6.4.2 [Release 6.3 to 6.4]Information in this document applies to any platform.
Symptoms
Having two shipments with different parameter set, the Link Shipment action is not honoring the planning parameter from the shipment, instead it is taking the one that is set at Domain setting.
It is expected when linking two shipments to have OTM use the parameter set from the primary shipment
The issue can be reproduced at will with the following steps:
1. Search for shipments <1>, <2> (shipment <1> is planned with parameter DEMO1, shipment <2> is planned with parameter DEMO2)
2. Check both and go to Actions -> Operational Planning -> Manage Continuous Move -> Link Shipment
3. It will fail (doesn't matter)
4. Retrieve the log
5. Search for setgid and notice that it is using the following:
PlanningParameters PlanningParameterHelper.getPlanningParameter(): setGid is null, retrieving setGid from DomainSetting table.
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 |