Advanced Key Figure Design: Calculation Levels, Aggregation and Performance (Part 4)
Design IBP key figures with explicit calculation level, aggregation/disaggregation and storage choices so planning semantics remain correct and performant across levels.
Explanation
Key figures are the numerical measures of an IBP planning area. Their behavior depends on base planning level, storage/calculation design and aggregation/disaggregation rules.
A value meaningful at customer-product-week may not be valid to sum across every dimension. Ratios, percentages and inventory coverage require carefully designed calculations rather than default SUM behavior. Calculated key figures should reference other key figures at compatible levels to avoid unintended duplication.
Stored key figures support editable or persisted planning data; calculated key figures derive values at runtime. Overly complex nested formulas can affect planning-view performance and make troubleshooting difficult.
Disaggregation controls how a value entered at an aggregate level is distributed to lower-level combinations. The chosen method should reflect business meaning, not just system convenience.
Performance tuning starts by simplifying formulas, reducing unnecessary planning levels and limiting planning-view scope. Do not add dimensions to a planning area merely because they might be useful later.
Real project scenario
A planner entered a 10% growth assumption at region level, but a poorly designed calculated key figure summed percentages across customers. Correct calculation-level design produced the intended weighted result.
Common mistakes
- Treating every key figure as additive.
- Deep nested formulas with unclear levels.
- Adding unnecessary planning dimensions.
- Choosing disaggregation with no business rationale.
- Tuning Excel before fixing planning-model complexity.
Best practices
- Design semantics before formulas.
- Keep planning levels minimal.
- Document aggregation/disaggregation.
- Reuse clear intermediate calculations.
- Test at multiple aggregation levels.
Interview angle
Explain base planning level, stored versus calculated key figures and why percentages require different aggregation from quantities.
Practice this lesson
Quick check
1. Scenario — A planner entered a 10% growth assumption at region level, but a poorly designed calculated key figure summed percentages across customers. In this Key Figures situation, which response best addresses the underlying design risk?
2. Which key figure attribute controls how detailed values are combined when a planner navigates from a lower planning level to a higher planning level in a view?
3. Which key figure attribute defines the time granularity (such as Day, Week, or Month) at which a key figure's values are stored and processed in the planning area?
Interview questions
1. A senior architect is reviewing Key Figures. The project situation is: A planner entered a 10% growth assumption at region level, but a poorly designed calculated key figure summed percentages across customers. What design changes, validation evidence and production controls would you require before approving the solution?
Answer it in your own words first, then compare.
2. A project encounters this situation while working on Configuring Key Figures: Storage, Calculation, and Aggregation Design: In a supply planning rollout, planners reported that adjusting a monthly total supply number at the product family level produced illogical weekly splits that did not match known seasonal patterns. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.
Answer it in your own words first, then compare.
Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.