Aggregation
Normally, values in a table are aggregated along the hierarchy but sometimes exceptions are necessary.
Aggregation of values in a hierarchy is determined by the Aggregation type setting, which is applied to each account member in Modeler. Typically, values are summed up into higher-level totals.
No Aggregation
In some situations, it is not possible to simply aggregate values; this would be true, for example, when working with different currencies, or if values are expressed in different units that are not compatible with each other. In these cases, a parent cell may be displayed as empty, or a common value appear in the cell, but it isn't a simple aggregation.
In order to make these cells recognizable, the cell is shown with a diagonal line drawn through it, and a help message is available to explain the data. Select the notification symbol next to the cell to see the explanation.
Aggregation for Analytic-type Models
For analytic models, values can be booked to parent nodes in a hierarchy. In this case, the node shows the sum of the booked value plus the sum of the child values. (For planning models, this situation only occurs when working with different hierarchies for the same dimension. See Entering Values with Multiple Hierarchies and Disaggregation of Values During Data Entry for more information.)
Example
A value of 30 has been booked to the parent node Sales Expenses. The value shown in the table cell is 50; this figure includes the aggregation of two child accounts.
Sales Expenses 50
– Travel Expenses 10
– Other Expenses 10