Dynamic Aggregation Dimension Scanner Doesn't Scan By The MC Set Order Defined In Aggregation Run
(Doc ID 2795202.1)
Last updated on OCTOBER 03, 2022
Applies to:
Oracle Utilities Market Settlements Management - Version 2.3.0.0.0 to 2.4.0.0.0 [Release 2.3 to 2.4] Information in this document applies to any platform.
Symptoms
On : 2.3.0.0.0 version, Function processing
Dynamic Aggregation Dimension Scanner doesn't scan by the MC Set order defined in Aggregation Run
After execution of Aggregation Group Run Dimension Scan batch job, it is found that the Dimension Scanner doesn't scan by the MC Set order defined in Aggregation Run (See attached document). As a result, need to execute the Aggregation Group Run several times to get all required Aggregator MCs generated. In our project, we have 4 levels of MCs. So, it basically needs to complete 4 Aggregation Run to generate all required Aggregator MC. Please fix this issue.
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!
