Which statement is FALSE about running consolidations?

• A. When you consolidate an entity for a period, prior periods with Impacted calculation status are also consolidated.
• B. Running consolidation using the force Consolidate option consolidates entities with any calculation status other than OK and NO DATA.
• C. When you run consolidation for a child with Impacted calculation status, the parent entity is also re-consolidated.
• D. When you consolidate a parent with children with impacted calculation status are also consolidated.

Answer: (C)

The behavior being tested is how consolidation propagates through the hierarchy and how calculation statuses guide what gets recalculated. In FCCS, an Impacted status means data has changed in a way that affects the roll-up and requires re-consolidation, but this does not imply that simply consolidating a child will automatically re-run the parent’s consolidation. The parent’s results are updated when you explicitly consolidate the parent (or use a force consolidate that touches the parent’s pass). So the statement that running consolidation for a child with Impacted status causes the parent to be re-consolidated is not how the process works, making it false.

Context on the other options helps anchor the behavior: consolidating an entity for a period can trigger recalculation for prior periods that are marked Impacted to keep interperiod results consistent; Force Consolidate targets entities with statuses other than OK or NO DATA, forcing recalculation despite status; and consolidating a parent will include its children and reflect any impacted values in the rolled-up result.