...FDM reclassifications with logic accounts

I was recently discussing (with my wife) about the various HFM reclassification journals (VAT, Corporate tax, Cash/Overdraft) and it occurred to me that the easiest way to complete this task is with the proper configuration and design of the FDM application.

Proem

When designing an FDM – HFM solution, my understanding is that FDM should be used to replace all the manual, time consuming, non-value-added data-management steps of the ETL process while moving data from the ERP to HFM.

This design has 2 main guidelines:

• The extract query from the ERP system should not exclude any of the data. The main reason of this guideline is to prevent the exclusion of any future ERP changes to be extracted in the extract file.

..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,