Hierarchies

In aggregate storage outlines and block storage outlines, dimensions are structured to contain one or more hierarchies of related levels and members within the levels. For example, the Time dimension in the ASOsamp.Sample database includes the hierarchies MTD, QTD, and YTD, as shown in Figure 155, Outline Showing Multiple Hierarchies and Members on the Time Dimension.

Figure 155. Outline Showing Multiple Hierarchies and Members on the Time Dimension

This image shows an outline in which the Time dimension is enabled for multiple hierarchies.

In an aggregate storage database, you can create two types of hierarchies:

The two types of hierarchies have different advantages and restrictions. A dimension may contain both types of hierarchies. To use multiple hierarchies in a dimension (even if they are all stored hierarchies), you must enable multiple hierarchies for that dimension.

  To enable multiple hierarchies for a dimension, tag the dimension member as multiple hierarchies enabled using a tool:

Tool

Topic

Location

Administration Services

Defining Hierarchies in Aggregate Storage Outlines

Oracle Essbase Administration Services Online Help

MaxL

import database

Oracle Essbase Technical Reference

When you tag a dimension member as multiple hierarchies enabled, it is automatically tagged label only.

If you do not tag the dimension as multiple hierarchies enabled, Essbase automatically tags the dimension as a stored hierarchy (except the dimension tagged as Accounts, which is automatically tagged as a dynamic hierarchy).

Note:

The first hierarchy in a multiple hierarchies enabled dimension must be a stored hierarchy.