By Grégory Ponce | Principal Product Manager – Anaplan FCR.
Hello Anaplan Community!
Today, we are diving into a game-changing capability in Anaplan Financial Consolidation and Reporting (FCR): Datamodel Scalability.
If you deal with group financial consolidation and statutory reporting on a regular basis, you know how dynamic corporate requirements can be. The appointment of a new CFO, a strategic business reorganization, or evolving stakeholder expectations can trigger immediate demands for deeper analytical insights across your consolidated data.
Haven't you ever faced new leadership requests asking for a detailed breakdown of your group turnover and revenue by product line and client segment?
Let's suppose that your local ERP and source accounting systems already have this detailed data available. Then the next crucial question naturally arises:
How do I manage the addition of these new analytical dimensions in the smartest, most seamless, and peaceful way possible — without risking historical figures or rebuilding existing consolidation models?
Why Anaplan FCR is agile and evolutive
In traditional legacy consolidation applications, modifying an established data model to introduce new analytical dimensions is often a complex, high-risk project requiring extensive database schema refactoring, data migration scripts, and costly regression testing.
In Anaplan FCR, scalability is built directly into the core architecture. A data model evolution is carried out smoothly and simply by adding analytical dimensions of type 'Other'.
Figure 1: Adding new analytical dimensions of type 'Other' in the Dimensions configuration.
The essential foundation: Default input and default reporting members
When introducing new analytical dimensions, the cornerstone of the configuration is defining two mandatory anchor members for each dimension:
- Default input member: Used across all transactional and manual entry screens to receive standard entries.
- Default reporting member: Used across consolidated financial reports and aggregated statements.
These default members become selectable in the dimension properties once you have created the member hierarchy for that specific dimension.
Figure 2: Configuring Default Input Member and Default Reporting Member in dimension properties.
Why is this so critical?
Defining these two default members is what guarantees complete peace of mind during and after model evolution:
- Automated pre-population: All data entry masks (input forms) and reporting schedules are automatically pre-populated, and your existing journal entries are directly fed without requiring manual intervention.
- Zero impact on historical data: Because the enriched data model leans on the default input and default reporting members, there is zero distortion of prior periods. Your historical consolidated data remains fully intact, perfectly consistent, and directly auditable over time.
💡 Key technical reminder: AXL grid behavior
AXL input grids: Automatically apply the Default Input Member when 'Grid Properties > Behaviour > Default Member type > Input' is selected.
AXL reporting grids: Automatically apply the Default Reporting Member when 'Grid Properties > Behaviour > Default Member type > Reporting' is selected.
Step-by-step guide: The 8-step update workflow
Updating your consolidation model to integrate the new analytical dimensions requires following the 8 structured steps detailed below:
- Step 1: Add the new dimension – Navigate to dimension management and create the new analytical dimension (e.g., Products, Clients) under the 'Other' dimension type category.
- Step 2: Add members to the dimension – Populate the dimension with its required hierarchy members, ensuring you create the designated leaf elements and specifically define the default input member and default reporting member.
- Step 3: Save and process the dimension – Execute the Save and Process action to validate and commit the new dimension structure.
- Step 4: Set the leaf default input and reporting members – Adjust the dimension configuration properties to designate one of the leaf members as the default input member and default reporting member.
- Step 5: Save and process – Save and process the dimension once more to apply the updated member properties.
- Step 6: Deactivate extended drillback (if enabled) – If extended drillback is activated on your model, temporarily deactivate it, then Save and Process. This ensures schema changes proceed smoothly without locking conflicts.
- Step 7: Add dimension to model and process – Attach the new dimension to your consolidation model and run the model process action. This step executes the structural table schema adjustments in the database.
- Step 8: Reactivate extended drillback – Reactivate extended drillback ('On') and run Save and Process, restoring full transactional transparency and drill-down audit capabilities for business users.
Adjusting journal entry configuration
Once the consolidation model has been updated, the final configuration step is aligning your journal entries with the expanded dimensional structure.
Figure 3: Navigating to the journal configuration interface.
The journal configuration screen features an intelligent alert icon indicating that a structural update is required. In the screenshot below, the interface currently reflects 13 dimensions, signaling that the two newly created analytical dimensions need to be incorporated:
Figure 4: Alert icon indicating pending dimension updates in journal configuration (13 dimensions displayed).
After adding the two new dimensions, the journal configuration interface displays two new dedicated rows, automatically populated with the designated default input member in the 'default input value' column:
Figure 5: Updated journal configuration showing the two newly added dimensions and default input values.
Key takeaways
- Frictionless scalability: Easily expand your consolidation models to satisfy new executive, business unit, and management reporting requests without restructuring your core application.
- Preserved historical integrity: The default member architecture ensures that prior accounting years and historical periods remain completely stable, reconcilable, and compliant.
- End-to-end alignment: AXL data entry grids, reporting books, and journal entries adapt seamlessly across all analytical intersections without manual data patches.
- Governed execution: A clear, structured 9-step technical protocol guarantees reliable, predictable deployment with zero downtime.
Join the Community conversation
Are you already leveraging datamodel scalability in your Anaplan FCR environment? What new analytical dimensions have you recently introduced to support evolving management requirements?
Share your experiences, tips, and questions in the comments below!