Rules

These are the rules:

• Virtual leaf members (parent members at the selected level depth) must already have been consolidated using the same currency and rate set as the level depth consolidation
• Parent members on the starting level are never consolidated. Parent members on non-starting levels are always consolidated.
• A level depth consolidation is performed only for the selected hierarchical dimension. A currency consolidation is run for all other hierarchical dimensions. This ensures that data is generated for all combinations of members.
• Leaf members outside the scope of the consolidation are never consolidated. In-scope leaf members are optionally consolidated. To prevent unnecessary reconsolidation of these members, set SuppressLeafProcessing to 1.
• When SuppressLeafProcessing is set to 0, a currency consolidation is run on all in-scope leaf members prior to executing the level depth consolidation.
• Ownership processing is supported only if the level depth is 0. If SuppressLeafProcessing is 0, ownership data is used for roll-ups, and ownership journals are posted. If SuppressLeafProcessing is 1, ownership data is still used for roll-ups, but ownership journals are not posted.
• If the selected level depth includes only leaf members (or the selected level is 0) and:
  • SuppressLeafProcessing is set to 0, a currency consolidation is performed to avoid the additional steps required to run a level depth consolidation.
  • SuppressLeafProcessing is set to 1, a consolidation is run only for non-leaf members. This is a convenient way to consolidate hierarchies with the same leaf members as a previously consolidated hierarchy (note that unique leaf members must still be consolidated separately prior to the level depth consolidation).