Essbase Dynamic Member With Self-Reference
Planning/Essbase professional like to use Dynamic member formulas. One of advantages is to take no data storage, therefore to improve overall performance. Second, it improve the correctness of calculation and can be easily and quickly verified, without waiting for calc scripts to run (some may rely on aggregation). When you have multiple Dynamic Calc members, whether within a dimension or cross dimensions, you would have to understand the ordering between Dynamic Calc members. 1) Dynamic Calc order within a dimension follows the outline order. 2) Dynamic Calc on Sparse dimensions will come before Dynamic Calc on Dense dimensions. The reason for this is that the Block Storage need be VIRTUALLY created first before it can perform calculation. 3) Dynamic Calc on Dense dimensions will come after Dynamic Calc on Sparse dimensions. (is this just a repetition of #2 in an opposite way?) Among the dense members, Account and Time will be calculate first, following by other Dense dimensions