1. Administrator's Guide
  2. Creating Profitability and Cost Management Applications
  3. Creating Applications Using the Profitability Applications Console
  4. Creating an Essbase Master Cube for Profitability and Cost Management

Creating an Essbase Master Cube for Profitability and Cost Management

Administrators or other users with appropriate security provisioning can create dimensions and dimension members in an Oracle Essbase Master Cube.

These are then imported into a Oracle Hyperion Profitability and Cost Management application in Profitability Applications Console. The Master Cube is an ASO Application. The same Master Cube can be used to create multiple Profitability and Cost Management applications. The application type — Standard, Detailed, or Management Ledger — is set in the Console when you create the application. It does not come from the Essbase Master Cube.

This section describes how to create Essbase Master Cubes for use with the Profitability Applications Console. To use a flat file instead, see Preparing Templates and Flat Files for Creating and Updating Management Ledger Profitability Applications.

To create the Essbase Master Cube:

  1. Create the Essbase Master database for your Profitability and Cost Management application, using the following guidelines to generate the dimensions and members for the application:

    For detailed instructions on creating applications and databases in Essbase, see the Oracle Essbase Database Administrator's Guide.

    Caution:

    The Essbase Master database name must be the same as the Essbase Master Cube name. If these names differ, users cannot update dimensions when deploying using the Profitability Applications Console.

  2. Ensure that users who will create the Profitability and Cost Management application have been provisioned as an Administrator or other user with application creation provisioning.

  3. Create the Profitability and Cost Management application.

Caution:

If you rename or delete dimensions in the Essbase Master Cube, you will no longer be able to update dimensions properly on already deployed Profitability and Cost Management applications that reference those dimensions. In other words, you should not modify in any way the UDAs that define the dimension type. If you want to rename or delete dimensions, consider creating a separate Essbase Master database so that your existing Profitability and Cost Management applications can still be updated if necessary. The existing validations in the Pre-Update Analysis option do not report these cases.

Note:

When deploying the Essbase Master Cube, the ASO dimension members and their properties, such as ASO Storage Type, ASO Formula, Hierarchy Type, and so on, are automatically read into Essbase. No manual actions are required..

BSO-specific dimension and member properties cannot be read automatically during deployment. To manage this, you must create User-Defined Attribute Dimensions (UDAs) for BSO dimension members and properties, such as Formulas, Data Storage, and Dimension Storage type. to align the BSO database with Essbase.

Note:

When a Standard or Detailed application that was created using the Master Cube method is duplicated, the Profitability and Cost Management service may need to be restarted before the cube in the duplicated application can be successfully deployed to Essbase.