Explanation of Consolidations,in HFM (文档 ID 585822.1)

Explanation of Consolidations, Calculations and Translations in Hyperion Financial Management (HFM) (文档 ID 585822.1)

转到底部

---

In this Document

Goal

Solution

---

Applies to:

Hyperion Financial Management - Version 1.0.0.0.00 and later
Information in this document applies to any platform.

Goal

Explanation of Consolidations, Calculations and Translations in Hyperion Financial Management (HFM).

Solution

The HFM operations, Consolidate, Calculate and Translate will only be available for Impacted members, i.e. those with a status of other than OK or OK SC. There may be situations where the user wants to re-execute one or more of these operations based on some change that has occurred in the application. For example, suppose there is logic that pulls a data value from another scenario or year within the current scenario. If this data value changes, one or more values may no longer be correct in the current year and scenario, yet the status remains OK. The user can perform a Force Calculate to re-execute the logic for the base entity of interest or force a re-consolidation to re-execute logic for all child members of the selected parent and consolidate.

Also, a change may have occurred to the application itself such as changes to the logic or metadata. This will set an OK status to OK SC, indicating that some system change has occurred since the last successful calculation, translation or consolidation and the data may no longer be correct. Knowing how the system change affected the data in the application, the user can selectively force a re-execution of logic through a Force Calculate or force a re-consolidation.

Force Consolidation can be initiated in one of two ways: Consolidate All with Data and Consolidate All. Consolidate All with Data will re-execute logic, translate and re-consolidate all entities below the selected parent with a status of OK and OK SC, ignoring entities with status of NODATA. Consolidate All will re-execute logic, translate and re-consolidate all entities below the selected parent, including entities with status of NODATA. Users should be careful when using Consolidate All because, in applications with large, extensive organizations, the consolidation time may be unnecessarily long.

A change in translation rate data is considered a system change and will set all OK statuses to OK SC. Knowing which currency was affected, the user can re-execute a translation using Force Translation. However, where the translation is part of the value dimension roll-up, translation will occur automatically during a forced re-consolidation and the user need not be concerned with Force Translate. In practice, users will utilize Force Translate for "translation-on-the-fly", i.e. for currencies as they appear in the value dimension.

Finally, the Calculate Contribution operation can be thought of as a consolidation for a single entity, where the system rolls the data up to the Contribution Total of the value dimension for the selected entity, stopping short of consolidating the data to the parent. This also has a "force" counterpart called Force Calculate Contribution, where logic and translation are re-executed for the current entity and the data re-rolled up to the current entity's Contribution Total.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/17087603/viewspace-2138919/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/17087603/viewspace-2138919/