While Using Commitment Allocation in OTM, Total Planned Count is NOT Matching With Total Finalized Count
(Doc ID 2994271.1)
Last updated on DECEMBER 20, 2023
Applies to:
Oracle Transportation Management Cloud Service - Version 19.3 and laterInformation in this document applies to any platform.
Symptoms
OTM Customer sometimes has observation that, while using Commitment Allocation and planning Order Releases, Total Planned Count is not matching with Total Finalized Count.
The issue can be understood with the following details :
-----------------------------------------------------------------
1. Defined commitment allocation
2. It has been configured with 3 service providers details
3. User planned 7 orders and got the expected number for each Service Providers that is on the commitment.
4. All orders are with the same status (Not Started)
5. The Total Planned Count (7) is the same as the number of orders planned
6. But the Total Finalized Count (4) is less than the Total Planned Count
-----------------------------------------------------------------
1. Defined commitment allocation
2. It has been configured with 3 service providers details
3. User planned 7 orders and got the expected number for each Service Providers that is on the commitment.
4. All orders are with the same status (Not Started)
5. The Total Planned Count (7) is the same as the number of orders planned
6. But the Total Finalized Count (4) is less than the Total Planned Count
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 |