Technical data

Chapter 9 Creating Hierarchies

Note. This section describes the member order as it exists within the analytic calculation engine. This internal

order may differ from the member order that is ultimately displayed to the end user.

• If the dimension is mapped to a tree, the analytic calculation engine first determines the m ember order by the

order of the detail values in the tree.

Next, the analytic calculation engine determines the member order from the order of the values as they

exist in the database.

For example, suppose a dimension is attached to a GBL tree and uses the United Kingdom node as its

hierarchy root member. This node contains detail values in this order: Cardiff, Liverpool, London,

Manchester. This dimension is also mapped to the UNITED_KINGDOM field i n the database, which

contains the Edinburgh and Glasgow values. The analytic calculation engine creates this member order

in the hierarchy:

1. Cardiff

2. Liverpool

3. London

4. Manchester

5. Edinburgh

6. Glasgow

Note. The next time the analytic calculation engine creates these members (for example, when the

application loads the analytic model), the analytic calculation engine employs the existing member

order, even if it recognizes a n ew database value that matches the name of an existing member.

For example, suppose the analytic model has already established the above hierarchy before the

application adds the Manchester value to the UNITED_KING DOM field. When the application

reloads the analytic model, the member order in this hierarchy remains; for this reason, Manchester

retains its fourth member position.

• If the dimension is not mapped to a tree, the member order is determined by the order of the members’ values

as they exist in the field that is mapped to the dimension.

Understanding the Persistence of Aggregate Data

This section discusses:

• P ersistence of aggregate and detail data.

• Aggregate record proper ties.

• Pushed down data.

• Data type considerations.

Persistence of Aggregate and Detail Data

Assuming that you selected a main record and aggregate record in the cube collection, PeopleSoft Analytic

Calculation Engine uses these records to persist aggregate data an d detail data: