In SAP IBP, key figure calculations often involve disaggregation or aggregation across planning levels. Here, the task is to distribute (disaggregate) values from a higher aggregation level (PERPRODCUSTREGION, i.e., Product-Customer-Region) to a more detailed level (PERPRODCUST, i.e., Product-Customer). This is a common requirement in supply chain planning to allocate regional data to individual customer levels.
Option A: Splitting the values from detailed to aggregated level by using a copy operatorThis is incorrect because the question specifies moving from PERPRODCUSTREGION (aggregated) to PERPRODCUST (detailed), not the reverse. A copy operator typically copies values without transformation, and aggregation moves data upward, not downward.
Option B: Splitting the values from aggregated to detailed level using multiplication by the proportionsThis is correct. In SAP IBP, disaggregation can use proportional factors to split aggregated data. For example, if PERPRODCUSTREGION has a total value (e.g., 100 units), it can be distributed to PERPRODCUST based on predefined proportions (e.g., Customer A gets 60%, Customer B gets 40%). This is configured in the key figure’s disaggregation settings using a proportional calculation, a standard feature in SAP IBP’s time-series planning.
Option C: Splitting the values from aggregated to detailed level, based on the time profile attributeThis is incorrect. Time profile attributes (e.g., week, month) govern temporal granularity, not the structural disaggregation between planning levels like PERPRODCUSTREGION and PERPRODCUST. Disaggregation in SAP IBP is driven by key figure settings, not time profile attributes directly.
Option D: Splitting the values from aggregated to detailed level, based on a stored split-factor key figureThis is correct. SAP IBP supports disaggregation using a stored key figure as a split factor. For instance, a key figure like "Customer Distribution Ratio" (stored at PERPRODCUST) can define how the aggregated value (e.g., 100 units at PERPRODCUSTREGION) is split (e.g., 70 units to Customer A, 30 units to Customer B). This method is widely used in SAP IBP for precise, data-driven disaggregation, as documented in SAP’s configuration guides.
Thus, B and D align with SAP IBP’s disaggregation capabilities, leveraging proportions or stored split factors to move data from an aggregated to a detailed level.
