Hierarchies identify the parent-child relationships among dimension members. For example, in a Time calendar hierarchy, a year is the parent of four quarters, and a quarter is the parent of three months. Hierarchies are used to generate aggregate data and to select data.
Hierarchies are usually based on levels.
Name
A simple name.
To provide default labels, use an underscore for spaces; Analytic Workspace Manager provides initial capitals automatically. For example, cal_rollup generates the name CAL_ROLLUP and the label Cal Rollup.
ID
The fully qualified name.
This information appears on the property sheet after the hierarchy has been created; it does not appear on the initial dialog box.
Short Label
A short descriptive name for display, usually in mixed case.
Long Label
A long descriptive name for display, usually in mixed case.
Description
Additional descriptive text, which can include mixed case and spaces.
Set as Default Hierarchy
Select this option if this is the only hierarchy for the dimension, or if this is the hierarchy that will be used most frequently for analysis.
Level Based Hierarchy
Create a level-based hierarchy when the dimension has parent-child relationships that define levels, such as Month and Year, or City and Region. You must define the levels before you can finish defining the hierarchy.
Value Based Hierarchy
Create a value-based hierarchy when parent-child relationships exist, but you cannot group them into meaningful levels. For example, an employee dimension may have parent-child relationships defined in the data that identify each employee's supervisor, but these relationships may not form meaningful levels across the organization.
You can define a value-based hierarchy only when the dimension members are unique in the data source; you cannot define a value-based hierarchy for a dimension that requires the creation of surrogate keys in the analytic workspace. Level names are required for the creation of surrogate keys.
Available Levels
A list of the levels that are defined for the dimension but have not been selected for this level-based hierarchy. Use the shuttle keys to move selected levels between Available Levels and Selected Levels.
Selected Levels
A list of the levels selected for this level-based hierarchy. This list must be ordered from the highest level of aggregation to the lowest level of aggregation. A hierarchy can have a maximum of 126 levels.
To reorder the list, select a level, and click the up arrow or the down arrow to move it one place. Repeat as necessary.
The following is an example of correctly ordered levels for a Calendar hierarchy:
YEAR
QUARTER
MONTH
DAY
Copyright © 2003, 2007, Oracle. All rights reserved.