OTM Rate Inquiry (RIQ) is Not Resulting with the Specific Rate Record While Used Multiple Ship Units As Constraints
(Doc ID 2930056.1)
Last updated on MARCH 15, 2023
Applies to:
Oracle Transportation Management Cloud Service - Version 22.3 and laterInformation in this document applies to any platform.
Symptoms
While executing Rate Inquiry (RIQ) with more than one constraints for Ship Unit, OTM is listing all available Rate Records rather than a specific one that fully satisfied the conditions from all those Ship Unit constraints.
For an example, if-
Customer has two rate records as below-
- Rate Record 1 with Ship Unit length <= 100 m, Rate Cost 100 EUR
- Rate Record 2 with Ship Unit length <= 200 m, Rate Cost 200 EUR
During RIQ, if the constraint added is-
Scenario# 1 : ship unit with length 80 m, this fetches the Rate Record 1
Scenario# 2 : 1 ship unit with length 150 m, this fetches the Rate Record 2
Scenario# 3 : Both the ship units from 1 and 2, then both the rate records are fetched
Expected Behavior
-------------------------
For the Scenario# 3, the expectation is to get only the Rate Record 2.
Because, only this rate record is satisfying both the conditions.
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 |