Hierarchies for Cross Validations, Revaluations, and Chart of Accounts Mapping

Hierarchies you create for reporting or allocations may not be suitable for setting up cross validations, revaluation, and chart of accounts mapping rules.

For example, if you must enforce a cross-validation rule that a set of 20 departments is applicable only to a certain company, then you can group the 20 departments in a hierarchy node and refer to that hierarchy node in the cross-validation rule.

Cross Validations, Revaluations, and Chart of Accounts Mapping

For hierarchies for cross validations, revaluations, and chart of accounts mapping:

• Create hierarchies for cross validations, revaluation, or chart of accounts mapping within one hierarchy. Associate this hierarchy to the chart of accounts segment instance in the chart of accounts instance setup page. You can only associate one hierarchy with the chart of accounts instance. You can create separate root nodes for each segment of the hierarchy.

• Create an account hierarchy for each of the segments that are used in the rule set ups. Depending on your requirements, not all segments may need a hierarchy.

• Use the same child to roll up to different parents if you need different roll ups for cross validations, revaluations, and chart of accounts mapping.

• Flatten and audit the hierarchy after the hierarchies are complete and set it to an active status.

• Associate the hierarchy to the chart of accounts segment instance.

• Redeploy the accounting flexfield after the chart of accounts instance is updated.

If you have the duplicate segment values in a hierarchy, you should not publish the hierarchies to Oracle Essbase.