About Dimensions

Profitability and Cost Management uses dimensions and members created in Performance Management Architect to represent many of the structural elements of the business model in the Essbase outline:

The database outline provides the data structure for the model, and includes calculation instructions, and formulas. Dimensions in the Essbase outline are hierarchical, and data is stored at dimension intersections. Each stage in the model may include up to three dimensions.

Caution!

Members must not be repeated within the same dimension; however, the member can be repeated across several dimensions.

The following illustration shows a sample Essbase outline of a calculation database, shown on the Essbase console.

Example shows a sample Essbase outline for a calculation database on the Essbase console.

Dimensions exist as Shared or Local:

Although there is no physical limit to the number of dimensions and members that can be created, performance issues occur with large dimensional structures.

The dimensions are created and maintained in Performance Management Architect, and must exist before they can be used in models. Through Performance Management Architect, the Profitability and Cost Management Administrator can select existing dimensions and members from other products, or create new dimensions and members specifically for the model. The common data can be shared and updated between multiple products and applications. The dimensions and their members are available in the Profitability and Cost Management application after the application is deployed.

Caution!

Oracle recommends that you do not add or delete dimensions and dimension hierarchies after the modeling process has begun.

For each dimension, a dimension type and dimension name must be specified:

To enter or load a data value to an Essbase database, you assign the data value a member from every dimension in the database. This is referred to as the dimension intersection for the data value. A dimension intersection identifies a unique database location or cell.

For detailed information on creating, maintaining and working with dimensions, see the Oracle Hyperion Enterprise Performance Management Architect Administrator's Guide For naming conventions for dimensions and members, see the Oracle Hyperion Profitability and Cost Management Administrator's Guide.