Weighted average calculations in SAP IBP (e.g., KF3 = SUM(KF1 * KF2) / SUM(KF2)) use a weight key figure, configured in the Planning Areas app, per SAP IBP’s documentation.

Option A: The numerator of the calculation should be storedThis is incorrect. The numerator (e.g., value * weight) is calculated, not necessarily stored.

Option B: The first parameter of the formula acts as a weightThis is incorrect. The weight is explicitly defined (e.g., KF2), not assumed as the first parameter.

Option C: Attributes can be used in weighted average key figure calculationThis is incorrect. Attributes as key figures provide static values, but weights are typically key figures, not attributes directly.

Option D: The numerator’s value should include multiplication by the weightThis is correct. In a weighted average (e.g., (KF1 * KF2) / SUM(KF2)), the numerator multiplies the value (KF1) by the weight (KF2), a defining feature, per SAP IBP’s calculation rules.

Thus, D is the correct feature, per SAP IBP’s official calculation logic.

The Planner Workspaces app in SAP IBP is a Fiori-based UI that integrates planning tools, analytics, and collaboration features for supply chain planners.

Option A: It supports simulating the effect of the changesThis is incorrect. While simulation is a feature in SAP IBP (e.g., via versions or scenarios in Excel), Planner Workspaces focuses on visualization and navigation, not direct simulation execution. Simulation occurs in other apps like Excel or Manage Scenarios.

Option B: It supports favorites created in SAP IBP, add-in for Microsoft ExcelThis is correct. Planner Workspaces integrates with the Excel add-in, allowing users to access their Excel favorites (e.g., planning views) directly within the workspace. This enhances usability by linking preferred tools, as per SAP IBP’s documentation on Planner Workspaces.

Option C: It supports embedding analytic stories as a workspace componentThis is correct. Analytic stories (created in the Manage Analytics Stories app) can be embedded in Planner Workspaces, providing charts and insights alongside planning data. This is a key visualization feature, per SAP IBP’s UI capabilities.

Option D: It supports sharing with other users or user groupsThis is incorrect. Sharing is available in Excel (e.g., templates) or analytics apps, but Planner Workspaces doesn’t have a native sharing function for workspaces themselves. Collaboration occurs via other mechanisms.

Thus, B and C are accurate capabilities of Planner Workspaces, aligning with SAP IBP’s official feature set.

SAP IBP provides sample planning areas (e.g., SAPIBP1, SAP3, SAP6) with preconfigured processes to demonstrate module-specific functionality.

SAP6: Focused on Demand Planning and Sensing, enhancing short-term demand forecasts.

SAP3: Focused on Inventory Optimization, managing multi-stage inventory targets.

Option A: SAP6 Control Tower, and SAP3 Sales and Operations Planning and Supply PlanningThis is incorrect. SAP6 is not Control Tower-specific (that’s SAP8), and SAP3 focuses on Inventory Optimization, not broad S&OP or Supply Planning.

Option B: SAP6 Demand Planning and Sensing, and SAP3 Control TowerThis is incorrect. SAP3 is Inventory Optimization, not Control Tower, which is a separate module (SAP8).

Option C: SAP6 Demand Planning and Sensing, and SAP3 Inventory PlanningThis is correct. SAP6 includes Demand Planning (statistical forecasting) and DemandSensing (short-term adjustments), while SAP3 focuses on Inventory Planning (e.g., safety stock optimization), matching their official purposes per SAP IBP’s sample content documentation.

Option D: SAP6 Sales and Operations Planning and Supply Planning, and SAP3 Inventory PlanningThis is incorrect. SAP6 is narrower (Demand Planning/Sensing), not full S&OP or Supply Planning (more aligned with SAPIBP1). SAP3 is correct for Inventory Planning.

Thus, C accurately reflects the processes in SAP6 and SAP3, per SAP IBP’s sample planning area definitions.

Transportation Load Building (TLB) in SAP IBP (part of Supply Chain Control Tower or integration with SAP TM) optimizes the consolidation of shipments into transportation loads based on constraints like capacity and rules.

Option A: Loads are calculated based on transportation lanes and modes of transportThis is partially true but not the defining feature. TLB considers lanes and modes (e.g., truck, rail) as inputs, but its core function is grouping shipments, not merely calculating based on these. It’s too generic to be the standout feature.

Option B: Loads are integrated into SAP ERP or SAP S/4HANA as distribution receiptsThis is incorrect. TLB focuses on planning loads within SAP IBP or TM, not direct integration into ERP/S4HANA as "distribution receipts." Integration might occur downstream, but it’s not a TLB feature.

Option C: It uses rule-based planning to create transportation loadsThis is correct. TLB employs configurable rules (e.g., maximum weight, volume, compatibility) to consolidate shipments into loads. For example, it might ensure a truck’s capacity is fully utilized while respecting delivery windows, a hallmark of TLB in SAP IBP’s supply planning capabilities, as per official documentation.

Option D: Loads are calculated based on the minimum utilization of equipmentThis is incorrect. TLB aims to maximize, not minimize, equipment utilization to reducecosts. Minimum utilization might be a constraint, but it’s not the calculation basis.

Thus, C is the defining feature of TLB, reflecting its rule-based approach, consistent with SAP IBP’s supply chain optimization tools.

The Time-Series Supply Optimizer in SAP IBP minimizes an objective function (cost-based), penalizing violations of soft constraints, while hard constraints must be fully satisfied, per SAP IBP’s optimization documentation.

Option A: Violation of minimum resource utilizationThis is correct. Minimum resource utilization (e.g., machine usage) is a soft constraint; violations incur penalties (e.g., underutilization costs), influencing the objective function.

Option B: Not respecting production capacityThis is incorrect. Production capacity is a hard constraint in the optimizer; it cannot be violated, only respected, unlike soft constraints with penalties.

Option C: Not fully satisfied demandsThis is correct. Unsatisfied demand (non-delivery) is a soft constraint, penalized via high non-delivery costs in the objective function, a core optimizer feature.

Option D: Violation of minimum aggregated inventory valuesThis is correct. Minimum inventory levels (e.g., safety stock) are soft constraints; violations are penalized (e.g., stockout costs), affecting the objective function.

Thus, A, C, and D are penalized solutions, per SAP IBP’s optimizer behavior.

ABC/XYZ segmentation in SAP IBP is a demand planning tool to classify products based on value (ABC, e.g., revenue contribution) and demand variability (XYZ, e.g., forecast accuracy). It’s used to prioritize planning efforts and optimize inventory.

Option A: Substitute missing values in case of sporadic demandsThis is incorrect. ABC/XYZ segmentation classifies products but doesn’t inherently substitute missing values. Sporadic demand handling is managed by demand sensing or specific forecast models, not segmentation itself.

Option B: Choose time-independent key figures as segmentation measuresThis is correct. In SAP IBP, segmentation measures (e.g., sales value for ABC, coefficient of variation for XYZ) can be time-independent key figures (e.g., total annual revenue, average variability). These are configured in the ABC/XYZ Segmentation app, allowing static or dynamic analysis, as per SAP’s demand planning documentation.

Option C: Identify inventory items that require closer attentionThis is correct. ABC classifies high-value items (A) versus low-value (C), while XYZ identifies stable (X) versus erratic (Z) demand. Combining them (e.g., AX = high-value, stable) highlights items needing focus (e.g., AZ = high-value, erratic), aiding inventory and planning prioritization—a core feature of SAP IBP segmentation.

Option D: Use forecasting algorithms that are specific to seasonal demands of SKUs in the segment "B"This is incorrect. ABC/XYZ segmentation doesn’t directly dictate forecasting algorithms or tie them to specific segments like "B" (moderate value). Forecast models (e.g., seasonalARIMA) are configured separately in demand planning, not as a segmentation output.

Thus, B and C reflect SAP IBP’s ABC/XYZ segmentation capabilities per official documentation.

Planner Workspaces in SAP IBP is a Fiori-based UI that integrates planning tools, analytics, and workflows, enhancing planner productivity. Its value drivers are outlined in SAP IBP’s UI documentation.

Option A: Issues can be identified and solved with special functionsThis is correct. Alerts and playbooks in Planner Workspaces help identify and resolve issues (e.g., supply shortages), a key value driver, per SAP IBP’s features.

Option B: It combines various components into one user interfaceThis is correct. It integrates planning views, charts, and alerts into a single UI, streamlining workflows, a core benefit, per SAP IBP’s documentation.

Option C: It can trigger SAP S/4HANA transactions in real timeThis is incorrect. Planner Workspaces focuses on IBP planning, not real-time S/4HANA transaction execution, which requires integration tools like CI-DS.

Option D: It combines the data from multiple planning areas into one user interfaceThis is incorrect. It operates within one planning area; combining multiple areas requires separate configurations or views, not a native feature.

Option E: Application jobs can be started from this user interfaceThis is correct. Planners can trigger jobs (e.g., Copy Operator) directly from Planner Workspaces, enhancing efficiency, per SAP IBP’s UI capabilities.

Thus, A, B, and E are value drivers, per SAP IBP’s official Planner Workspaces description.