Saturday, 30 November 2013

..designing a scenario

Hi all,

In this post I am trying to clarify my thoughts regarding the Scenario dimension.

The scenario dimension in HFM holds the different data sets reported by the group. Despite the fact that scenario dimension has usually up to ten members, it is one of the most important dimensions of the application. The reason is that the scenario dimension defines the input frequency (month-to-date, quarter-to-date or year-to-date), the calculation sequence between Periodic and YTD for the flow accounts, the process management, the data audit and the execution of the consolidation rules.

From a functional perspective, the most common scenarios that I have seen up to today are:
  • Flash
  • Actual
  • Budget
  • Forecast
  • Translation scenarios of the previous data sets
Following, I have a quick description of the scenario dimension setting. The description is based on my experience, on the HFM admin manual and on discussions that I had with other consultants.

1. Member or Label or Name:

The name or the label of the scenario. After version, the name must be unique and can contain up to 80 characters,

Sunday, 24 November 2013

Next post is coming…

Hello all,

It was an HFM update period for my company…As a result, all the effort was focused on the update and I postponed the publishing of the post… The subject will be the scenario dimension.

See you soon,


Saturday, 9 November 2013

..HFM project steps

     Hi all,
    The topic that I had in mind the last two weeks is related with the question of how to build the best project plan for a Hyperion project (HFM or Essbase). I believe that this is a question that most of the consultants have at least one time in their life after completing 4 or 5 Hyperion projects.
    Based on a my experience, the best approach to build a project is: 

Saturday, 2 November 2013

..Value dimension

Hi all,

In 2008, I was asked to train the admin users of a financial group and explain them how their future application will work. Everything was really simple until I started thinking on how to present the Value dimension… since then I keep on trying to find the best way to present the Value dimension. So, I will start with the basics and then try to present my understanding on more complicated points.


The Value dimension is not used for a single purpose. The three purposes that I have identified are:

  1. It is used to store and identify the different types of data within HFM (data and journals).
  2. It is used to translate the values from local currency to parent currency and eventually calculate the contribution to the parent entity.
  3. Finally, it is used to maintain all the foreign currencies that the application can support.


The Value dimension is a system defined dimension. The Value dimension members are


Hi all, This is a post that I have in mind to write for at least 6 months but I kept on postponing due to the project... B...