Technical data
Creating Hierarchies Chapter 9
2003 (170)
Q1 (80)
Jan (10)
Feb (20)
Mar (50)
Q2 (90)
Apr (20)
May (30)
Jun (40)
In this example, 2003, Q1, and Q2 are non-leaf members—that is, aggregates. The numbers in parentheses to
the right of the aggregate members represent their aggregate values. The numbers in parenthesis to the right
of the nonaggregate members represent their nonaggregated values.
Understanding
Override Order of Precedence
You must understand default aggregation and the order of precedence that the analytic calculation engine uses
to override the default aggregation. When calculating aggregate members, PeopleSoft Analytic Calculation
Engine begins with the most specific override available, and then proceeds to more general overrides. The
analytic calculation engine uses this order of precedence to evaluate aggregate members:
1. If the dimension does not contain any aggregate members, use the data cube’s formula.
If the dimension does contain aggregate members, p erform one of these actions:
• If aggregate calculation is not enabled for the data cube, do not perform any more calculation
of aggregates.
Note. The analytic calculation engine generates an error when the analytic model is loaded.
• If Calculate Aggregates is selected for the data cube, perform Step 2.
2. Perform one of these actions:
Note. In either of these cases, the analytic calculation engine loads initial values from the aggregate
record when the analytic model is loaded, but overwrites the initial values upon recalculation.
• Use the cube dim
ension override user function if it exists.
This override o
perates on all of a dimension’s aggregate members for the dimension as it is attached
toaspecificd
ata cube.
For example, y
ou can create one cube dimension user function to operate on the PRODUCTS
dimension whe
n it is attached to the SALES data cube, and another cube dimension user function to
operate on the
PRODUCTS dimension when it is attached to the COST_OF_GOODS data cube.
To set a cube di
mension override user function, create a user function in the analytic model, and
then select th
e user function in the Aggregate Rule column in the Dimensions tab of the data cube’s
properties.
• If the cube dim
ension user function does not exist, perform Step 3.
3. Perform one of
these actions:
82 Copyright © 1988-2007, Oracl e. All rights reserved.