Configuring Key Figures: Storage, Calculation, and Aggregation Design

Explanation

Configuring key figures in SAP IBP is a design activity that directly shapes planner experience, data volume, and downstream integration reliability. When a key figure is added to a planning area, the consultant must decide its category (stored versus calculated), its data type (quantity, value, or generic number), its unit or currency handling, its time and level of aggregation, and how it disaggregates when a planner enters or adjusts a value at a higher planning level than its base storage level. Stored key figures are physically persisted at a defined storage level, which is often, but not always, the most granular level of the planning level hierarchy in that planning area. A common pattern is storing Sales History at Product/Location/Week, then letting the model aggregate it upward to Product Group/Region/Month for executive-level review. Calculated key figures, by contrast, are defined through formulas referencing other key figures using the formula editor in the planning area configuration; these formulas can include arithmetic operations, time-shift functions (referencing prior or future periods), and conditional logic. A frequent real-world example is a Total Available to Promise key figure calculated from Total Supply minus Total Demand minus Safety Stock, recalculated whenever its inputs change. Aggregation mode is one of the most consequential settings. Summation is appropriate for most quantity and value key figures, but for a key figure like Forecast Accuracy Percentage or Inventory Turns, summation across products or locations produces a number with no real business meaning. In these cases, consultants typically either mark the key figure as non-aggregating for certain views, build a weighted-average calculated key figure using volume as the weighting factor, or restrict such key figures to specific reporting apps designed to handle ratios correctly. Disaggregation is the reverse problem: when a planner changes a value at an aggregated level (say, adjusting a monthly total at product group level), the system must decide how to spread that change down to the underlying weeks and individual products. IBP supports several disaggregation methods, commonly proportional to an existing baseline distribution (such as historical proportions) or even distribution across periods or members. Choosing the wrong disaggregation logic is a subtle but damaging mistake: a planner might adjust a total expecting the increase to follow historical seasonality, but if the key figure is configured for even distribution, the resulting weekly numbers can look unrealistic and erode planner trust in the system. Another important configuration dimension is the relationship between key figures across time. Some key figures need to carry forward values, such as Projected Inventory, which depends on the previous period's ending balance plus current period supply minus demand. These are typically modeled as calculated key figures using time-shift references within formulas, and they require careful validation because errors compound period over period if the formula logic is even slightly wrong. From a governance perspective, changes to key figure configuration in a production planning area are not trivial: modifying a stored key figure's storage level, or changing an existing formula's logic, can require model regeneration and reprocessing of historical data, and should go through a controlled change process with testing in a non-production tenant first. Consultants should also be conscious that heavily nested calculated key figures, especially those referencing many other calculated key figures, can slow down interactive planning views and batch jobs, so simplifying formula chains where possible is a recurring performance optimization technique.

Code example

-- Conceptual example of a calculated key figure formula in the IBP formula editor-- (illustrative syntax; actual editor uses a graphical/formula builder, not free-form code) -- Total ATP = Total Supply - Total Demand - Safety Stock RequirementTotalATP := TotalSupply - TotalDemand - SafetyStockRequirement -- Projected Inventory carried forward across periods-- References prior period's ending inventory using a time-shift functionProjectedInventory[CurrentPeriod] :=     ProjectedInventory[PriorPeriod]     + TotalSupply[CurrentPeriod]     - TotalDemand[CurrentPeriod] -- Weighted Forecast Accuracy avoids naive summation of a percentage key figureWeightedForecastAccuracy :=     SUM(ForecastAccuracy * SalesVolume) / SUM(SalesVolume)

Real project scenario

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. Investigation showed the key figure's disaggregation profile was configured for even distribution rather than proportional-to-historical-baseline distribution. The consulting team reconfigured the disaggregation setting in a sandbox tenant, validated the corrected weekly splits against three prior seasonal cycles with the business, and promoted the change through the standard transport/change process before planners resumed using the aggregated adjustment workflow with confidence.

Common mistakes

• Leaving default disaggregation settings unexamined, resulting in unrealistic period-level splits when planners adjust aggregated values • Summing ratio-based key figures like accuracy percentages or turns without a weighting mechanism, producing misleading dashboard totals • Building deeply nested calculated key figures that reference many other calculated key figures, degrading interactive planning performance • Changing a stored key figure's storage level directly in production without testing the model regeneration impact first • Forgetting that time-shift formulas for carry-forward key figures like projected inventory can silently propagate a one-time data error across all future periods

Best practices

• Explicitly choose and document the disaggregation method for every key figure planners can adjust at an aggregated level • Use weighted-average calculated key figures instead of raw summation for any ratio, percentage, or per-unit metric • Keep calculated key figure formula chains as shallow as practical to protect interactive planning performance • Test any change to stored key figure storage level or formula logic in a non-production tenant before promoting to production • Validate carry-forward or time-shifted key figures against several historical periods to catch formula errors before they compound

Interview angle

A frequent scenario-based question asks how you would design a key figure that must show a running inventory balance across weeks, or how you would handle a percentage key figure that looks wrong when viewed at a rolled-up level. Strong candidates describe the storage-versus-calculated decision, the time-shift formula pattern for carry-forward figures, and the weighted-average technique for ratio key figures, along with the governance step of testing configuration changes before production deployment.