Calculation Rules with Consolidation Commands

When a user selects one of the Consolidate commands, Oracle Hyperion Financial Management runs the Calculation rule for several of the Value dimensions that intersect each previously unconsolidated child entity. After executing for the children, Financial Management runs the rule for the intersection of the parent entity and the member of the Value dimension for the parent’s default currency.

1. The rule is run for the intersection of the child entity and the Value member that stores the child entity’s default currency (Entity Currency).

2. If the child entity’s AllowAdjs attribute is set to Y, the rule is run for the intersection of the child entity and the Value member that stores adjustments in the child entity’s default currency (Entity Curr Adjs).

3. If the child’s currency differs from the parent’s currency, the rule is run for the intersection of the child entity and the Value member that stores amounts translated to the parent’s home currency (Parent Currency).

4. If a child’s currency differs from the parent’s currency and the rules file contains a Translation rule, Financial Management executes the Translation rule before step 3.

5. If the child’s currency differs from the parent’s currency, and the child entity’s AllowAdjs attribute is set to Y, the rule is run for the intersection of the child entity and the Value member that stores adjustments translated to the parent’s home currency (Parent Curr Adjs).

6. If the parent entity’s AllowAdjFromChildren attribute is set to Y, the Logic rule is run for the intersection of the child entity and the Parent Adjs value.

7. The rule is run for the intersection of the child entity and the Proportion value.

8. The rule is run for the intersection of the child entity and the Elimination value.

9. If the parent entity’s AllowAdjFromChildren attribute is set to Y, the rule is run for the intersection of the child entity and the Contribution Adjs value.

10. For each additional child entity that contains previously unconsolidated data, repeat steps 1 through 9.

11. The rule is run for the intersection of the parent entity and the Value member that stores the parent entity’s default currency.

Example

For example, a parent entity named UnitedStates has children named EastUS and WestUS. The children have the AllowAdjs attribute enabled. The UnitedStates entity has the AllowAdjs and the AllowAdjFromChildren attributes enabled. All three entities share a default currency of USD.

If you change data for EastUS and WestUS and consolidate UnitedStates, Financial Management runs the rule for each of these intersections of the Entity and Value dimensions:

1. EastUS and Entity Currency.

2. EastUS and Entity Currency Adjs. (EastUS’s AllowAdjs attribute has been set to Y.)

3. EastUS and Parent.

4. EastUS and Parent Adjs. (UnitedStates’ AllowAdjFromChildren attribute has been set to Y.)

5. EastUS and Proportion.

6. EastUS and Elimination.

7. EastUS and Contribution Adjs. (UnitedStates’ AllowAdjFromChildren attribute has been set to Y.)

8. WestUS and Entity Currency.

9. WestUS and Entity Currency Adjs. (WestUS’s AllowAdjs attribute has been set to Y.)

10. WestUS and Parent.

11. WestUS and Parent Adjs. (UnitedStates’ AllowAdjFromChildren attribute has been set to Y.)

12. WestUS and Proportion.

13. WestUS and Elimination.

14. WestUS and Contribution Adjs. (UnitedStates’ AllowAdjFromChildren attribute has been set to Y.)

15. UnitedStates and Entity Currency.

Following are examples of the consolidation process.

The first example shows the process when the entity currency and the parent currency are different.

The following example shows the process when the entity currency and the parent currency are the same.