Database Reference
In-Depth Information
The first warning is to make sure that the FIx tightly controls the number of blocks
that will be processed. I have already shown what happens when a large dimension is
not included in the fix.
The rules for CrEAtEBLoCkonEQ include:
• The result of the formula must be a member of a sparse dimension.
• Do not use cross-dimensional formulas.
• CrEAtEBLoCkonEQ statement forces a top-down calculation.
Below is an example of a cross-dimensional formula. measures and year are
dense. All other dimensions are sparse. The database is completely empty except for
C ola->new york->Ac t u a l->S a le s->Ja n.
FIX ("Cola")
SET CREATEBLOCKONEQ OFF;
"Nevada" = "Actual"->"New York" + 100;
ENDFIX
note that CrEAtEBLoCkonEQ is oFF. table 4.7 shows the results of this adjusted
formula.
Even though CrEAtEBLoCkonEQ is oFF, the budget block for nevada is created.
When there is a cross-dimensional formula, CrEAtEBLoCkonEQ does not influence
the result.
The next script is exactly the same as the prior script except that the cross-dimension
reference has been removed. CrEAtEBLoCkonEQ is still set to oFF.
FIX ("Cola")
SET CREATEBLOCKONEQ OFF;
Nevada = "NEW YORK" + 100;
ENDFIX
As can be seen in table 4.8, blocks were created for Actual, but not Budget for nevada.
In this next example, CrEAtEBLoCkonEQ is on and the cross-dimensional for-
mula has been removed.
FIX ("Cola")
SET CREATEBLOCKONEQ OFF;
Nevada = "NEW YORK" + 100;
ENDFIX
Table 4.7
Block Explosion Eliminated
Sales
Jan
Actual
Budget
Cola
Connecticut
#mi
#mi
California
#mi
#mi
oregon
#mi
#mi
nevada
101.1
101.1
California
#mi
#mi
n e w yo r k
1.1
#mi
