Table 190 shows how Essbase calculates #MISSING values. In this table, X represents any number:
Table 190. How Essbase Treats #MISSING Values
X + #MISSING | X |
X – #MISSING #MISSING – X | X -X |
X * #MISSING | #MISSING |
X / #MISSING #MISSING / X X / 0 | #MISSING #MISSING #MISSING |
X % #MISSING #MISSING % X X % 0 | #MISSING #MISSING #MISSING |
X == #MISSING | FALSE, unless X is #MISSING |
X != #MISSING X < > #MISSING | TRUE, unless X is #MISSING TRUE, unless X is #MISSING |
X <= #MISSING | (X <= 0) |
X >= #MISSING | (X >= 0) or (X == #MISSING) |
X > #MISSING | (X > 0) |
X < #MISSING | (X < 0) |
X AND #MISSING: Y AND #MISSING, where Y represents any nonzero value 0 AND #MISSING #MISSING AND #MISSING | #MISSING 0 #MISSING |
X OR #MISSING: Y OR #MISSING, where Y represents any nonzero value 0 OR #MISSING #MISSING OR #MISSING | Y #MISSING #MISSING |
IF (#MISSING) | IF (0) |
f (#MISSING) | #MISSING for any Essbase function of one variable |
f (X) | #MISSING for any X not in the domain of f and any EssbaseEssbase function of multiple variables (except where specifically noted) |
By default, Essbase does not roll up #MISSING values. However, if you always load data at level 0 and never at parent levels, you should enable the setting for consolidating #MISSING values. This setting provides a calculation performance improvement of 1%–30%. The performance improvement varies, depending on database size and configuration.
The default, not consolidating #MISSING values, must be in effect if you load data at parent, rather than child, levels, if any child member combinations have #MISSING values. If all child member combinations have any other values, including zero (0), Essbase rolls up the child values and overwrites the parent values correctly, so you can safely change the default. |