Which statement correctly describes the Consolidation dimension?

• A. The dimension aggregates input, consolidated, and eliminated data together
• B. The dimension allows users to see input versus journal adjustment data
• C. The dimension uses a separate member for data from an entity's level zero descendants
• D. The dimension contains members to store non-controlling interest and joint venture data

Answer: (C)

Consolidation requires bringing together data from all entities that roll up to a parent, and FCCS provides a special place to hold data originating from an entity’s level-zero (leaf) descendants. This separate member for level-zero descendants lets you isolate the leaf data and then roll it up through the consolidation process with the correct adjustments and eliminations applied at the appropriate levels. It ensures the leaf-level figures are preserved for accurate parent-level calculations and for applying consolidation rules to the entire subtree.

Why this is the best fit: having a dedicated member for level-zero descendants directly supports accurate roll-up and consolidation of hierarchical data, which is the core purpose of the Consolidation dimension. The other statements don’t capture this specific mechanism—consolidation isn’t defined by combining input, consolidated, and eliminated states in one place, nor by exposing input versus journal adjustments in the consolidation dimension, and while non-controlling interest and joint venture data relate to ownership, they aren’t described by this particular level-zero descendant member.