SAP C_IBP_2502 - SAP Certified Associate - SAP IBP for Supply Chain

Rolling aggregation in SAP IBP refers to calculating a cumulative or moving total across a time horizon (e.g., year-to-date sales). This is a common requirement in planning and reporting, achieved through specific configuration methods.

Option A: Using an attribute as a key figureThis is incorrect. Attributes as key figures provide static values (e.g., Product Category), not dynamic time-based aggregations like rolling totals.

Option B: Using an appropriate period weight factorThis is incorrect. Period weight factors adjust proportional disaggregation (e.g., splitting monthly data to weeks), not rolling aggregation across periods.

Option C: Using a key figure calculationThis is correct. Rolling aggregation is achieved in SAP IBP via key figure calculations, such as the CUMULATE function (e.g., KF2 = CUMULATE(KF1)), which sums values from the start of the horizon to the current period. This is configured in the Planning Areas app and is a standard method for time-series calculations, per SAP IBP’s official documentation on key figure calculations.

Option D: Using a local memberThis is incorrect. Local members in the Excel add-in allow ad-hoc calculations within a planning view, but they are user-specific and not a system-configured method for rolling aggregation across the planning area.

Thus, C is the correct method for achieving rolling aggregation, aligning with SAP IBP’s calculation capabilities.

This scenario involves optimizing resource use with a minimum threshold, potentially overproducing, in SAP IBP’s supply planning, per its documentation.

Option A: Excess stock can be generated and will need to be staged in an overflow warehouseThis is correct. Overproduction to meet minimum use generates excess stock, requiring storage (e.g., overflow warehouse), a practical outcome, per SAP IBP’s planning behavior.

Option B: Capacity leveling will be possible for production and storage resourcesThis is incorrect. Capacity leveling (smoothing production) is a PP/DS feature, not standard in IBP’s time-series planning.

Option C: Balance can be achieved between excessive prebuild and minimum use by incorporating violation costsThis is correct. The Supply Optimizer can balance minimum utilization (via costs) and excess production (via inventory costs), a supported solution, per SAP IBP’s optimization features.

Option D: Minimum capacity utilization will result in pull productionThis is incorrect. Pull production (demand-driven) contradicts producing beyond demand; this scenario aligns with push logic.

Thus, A and C apply, per SAP IBP’s official supply planning capabilities.

In SAP IBP, the "Attribute as Key Figure" feature allows master data attributes (e.g., Product Category) to be used as key figures, configured in the Planning Areas app, per SAP IBP’s documentation.

Option A: This type of key figure is not usually stored and it cannot be editableThis is incorrect. Attribute key figures are stored (sourced from master data) and can be editable if configured as such, not inherently non-editable.

Option B: This type of key figure has better performance than a time-independent key figureThis is incorrect. Performance depends on usage, not a guaranteed advantage over other time-independent key figures.

Option C: This object usually provides a single value for a unique planning combinationThis is correct. An attribute key figure (e.g., Product Price) provides one static value per planning combination (e.g., PERPROD), a defining feature, per SAP IBP’s configuration guides.

Option D: This object contains user-defined criteria that monitor the running of business plansThis is incorrect. This describes alerts or KPIs, not attribute key figures.

Thus, C is the relevant feature, per SAP IBP’s official definition.

SAP IBP for Sales and Operations Planning (S&OP) unifies demand, supply, and inventory processes, with key data reviewed in the S&OP cycle, per SAP IBP’s S&OP documentation.

Option A: Global Demand PlanThis is incorrect. "Global Demand Plan" is not a standard term in SAP IBP S&OP; it’s typically "Consensus Demand Plan" after collaboration.

Option B: Constrained Demand PlanThis is incorrect. Constrained demand is more relevant to supply planning or response, not the unified S&OP review process.

Option C: Inventory PlanThis is correct. The Inventory Plan (e.g., safety stock, target inventory) is reviewed in S&OP to ensure alignment with demand and supply, a key unified process, per SAP IBP’s documentation.

Option D: Consensus Demand PlanThis is correct. The Consensus Demand Plan, finalized after S&OP collaboration, is a central data point reviewed to balance supply and inventory, per SAP IBP’s S&OP workflow.

Thus, C and D are commonly reviewed in S&OP, per SAP IBP’s official processes.

SAP IBP for Demand enhances demand planning with advanced features, per SAP IBP’s demand module documentation.

Option A: Automated, exception-based processingThis is correct. Automated forecasting with exception handling (e.g., alerts for outliers) is a core capability, per SAP IBP’s demand planning features.

Option B: Statistical analysis using the predictive analytics toolsThis is incorrect. Predictive analytics (e.g., machine learning) is available via SAP HANA integration, not a native IBP Demand tool.

Option C: Determination of coefficient of variation (CV)This is correct. CV (variability measure) is calculated in ABC/XYZ segmentation and demand analysis, a standard feature, per SAP IBP’s documentation.

Option D: Classifying demand into zonesThis is incorrect. "Zones" is not a standard demand classification in SAP IBP; ABC/XYZ segmentation is used instead.

Option E: Embedded, on-the-fly demand analyticsThis is correct. Real-time analytics (e.g., in Excel or Planner Workspaces) provide instant demand insights, per SAP IBP’s demand capabilities.

Thus, A, C, and E are key capabilities, per SAP IBP’s official demand planning scope.

SAP IBP for Response and Supply includes time-series-based planning (e.g., heuristics, optimization) alongside order-based planning. Time-series planning relies on master data types to define the supply chain network and planning objects.

Option A: DS Order FulfillmentThis is incorrect. "DS Order Fulfillment" is not a standard master data type in SAP IBP. Order fulfillment is an outcome of response planning (order-based), not a time-series master data type.

Option B: Transportation LaneThis is incorrect in this context. While Transportation Lane is a master data type in SAP IBP, it is primarily used in supply planning (e.g., defining sourcing relationships). However, in the specific scope of "time-series-based planning within SAP IBP for response and supply," it’s less prominent, as response planning often emphasizes order-based logic over time-series constraints like lanes. The correct answers focus on foundational master data.

Option C: CustomerThis is correct. The Customer master data type (e.g., Customer ID) is essential in time-series planning to model demand at the customer level (e.g., in Sales and Operations Planning or supply planning). It’s a core component of planning levels like PERPRODCUST.

Option D: LocationThis is correct. The Location master data type (e.g., Plant, Warehouse) defines nodes in the supply chain network. Time-series planning uses locations to calculate supply, inventory, and transportation quantities across the planning horizon.

Option E: ProductThis is correct. The Product master data type (e.g., Product ID) is fundamental to time-series planning, representing the items being planned. It’s used in key figures like production quantities or demand forecasts.

Thus, C, D, and E (Customer, Location, Product) are core master data types in SAP IBP’s time-series-based planning for response and supply, as per official documentation on planning area setup.

Lot sizes in SAP IBP are critical for supply planning, defining the minimum or fixed quantities for production or transportation to optimize resource use and costs. They are typically configured as master data attributes in planning areas supporting time-series-based supply planning.

Option A: Lot sizes are applicable for production and handling quantitiesThis is misleading. In SAP IBP, lot sizes apply to production (e.g., Production Source of Supply) and transportation (e.g., Transportation Lane), but "handling quantities" is not a standard term in SAP IBP’s supply planning context. Handling might imply warehouse operations, which are out of scope for lot size settings.

Option B: Periodic lot size setting overrides the minimum lot sizeThis is incorrect. SAP IBP does not define "periodic lot size" as overriding minimum lot size in its standard configuration. Minimum lot size (e.g., Minimum Production Lot Size) is a fixed constraint enforced by the supply planning heuristic or optimizer, and periodic settings (e.g., planning frequency) do not override it.

Option C: Lot sizes are time-independent master data settingsThis is correct. In SAP IBP, lot sizes (e.g., Minimum Lot Size, Maximum Lot Size) are defined as attributes of master data types like Production Source of Supply or Transportation Lane. These are static, time-independent values unless explicitly modeled as time-dependent key figures, which is not the default behavior. This aligns with SAP IBP’s master data framework.

Option D: Lot sizes are applicable for production and transportation quantitiesThis is correct. SAP IBP’s supply planning supports lot sizes for both production (e.g., via Production Source Header) and transportation (e.g., via Transportation Lane). For example, a minimum lot size ensures that production runs or shipments meet a threshold, optimizing efficiency, as per SAP IBP’s supply planning documentation.

Thus, C and D accurately reflect SAP IBP’s lot size properties, emphasizing their role as time-independent master data affecting production and transportation.

Helper key figures in SAP IBP are intermediate calculated key figures that simplify complex logic, per SAP IBP’s calculation documentation.

Option A: Used to break down a large calculation into manageable subcalculationsThis is correct. Helper key figures split complex formulas (e.g., multi-step demand adjustments) into smaller, reusable parts, a primary use case, per SAP IBP’s guides.

Option B: Used by end-users in planning views to help visualize cross-period calculationsThis is incorrect. Helper key figures are backend tools, not typically exposed for visualization; local members serve that purpose in views.

Option C: Used at any level of calculation level except the Request LevelThis is incorrect. Helper key figures can be used at any level, including Request Level, depending on configuration.

Option D: Used when you have more than three inputs at different planning levels in one calculationThis is correct. They manage complexity when combining multiple inputs (e.g., from PERPROD and PERPRODLOC), a common scenario, per SAP IBP’s documentation.

Thus, A and D are relevant use cases, per SAP IBP’s official helper key figure roles.

Lag-based snapshots in SAP IBP capture historical key figure values with a specified time offset (lag), useful for tracking past data (e.g., demand from 3 weeks ago). Their configuration and behavior are defined in SAP IBP’s time-series planning framework.

Option A: The number of lag-based snapshots are limited to nine levelsThis is incorrect. There’s no documented limit of nine snapshots in SAP IBP; the number depends on configuration and performance, not a fixed cap.

Option B: Lag-based snapshots are created in the Configuration app for a fixed time rangeThis is incorrect. Snapshots are configured in the Planning Areas app (via key figure settings), not a generic "Configuration app," and they dynamically adjust based on lag, not afixed range.

Option C: Target key figures for these snapshots are exposed to the user in planning viewThis is correct. Lag-based snapshot key figures (e.g., SNAPSHOT_LAG1) are visible and usable in planning views (e.g., Excel), allowing users to analyze historical data, per SAP IBP’s documentation.

Option D: Target key figures for these snapshots must have lag as a root attribute in the base planning levelThis is correct. The lag attribute (e.g., LAG = 1, 2) must be part of the base planning level (e.g., PERPRODLOCLAG) to store snapshot values distinctly, a requirement in SAP IBP’s snapshot setup, per official guides.

Thus, C and D are features of lag-based snapshots, per SAP IBP’s official functionality.