Lab A: Configure FictoCorp

Hands-on: configure and generate IFP for FictoCorp Phase 1 (Revenue/COGS + OpEx + HC)

Module 2Lab45–60 min
📖 Tell Customer Requirements FictoCorp's Phase 1 requirements — what to deploy and why the scope was chosen.
👁 Show Facilitator Walkthrough Instructor completes the first 3 questions live, then participants continue independently.
✅ Do Configure and Generate Complete all configuration questions, set hierarchy levels, and generate the FictoCorp Phase 1 application.
ℹ Lab Scope

Phase 1 deploys Revenue/COGS + OpEx + Headcount only. No CapEx model, no Balance Sheet. Lab B will extend to the full 3-statement scope.

Requirements Brief — FictoCorp Phase 1

RequirementYour Configuration Choice
Entity nameEntity — 2 levels
DepartmentYes — Department — 3 levels
GeographyNo
Functional AreaNo
VendorNo
Headcount approachOption A: IFP Role-Based HC Model
Multi-currencyYes (USD base)
Balance SheetNo
Cash FlowNo
CapEx approachOption B — GL level (delete CE after generation)
Margin planningIn FP only
Product dimensionYes — Product — 2 levels
Customer dimensionYes — Customer — 2 levels
IS list namePlanning Account IS Hierarchy (default)
Expense planningYes — Entity + Department dimensionality
Expense allocationsNo

Lab Steps

  1. Open the Application Framework — navigate to the configurator in your IFP workspace
  2. Answer Top-Level questions — use the requirements table above; pay close attention to naming
  3. Open Hierarchy Configuration — set Entity to 2 levels, Department to 3 levels; rename both to match your question responses exactly
  4. Answer FP model questions — margin in FP, Product (2 levels), Customer (2 levels), expense with Entity + Department dimensionality, no allocations
  5. Answer HC model questions — multi-currency: Yes, IS list name: default, Department: Yes, Job term: Job
  6. Generate — click Generate and monitor the logs
  7. Review generation logs — identify any errors; note items that failed to generate
  8. Delete the CE model — since we chose GL-level CapEx, the generated CE model is not needed
App Framework — Top-Level configuration questions showing Entity, Department, and dimension naming
Top-Level questions — entity and department dimension naming, multi-currency support (Yes), and other cross-model settings. Note the CUSTOM ANSWER badges where your choices differ from defaults.
Hierarchy Configuration screen — dimension list showing Entity, Department, Product, Customer, Geography, Job, Vendor hierarchies with level counts
Hierarchy Configuration — each dimension listed with its number of levels, referenced models, and last-updated metadata. Set Entity to 2 levels and Department to 3 levels for FictoCorp.
App Framework Configurations page with Generate application button visible in the bottom-right corner
Generate Application — after completing all configuration questions, click the blue Generate application button (bottom-right) to trigger model creation. Review all CUSTOM ANSWER entries before generating.

Debrief Questions

  1. What happens if the Entity name in the configuration question doesn't match the name in the Hierarchy Configuration screen?
  2. Why did we choose Option A for Headcount but Option B for CapEx?
  3. If FictoCorp later decides to add a Geography dimension, what would be the impact?
  4. What is the minimum number of hierarchy levels? Maximum?
  5. Why does the Application Framework generate a CE model even when we selected GL-level CapEx?
💡 Generation Failures

If generation fails: (1) confirm you have all 4 required roles, (2) confirm you are generating in your default tenant, (3) check PAF configuration logs to see where failures occurred.

← PreviousNext →