Order Release Constraint in OTM is Getting Panned Even If the Planning Criteria is Not Satisfied
(Doc ID 2947504.1)
Last updated on MAY 14, 2023
Applies to:
Oracle Transportation Management Cloud Service - Version 19.3 and laterInformation in this document applies to any platform.
Symptoms
While executing Order Release Planning in OTM, users have choice to add Constraints on an Order Release. Constraints can be one or multiple planning attributes that are responsible and playing a vital role during Order Release Planning.
Couple of Key Constraints for OTM Planning are as like Itinerary, Service Provider, Rate Offering, Rate Records, Transport Mode, Equipment Group etc.
During planning, adding a Constraint in Order Release is mainly done when customer wants a specific attribute to be selected among more than one eligible attributes.
On this context, there is observation like- a Constraint in Order Release is being picked up for Planning even if that doesn't satisfy the Planning Criteria for the Order Release.
Customer added one random Rate Record as Order Release Constraint Buy Rate Record ID. Suppose, that Rate Record is not satisfying the other criteria of Planning for that Release e.g.
- Constraint Rate Record is for different Geography
- Other Constrains don't go with the same Rate Record etc.
Now if they Plan the Order Release, the Planning will happen successfully and that random Rate Record will be considered as the Planned Rate Record.
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 |
References |