Application Framework Walkthrough

Every configuration question — options, implications, and what to choose for FictoCorp

Module 2Configuration Workshop45 min
📖 Tell All Config Questions Walk through every question in the Application Framework — what each controls and the trade-offs of each option.
👁 Show Instructor Demo Facilitator opens the Application Framework and walks through each question section without yet answering them.
✅ Do Preview FictoCorp Config Using the FictoCorp requirements, write down your answers to the Top-Level questions before starting Lab A.

Top-Level Configuration Questions

Application Framework overview — 43 configuration questions organized across Top Level, Financial Planning, Headcount, and CapEx sections
Application Framework overview — 43 configuration questions across 4 sections; the Configurations tab shows Top Level, Financial Planning, Headcount, and CapEx sub-sections
Application Framework — Financial Planning model-specific questions including currency translation and balance sheet options
Financial Planning section — questions cover currency support, headcount approach, CapEx planning method, and balance sheet/cash flow options
Application Framework Configurations — top-level questions showing Entity dimension name fields (capital and lowercase), Department dimension toggle, and Geography option
Top-level configuration questions — entity dimension name, department dimension toggle, and optional dimension settings; note the capital/lowercase name pairs required for case-sensitive substitution

These questions define the foundational structure applied across all 4 models.

Entity Dimension

SettingDetails
What it isMandatory — your primary organizational hierarchy (e.g., Business Unit, Company, Legal Entity)
What to configureName (capital + lowercase versions) + number of levels in hierarchy screen
ImpactUsed in Admin, FP, HC, CE — core dimension for all aggregation and reporting
⚠ Critical Naming Rule

Use the EXACT same name in both the question response and the hierarchy rename. A mismatch causes modules and line items to not be renamed correctly throughout the model.

Department Dimension

OptionImplication
Yes — includeSeparate dept hierarchy created in all models; enables 2D planning (entity × dept); increases model size
No — excludeSimpler model; planning only by Entity; choose for simple or small implementations

Optional Dimensions

DimensionUsed InInclude?Exclude?
GeographyRevenue/COGS, OpEx, Top-DownMulti-dimensional planning; more complexitySimpler model; less dimensional granularity
Functional AreaOpExEnables expense tracking by functionOpEx by dept only
VendorOpExEnables vendor-level expense trackingNo vendor dimension in OpEx
⚠ Removing Dimensions Later Is Painful

Removing a dimension after generation affects ALL areas of the model that use it. Make dimension decisions upfront — changing them later requires re-generation and re-doing all post-gen work.

Headcount Planning Approach

OptionWhat Gets DeployedWhen to Choose
Option A: IFP Role-Based HC ModelFP + HC models active; job-level HC costs flow into FPDefault for most implementations — best practice
Option B: GL-Level Planning in FPFP + HC generated; HC deleted after; HC expenses entered at GL level in FPSimpler — for customers who don't need job-level detail
Option C: External Model → Load to FPFP + HC generated; HC deleted; summarized HC loaded from OWP or externalWhen OWP or another model is the HC system of record

Multi-Currency

OptionImplication
YesReporting Currency dimension added; FX rates required; triangulation enabled
NoSingle currency; simpler but not suitable for international organizations

Balance Sheet & Cash Flow

SettingOptions
Balance Sheet in FP?Yes = Admin + FP include BS accounts and logic / No = P&L only
Cash Flow Reporting?Yes = indirect cash flow statement generated / No = CF excluded

CapEx Planning Approach

OptionWhat Gets DeployedWhen to Choose
Option A: IFP CapEx ModelFP + CE models active; asset-level CapEx detail flows into FPAsset-intensive businesses needing depreciation modeling
Option B: GL-Level Planning in FPFP + CE generated; CE deleted; CapEx entered at GL account levelSimple CapEx needs without asset-level detail
Option C: External Model → Load to FPFP + CE generated; CE deleted; summarized CapEx loaded externallyWhen another system manages CapEx

Financial Planning Model Questions

Margin Planning Approach

OptionDescription
In FP OnlyFull Revenue/COGS planning within FP model — most common
Another Model → Load to FPCMP or external; results loaded via DAT Margin Planning Import module
CombinationSome in FP, some loaded from external source
Expense OnlyAll margin components excluded; FP focuses on OpEx only

Key FP Questions Summary

FictoCorp Configuration Preview

QuestionFictoCorp Answer
Entity nameEntity (2 levels)
DepartmentYes — Department (3 levels)
GeographyNo
Functional AreaNo
VendorNo
HeadcountOption A: IFP Role-Based HC Model
Multi-currencyYes — USD base, USD/EUR/GBP reporting
Balance Sheet (Lab A)No
Cash Flow (Lab A)No
CapEx (Lab A)Option B — GL level; delete CE after generation
Margin planningIn FP only
ProductYes — Product (2 levels)
CustomerYes — Customer (2 levels)
IS list namePlanning Account IS Hierarchy (default)
Expense planningYes — Entity + Department dimensionality
Expense allocationsNo
💡 Lab A Scope Reminder

Lab A deploys Revenue/COGS + OpEx + HC only. Lab B will add CapEx, Balance Sheet, Cash Flow, and Geography. Answer the questions above for Lab A first.