Technical data

ManualsBrandsSimplicity ManualsDo-It-Yourself tools4564

111

112

113

114

115

116

117

118

119

120

Chapter 9 Creating Hierarchies

• If you select to persist only the root aggregations of the D EPT_TREE dimension and to persist none

of the aggregates of the DATE_TREE dimension on the Dimensions tab of the cube collection’s

properties, the following rows are persisted in the aggregate record:

Note. Italicized values are the actual persisted aggregate members. The Fully Qualified Member

Name field is not a database value.

Fully Qualified Me mber Name DEPARTMENT TREE_DATE NUM_SALES

GBL

CAL2004.JA N . 2004–01–01

GBL 2004–01–01 13

GBL

2004–01–02

GBL 2004–01–02 2

GBL

2004–02–01

GBL 2004–02–01 16

Example: Creating Overrides

Thi

s section provides an example of creating overrides and discusses the affect of dimension order on

lculation.

The following table describes the three dimensions used in this example. The first column lists the names

of the dimensions. The second column lists the dimension order, which determines calculation priority.

The third column lists the dimension override functions that are used if member override functions do not

exist for the children of the parents in the dimension:

Dimension Dimension Order/Priority

Dimension Override User

Function

ACCT 1 <ACCT_DIM_DEFAULT_

FORMULA>

TRANS_DATE 2 <NONE>

DEPT

3 <DEPT_D IM_DEFA ULT_

FORMULA>

The following table describes the hierarchy of the ACCT dimension that is associated with the AcctTree tree.

The first column lists the parents in the hierarchy. The second column lists the children of the parents. The

third column lists the member override user functions that are performed on each c hild.

Note. Overrides are not performed on cells denoted (leaf) or <none>.

Parent Child

Member Override User

Function

100 110 <SALES_ACCT_SUM>

100 110 <DIRECTOR_ACCT_SUM>