General Page
This Technote provides important details about changes to the Consolidated rule functions in IBM Planning Analytics.
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_ref.2.0.0.doc/c_calculationfunctions_tm1ref.html
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_ref.2.0.0.doc/c_calculationfunctions_tm1ref.html
A defect with the consolidated rule functions (min, max, avg, count, and countunqiue) was corrected in the Planning Analytics 2.0.7 release. The ConsoidateChildren function is not impacted by the changes described in this document. Prior to this defect fix all consolidate rule functions used the TM1 Server sparse consolidation algorithm whenever the underlying cube had SKIPCHECK enabled.
However, even with SKIPCHECK enabled, a consolidate function can be called with ignore_zero_values disabled, that is a flag value of either 0 or 1. In this case, in order to include zero values the sparse algorithm is no longer appropriate, since it does not include zero values.
The fix in IBM Planning Analytics 2.0.7 causes the sparse calculation algorithm to be ignored when calculating values us cells populated by the consolidated rule functions. This is an exception to the SKIPCHECK rule which typically ensures that the sparse algorithm is always used for that cube.
As a result of this correction, two things changed for all consolidate functions using a flag parameter value of either 0 or 1.
1. Performance may degraded when calculating views. This degradation can be potentially significant if the total number of potential cells in the cube is large.
2. The value result of the consolidation is now different, since it now (as specified by the flag parameter) includes zero valued cells.
This assumption is based on that the customers were not treating the previously returned consolidation values as incorrect.
If the intent is to exclude zero values in the calculation of the consolidated rule function then the appropriate action is to modify the flag value of the consolidate rule function by changing the flag value from a 0 to a 2, or from a 1 to a 3.
An additional defect (APAR PH13403) was identified and corrected in the IBM Planning Analytics 2.0.8 IF5 and 2.0.9 releases. This second defect only affects the ConsolidatedCountUnique rule function. The other consolidated rule functions are not affected. This defect prevents the above suggested action of changing the flag parameter from 0 to 2, and 1 to 3, from being interpreted properly when rules are processed.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCTEW","label":"IBM Planning Analytics Local"},"Component":"TM1 Server","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
20 September 2021
UID
ibm13117345