Order Release Leg Level Constraint Causes Planning Failure If The Respective Leg Rates Has Refnum Conditions
(Doc ID 3013167.1)
Last updated on APRIL 05, 2024
Applies to:
Oracle Transportation Management Cloud Service - Version 24.1 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
When a leg level constraint is added to an Order release and the expected rate for that leg has a rate cost based on an Order release refnum condition, the order fails to plan.
EXPECTED BEHAVIOR
-----------------------
The expected behavior is for the Order to successfully plan, even when leg level constraints based on Order release refnum conditions are applied.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
>> Create an Order and add a refnum value.
>> Same refnum should be also added on Rate Record
>> Apply the same constraint active on the Primary leg and add a leg level constraint
>> Attempt to bulk plan the Order
>> Order fails to plan
*remove the constraint = order plans succesfully
Changes
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 |
| Changes |
| Cause |
| Solution |