1. User's Guide
  2. Working with Standard Profitability and Cost Management Applications
  3. Getting Started with Standard Profitability and Cost Management
  4. Comparison between Standard and Detailed Profitability Applications

Comparison between Standard and Detailed Profitability Applications

The type of application that you select depends on the type of modelling that you require to effectively manage your organization's models.

The following table compares features and abilities of two types of Oracle Hyperion Profitability and Cost Management applications:

  • Standard Profitability

  • Detailed Profitability

Depending on the application, you may use one or the other.

Note:

For a description of the third type of application, Management Ledger Profitability, see Management Ledger Profitability and Cost Management Applications.

Table A-1 Comparison between Standard and Detailed Profitability Applications

Feature Area Standard Detailed
General Application Information
Primary Use Cost Development Cost and Revenue Application
Focus Contribution analysis Profitability analysis
Database Oracle Essbase and Relational databases

Relational database only.

The pre-existing customer database is mapped to Detailed Profitability
Volume of Target Objects Hundreds of thousands to millions of unique targets as defined by dimension intersections in the target model stages.

Practical limits are based on dimension sizes, with dimensions larger than 25,000 members considered to be very large.

 Millions to hundreds of millions of unique targets as defined by row count in the target table.

Practical limits are not bounded by dimension sizes because the target row is not required to be defined by a unique intersection of dimensions.

Allocations
Type of Allocation

Multi-Step allocations

For example, you can follow allocations from department to department, department to activity, product and so on.

Single step allocation of pools or rates to profit objects

May use data from Multi-Step Standard model or external data
System Dimensions

Measures

AllocationType

MeasuresDetailed
Genealogy Allocations Yes No
Trace Allocations Yes No
Intrastage Allocations Yes No
Reciprocal Allocations Yes No
Model Building
Stages Up to nine stage, with up to 3 dimensions in each stage Only two stages:

  • Source - Up to 5 Source Dimensions

  • Destination - Up to 25 Destination Dimensions
Model Layers Cost and Revenue No
Data Entry Yes No
Pre-Defined Driver Measures Yes No
Driver Data Report Yes No