Cell Calculation Order: Example 2

In this example, these conditions are true:

Table 68 shows a subset of the cells in a data block:

Table 68. Calculation Order Example 2: Input Cells and Calculated Cells

Year-MarketNew YorkMassachusettsEast
Jan112345687544
Feb135788756435
Mar112234934566
Qtr1123/7

Data values have been loaded into the following input cells:

Essbase calculates the Qtr1 cells for New York, Massachusetts, and East and the East cells for Jan, Feb, and March. In Table 68, the calculation order for these cells is represented by the numbers 1 through 7 that appear in the cells:

  1. Qtr1 -> New York

  2. Qtr1 -> Massachusetts

  3. Qtr1 -> East

  4. Jan -> East

  5. Feb -> East

  6. Mar -> East

  7. Qtr1 -> East

Qtr1 -> East is calculated on both the Year and Market consolidation paths. First, Qtr1 -> East is calculated as a consolidation of Qtr1 -> New York and Qtr1 -> Massachusetts. Second, Qtr1 -> East is calculated as a consolidation of Jan -> East, Feb -> East, and Mar -> East.

The results, as shown in Table 69, are identical to the results for example 1 (see Table 67, Calculation Order Example 1: Results). However, Qtr1 -> East has been calculated twice. This fact is significant when you need to load data at parent levels (see Cell Calculation Order: Example 3).

Table 69. Calculation Order Example 2: Results

Year-MarketNew YorkMassachusettsEast
Jan11234568754181099
Feb13578875643211431
Mar11223493456205690
Qtr1360367237853598220

Based on the calculation order, if you place a member formula on Qtr1 in the database outline, its result is overwritten when Essbase consolidates Qtr1 -> East on the Market consolidation path. If you place a member formula on East in the database outline, the result is retained, because the Market consolidation path is calculated last.