Anaplan Data Orchestrator (ADO)

How ADO replaces the data hub, source-to-planning mapping, and the transformation view pattern

Module 1Platform Foundations30 min
📖 Tell What ADO Does in IFP ADO replaces the data hub model from v1.x — handling all master data and actuals loading through lightweight, centralized pipelines.
👁 Show Instructor Demo Facilitator opens ADO and shows the Source Data, Links, and Transformation Views tabs. Walks through one example link.
✅ Do Identify Your Links In your workspace ADO dataspace, how many links can you find? Which models do they push data to?

What ADO Replaces

v1.x Approachv2.0 ADO Approach
Large data hub model consuming workspace memoryLightweight mapping model — no memory overhead in workspace
Manual import actions into data hubADO links push data directly to spoke models
Source mappings in data hub modelMappings maintained in Admin model, consumed by ADO at load time
Separate admin model for master dataAdmin model is the mapping workbench; ADO is the pipeline

ADO Architecture in IFP

IFP v2.0 backend setup — model structure and ADO connections
IFP v2.0 backend setup — model structure and ADO connections

Two Types of ADO Loads

  1. Direct loads — load source data as-is (hierarchies, flat lists that don't need planning mappings). Set up once and reuse without transformation.
  2. Transformation loads — require alignment with planning structures before loading. These use transformation views to join source data with planning mappings from the Admin model.

Source-to-Planning Mapping Flow

  1. Load raw source data (accounts, departments, entities) into Admin model via ADO
  2. Map source items to planning items in the Admin model UX (Source → Planning)
  3. Re-sync Admin model datasets in ADO to pick up the updated mappings
  4. Push planning structures to all spoke models via ADO links
💡 Always Map Before Loading

Complete all source-to-planning mappings in the Admin model before pushing actuals to spoke models. Unmapped items will cause blank reports and missing data throughout FP, HC, and CE.

Transformation Views for Actuals

Loading actuals (trial balance, HRIS data) requires transformation views that join source data with planning mappings:

  1. Upload source actuals file (e.g., Trial Balance IS) to ADO Source Data
  2. Bring in mapping datasets from Admin model: SYS by Source Account IS Flat, SYS by Source Department Flat, SYS by Source Entity Flat
  3. Create leaf-level transformation views from each mapping dataset (filter: Is Leaf Level = true)
  4. Join mapping views to source file — adds planning codes to the source data
  5. Create final clean view with only required columns; change Ending Balance to float, Time Period to date
  6. Enable aggregation — combines source records mapping to the same planning dimension
  7. Map to the ADO link and push to the spoke model
ℹ Same Pattern for All Actuals

This transformation view pattern is identical for Trial Balance IS, Trial Balance BS, Trial Balance by Margin, BS Subledger, and HRIS Actuals. Only the source file columns change.

⚠️ Known Broken ADO Links

⚠ These Must Be Created Manually

The following ADO links are documented as broken or missing out of the box in IFP v2.0.0:

Financial Planning: Vendor Hierarchy
Headcount: SYS by J2 Job · SYS by J3 Job · SYS by J4 Job (no link generated at all) · Job Grade

Create all 5 manually using the ADO setup steps in the Configuration Guide before attempting data loads.

← PreviousNext →