1. Administrator's Guide
  2. Working with Management Ledger Profitability
  3. Understanding Management Ledger Dimensions
  4. Management Ledger Business Dimensions

Management Ledger Business Dimensions

Business dimensions describe the business-specific objects within the model, such as products, customers, regions, and employees.

Business dimensions may use some or all of the following dimension types, and may apply to one or more models:

  • Generic

  • Account

  • Entity

  • Country

When the Oracle Essbase outlines are deployed, the business dimensions are created in the Oracle Hyperion Profitability and Cost Management application as basic or generic dimensions, with no type. This feature enables Profitability and Cost Management to reuse the dimension member and hierarchies that were defined for other applications, such as Oracle Hyperion Planning.

Note:

This dimension type does not apply to aggregate storage outlines.

The Management Ledger Rule and Balance dimensions are system dimensions that are seeded and should not be edited in any way, even if some part of the system allows it (for example, Update Dimensions in the Profitability Applications Console). These dimensions are reserved for system use.

Business Dimension Requirements

When creating a business dimension for a Management Ledger application, the following requirements apply:

  • The first Gen2 child under the Gen1 dimension name is usually set to an All member. For example, AllDepartments for the Departments dimension.

    The primary hierarchy is hosted under the first Gen2 child. Only the first Gen2 hierarchy is used in allocation modeling, and this hierarchy cannot contain shared members.

  • Additional Gen2 members can host alternate hierarchies, but these hierarchies are not used in allocation modeling. If the dimension is going to host alternate hierarchies, set the Dimension HierarchyType to "Enabled", the first Gen2 member HierarchyType to "Stored" and the Gen2 member with alternative hierarchy with shared members to "Dynamic"

    These alternate hierarchies are not visible in Profitability and Cost Management modeling screens, and can only be viewed in Essbase.

Note:

In Management Ledger business dimensions, do not make shared members that reference non-level-0 base members. Doing so will cause the Copy POV and the calculation operations to fail because sharing with such references creates situations where Profitability and Cost Management needs to write to non-level-0 members, which is not supported in Essbase for ASO cubes.