Formulas Notes

· Describe the purpose of each function.

· Describe how to create category-specific formulas.

Category specific formulas are created by entering the formula a category column in the Method window.

· Given an exhibit of an entity's attributes and formula statements, define the expected results of running the default chart method for that entity.

[]

· Identify the results that should appear at various levels of the organization for an account that appears in formulas.

[]

· Correctly identify where CHARTDSM is used.

This method calculates the proportion, contribution, translation, parent adjustment, and elimination detail.

· Define where formula statements should appear given a set of requirements for which calculations must take place.

[]

· Given specific functions, identify which can or cannot be used in particular types of methods.

[]

· Determine the proper order of execution within DSM.

The order methods are executed within DSM is:

1. None Detail is calculated using all Chart methods except CHARTDSM.
2. Translation Detail is calculated using all Translation methods.
3. Consolidation Detail is calculated using all consolidation methods.
4. Elimination Detail is calculated.
5. Adjustments Detail is posted from Journals.
6. Contriduction Detail is calculated from None, Translation, Consolidation, Elimination and Adjustment Detail.
7. CHARTDSM Method is calculated for all detail except None.

· Define the purpose of update rules and where in the DSM information can be written.

Update rules are special functions that defines the ID for a group of formulas used to distribute values to accounts in other entities. Update rules are only used in consolidation methods.

Describe what happens during a standard consolidation if data is written to a "partner elimination" outside the branch of the organization chart that is currently being consolidated.

[]

Describe valid update rule keywords.

[]

· Describe the effects in the system of changing the default chart method.

The default chart method is CHART and the formulas in it apply throughout applications. Changes to CHART will therefore affect how all totals and values are calculated. Except where CHART is repalced by custom chart methods.

· Define system maintenance that will require formulas to be rechecked.

Formulas need to be checked when:

• Accounts are changed (system automatically prompts and checks methods)
• Application currency settings  are changed (system automatically prompts and checks methods)
• Categories are changed (system automatically prompts and checks methods)
• Methods are changed
• Methods are loaded

· Describe the ACE approach to logic (data in source accounts).

The Statutory Consolidation Engine (ACE) is an Hyperion Enterprise add-on that can improve consolidation performance when an application has a sparse data, and one or more of the following apply:

• The size of the chart of accounts is inflated by an extensive use of intercompany details.
• Conditional rules must be defined for intercompany transactions.
• Complex consolidation methods must be defined to calculate item and consolidation reserves, and to generate a detailed audit trail of the consolidation process.

ACE improves the performance of Hyperion Enterprise by:

• defining formulas by source account rather than by destination account.
• performing impacted consolidations by dependent rather than by parent.

For example the formula #X=#Y-#Z would be implemented in ACE as add the value in #Y to #X and subtract the value in #Z from #X.

· Describe how to build and maintain logic in the ACE Administration Module.

[]

· Describe how to calculate currency translation adjustments (including movements).

Currency translation adjustments can be calculated in the CHARTDSM method.

· Describe the effect of child rate accounts on currency translation.

Child Rate Accounts let you use non-global exchange rates for entities.