Hyperion profitability & cost management

I have spent a couple of tough months trying to build a proof of concept (POC) based on Oracle Hyperion Profitability & Cost Management (HPCM).

HPCM is a piece of Oracle software designed for multi-stage allocations. Ideologically it is a pre-build decision that allows us to create an allocation model with minimum programmer involvement.

The functional scope of my POC itself was very close to a real task with allocations. It had a realistic amount of data and real dimensions.

Now I would like to summarize my gained experience and compare two different types of HPCM applications.

As you may know, there are two types of HPCM applications at the moment; standard and detailed.

The standard type of the application runs calculations on Essbase (block storage outline – BSO) and the results can be transferred to Essbase (aggregate storage outline – ASO).

Unlike standard the detailed type of application runs calculations on a relational database. It can be either Oracle or MS SQL. The results of the calculation can be transferred to ASO in order to use Hyperion Financial Reporting and Hyperion Smart View as reporting tools. Detailed HPCM seems to be a direct competitor for SAS ABM.

Also from the version the third type of application will be available, Management Ledger which will be based on ASO for calculations and reporting. But I haven’t tried this one because it hasn’t been released yet.

So I’m going to compare Standard and Detailed HPCM.

In the first place, I started with Standard. Some pros and cons became evident.

Standard HPCM disadvantages

Standard HPCM advantages

As I said I started with Standard HPCM in the first place, but I find it difficult to manage so many assignments. In addition, I do have some issues with performance. I decided to try out a detailed application.

Here are some advantages and disadvantages of Detailed HPCM.

Detailed HPCM disadvantages

Detailed HPCM advantages