Database Reference
In-Depth Information
Table 4.8
Without Cross-Dimensional Formula
Sales
Jan
Actual
Budget
Cola
Connecticut
#mi
#mi
California
#mi
#mi
oregon
#mi
#mi
nevada
101.1
#mi
California
#mi
#mi
n e w yo r k
1.1
#mi
Table 4.9
Final Block Creation Results
Sales
Jan
Actual
Budget
Cola
Connecticut
#mi
#mi
California
#mi
#mi
oregon
#mi
#mi
nevada
101.1
100
California
#mi
#mi
n e w yo r k
1.1
#mi
The blocks for nevada were created for Actual and Budget as shown in table 4.9. This
example is how CrEAtEBLoCkonEQ should work.
4 .7. 6 . 3
CREATENONMISSINGBLK When Nothing Else Works
the Cr EAtEnon
mISSIngBLk statement is the “last resort” option. not only can this statement cre-
ate more blocks than you need, it also creates them slowly. This command follows the
outline processing the “potential” blocks according to the FIx statement. Each potential
block is loaded into memory. When all of the blocks have been consumed by the fix,
Essbase then writes any block that has a value. Blocks that are entirely empty are dis-
carded, hence, the name CrEAtEnonmISSIngBLk. Essbase will then log a message
specifying the number of missing blocks that were
not
written back. use this feature only
in FIx statements that tightly control the number of blocks being processed.
one might ask why use a command that has so many negative side effects? The
answer is that sometime there is no other way. table 4.10 shows the results of the script
below. note that the formula result is a dense member and the formula itself has cross-
dimensional references.
FIX (Budget);
SET CREATENONMISSINGBLK ON;
(Sales=Sales->Actual * 1.1;
Misc = Misc->Actual * .95 ;)
ENDFIX
Budget data blocks were created where actual data existed. Blocks where the formula
resolved to #missing did not get created. The following log message specified the num-
ber of blocks that were calculated in memory, but were not written.
Total #Missing Blocks Not Written Back: [4.5000e+002] Blocks
