Rules

Rule Considerations: 1. Rules are executed when users perform calculations, translations, consolidations,

and allocations. Calculation rules execute one time for each Entity/Value dimension intersection to which the calculation or consolidation applies. See “Calculation Rules with Calculation Commands” on page 208. 2. The dimension dimension members members to to which Financial Management applies calculations calculations depend on the data grid cell where the user’s cursor is placed and the members specified in the Point of View bar. See “Current Dimension Members” on page 212. 3. When a function puts data into a currency-related Value member, member, Financial Management might delete the current value in the Value member. See “Functions Automatically Clear Data” on page 214.Rule considerations 207 a nd there is a set order in which 4. Rules execute in sequential order within a routine and routines run before other routines. See “Rule Execution During Consolidation” (pg215)

Rule Execution during Consolidation: During the consolidation process, rules are executed in a pre-defined sequence. For each base child of a given parent, the calculation sequence for the various elements in the Value dimension takes place in this order: 1. Accounts defined as IsCalculated Is Calculated in the metadata are cleared in EntityCurrency. 2. Accounts defined as IsCalculated Is Calculated in the metadata are cleared in EntityCurrAdjs. 3. The Sub Calculate() routine is executed on EntityCurrency. 4. The Sub Calculate() routine is executed on EntityCurrAdjs. 5. The ParentCurrency data is cleared. 6. Default translation is applied to all accounts defined as Revenue, Expense, Asset, and Liability for the total amount of EntityCurrency and EntityCurrAdjs. EntityCurrAdjs. For accounts with attribute Flow or Balance, the total amount of EntityCurrency and EntityCurrAdjs is rolled up into Parent Currency. 7. The Sub Translate() routine is executed. 8. The Sub Calculate() routine is executed on ParentCurrency. 9. Accounts defined as “IsCalculated” “IsCa lculated” in the metadata are cleared in ParentCurrAdjs. 10. The Sub Calculate() routine is executed on ParentCurrAdjs. 11. Accounts defined as “IsCalculated” in the metadata are cleared in ParentAdjs 12. The Sub Calculate() routine is executed on ParentAdjs. 13. Proportion and Elimination data are cleared. 14. Default consolidation and eliminations are performed for the total amount of Parent and ParentAdjs. 15. The Sub Calculate() routine is executed on Proportion and Elimination. 16. Accounts defined as “IsCalculated” in the metadata are cleared in ContributionAdjs. 17. The Sub Calculate() routine is executed on ContributionAdjs. After the previous steps have been repeated for each base child, this sequence takes place for the parent entity: 1. The EntityCurrency data is cleared. 2. The sum of the total of Proportion, Elimination, and ContributionAdjs for every child is written into EntityCurrency of the parent entity. 3. The Sub Calculate() routine is executed on EntityCurrency. 4. Accounts defined as “IsCalculated” “IsCa lculated” in the metadata are cleared in EntityCurrAdjs.

5. The Sub Calculate() routine is executed on EntityCurrAdjs. Note: If a parent is further consolidated into another parent, this sequence continues with step 5 from the child consolidation sequence.

Conditional Rules  You may want a rule to execute an action only when certain dimension members are the current members in the Point of View. For example, you might want an account’s value to be calculated in one way when Actual is the current scenario and a different way when Budget is the current scenario. Tip: For information on how Financial Management determines the current dimension members, see “Current Dimension Members  To do this, use the Member function in a VBScript If structure. Member gets the name of  the current member of these dimensions: Entity (Use the Entity object to get the current entity or the Parent object to get the parent of the current entity) Period Scenario Value  Year If structures enable you to execute statements only if certain conditions are true. The following sections show a few different ways of using Member with If structures to test for dimension members. •

• • • •