BSo Will never Die and here Is Why - Developing Essbase Applications - page 142

Table 4.11 Correct Values with Cell Mode

Cola Sales

Jan Feb Mar Qtr1

Budget Budget Budget Budget

nevada 10 10 20 40

Table 4.12 Incorrect Values with Block Mode

Cola Sales

Jan Feb Mar Qtr1

Budget Budget Budget Budget

nevada 10 #mi #mi 10

table 4.11 shows the correct values. First Jan is set to 10, Feb = 10 + #missing,
and mar = 10, 10. After clearing Jan:mar and changing @CALCmoDE (CELL) to @
CALCmoDE (BLoCk), the script is rerun.
In this case, the values in table 4.12 are incorrect. It looks as though Jan was calcu-
lated after Feb and mar when block mode is used. When Essbase encounters certain
functions, it does not know that there is a dependency. It errs on the side of caution just
in case. If the developer knows that there is no dependency, it is permissible to override
the mode taking advantage of the performance benefit.

4.8 Bso matters anD then some
Despite BSo Essbase being almost old enough to buy a drink, there are still misun-
derstandings, misconceptions, and plain misuse of the tool. I hope that this chapter
has helped clear up some of the common and maybe not so common areas of BSo's
sometimes mysterious workings and given you clear guidance on BSo good practices.
BSo Essbase will be with us for some time to come and indeed shows no sign of
slowing down within Planning. Where it makes sense, it is an incredibly powerful and
useful tool. I hope that this chapter helps you maximize Essbase's original data storage
option.