..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 11.1.1.3, the name must be unique and can contain up to 80 characters,

...locking entities in HFM

Hi all,

Recently, I was working on an assignment to start locking the entities in an HFM application with 8 scenarios, 9 years of data and 600 base entities.

The options were the following:

1. Should we lock only the base entities?
2. Should we lock both the base entities and the parents?
3. Should we not lock anything? 

In the end, we decided that the best approach is