1. Administrator's Guide
  2. Working with Detailed Profitability
  3. Working with Detailed Profitability and Cost Management Dimensions and Metadata
  4. About Detailed Profitability Dimensions and Metadata

About Detailed Profitability Dimensions and Metadata

Detailed Profitability enables you to use the existing relational database as the starting point for your Detailed Profitability application.

Dimensions and metadata are created and maintained by the Oracle Hyperion Profitability and Cost Management Administrator, using the Profitability Applications Console. By using common dimensions and members, Profitability and Cost Management can easily use and transfer common data with other products, such as Oracle Hyperion Planning, saving time and effort, and improving accuracy. For detailed information on creating and maintaining dimensions and metadata, see Creating Applications Using the Profitability Applications Console.

Profitability and Cost Management uses the dimensions and members created in the Profitability Applications Console to represent many of the structural elements of the business model. During creation of the Detailed Profitability application, the following dimensions are selected.

  • MeasuresDetailed (required): A reserved dimension that contains the allocation members require to support stage balancing and other verification activities. Provides the structure for the model and scenarios This dimension does not contain driver measures.

  • At least one POV dimension (required): Time periods, scenarios and versions

  • At least one Business Dimension (required): Reflects the business-specific elements of the model, such as departments, General Ledger accounts, activities, customers, or products

  • Alias Dimension (optional)

  • Attribute Dimensions (optional)

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

  • Dimension type is a dimension property that enables the use of predefined functionality for selected dimensions.

  • Dimension name is assigned to identify the contents of the dimension, in relation to your organization or business. For example, a dimension of Account type may be given a dimension name, such as General Ledger or Chart of Accounts. The dimension name does not need to reflect the dimension type, although it may. For naming restrictions, see Essbase Naming Conventions.

Caution:

Although there is no physical limit to the number of dimensions and members that can be created, performance issues occur with large dimensional structures. Creating additional dimensions or members after the application has already been deployed may require re-registration in Model Data Registration in order for the new objects to be used.

For detailed instructions on creating and maintaining the dimensions and members, see Creating Applications Using the Profitability Applications Console.