Bulk Plans Run Longer when CHECK COMMODITY COMPATIBILITY Parameter Set to True
(Doc ID 2876089.1)
Last updated on JULY 05, 2022
Applies to:
Oracle Transportation Management Cloud Service - Version 22.1 and laterOracle Transportation Operational Planning Cloud Service - Version 22.1 and later
Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
When order commodities are considered during bulk planning by setting the CHECK COMMODITY COMPATIBILITY parameter to TRUE, OTM is excessively querying commodity data to load for planning. OTM is not utilizing cache to load commodity data which is impacting bulk plan run time and causing bulk plans to run slower. This is noticeable for bulk plans with larger set of orders (i.e. over 100 order releases)
EXPECTED BEHAVIOR
-----------------------
It is expected to be able to plan order releases by checking commodity compatibility close to the same time frame it takes with the parameter CHECK COMMODITY COMPATIBILITY set to FALSE.
STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Bulk plan a set of orders with defined order commodities. Ensure that the parameter set being used for planning has the CHECK COMMODITY COMPATIBILITY parameter set to TRUE
2. The respective bulk plan will take time to run. The time it takes to run is dependent on many factors including the number of orders.
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 |