Key Figures
Key Figures are the core data carriers in the SAP IBP planning model, representing quantities, values, or ratios (such as demand, supply, inventory, or forecast accuracy) that planners work with across time periods and planning levels. This topic covers key figure types, storage and calculation behavior, aggregation/disaggregation logic, configuration in the planning model, and their runtime integration with Excel, Control Tower, and S/4HANA, progressing from foundational concepts to configuration decisions that affect performance and planning accuracy.
Overview
Key Figures are the core data carriers in the SAP IBP planning model, representing quantities, values, or ratios (such as demand, supply, inventory, or forecast accuracy) that planners work with across time periods and planning levels. This topic covers key figure types, storage and calculation behavior, aggregation/disaggregation logic, configuration in the planning model, and their runtime integration with Excel, Control Tower, and S/4HANA, progressing from foundational concepts to configuration decisions that affect performance and planning accuracy.
Lessons in this topic
- SAP Key Figures Tutorial (Part 1)An introduction to the concept of key figures in SAP IBP, explaining what they represent, how they differ from master data attributes, and why they are central to every planning scenario.
- SAP IBP Key Figures: Storage, Calculation and Aggregation Design (Part 2)A practical look at how key figures are configured in the planning area, including storage type decisions, formula-driven calculated key figures, aggregation/disaggregation settings, and their impact on planning accuracy and performance.
- Calculated and Global Key Figures: Formulas, Operators, and Cross-Planning-Area Reuse (Part 3)Learn how to design calculated key figures using formulas and operators, and how global key figures enable reuse of calculation logic across multiple planning areas in SAP IBP.
- 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.
Interview questions covered
- What are the core concepts of Key Figures, and how would you explain them clearly in an SAP interview?
- How would you apply Key Figures in a real SAP project? Walk through the design or implementation approach.
- A production issue is reported in Key Figures. What would you check first, and how would you troubleshoot it systematically?
- What are the most important design decisions, trade-offs, and best practices in Key Figures?
- Suppose you inherit an existing Key Figures solution. How would you review it before making a change?
- 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?
- A project encounters this situation while working on Calculated and Global Key Figures: Formulas, Operators, and Cross-Planning-Area Reuse: A consumer goods client had two planning areas: one for monthly S&OP and one for weekly supply planning. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.
- Using this SAP project situation — During a greenfield IBP implementation for a consumer goods company, the business team initially requested over 40 key figures in the demand planning model, mirroring every column from their legacy Excel forecasting workbook — explain What Are Key Figures and Why They Matter in IBP. What should happen, which concepts or process steps matter, and what common mistake would you avoid?
- 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.