What is taken as an input for the demand sensing process? Note: There are 2 correct answers to this question.
Correct Answer: C,D
Demand Sensing in SAP IBP refines short-term forecasts using real-time data, per SAP IBP's demand sensing documentation. * Option A: Results of time series analysisThis is incorrect. Time series analysis (statistical forecast) is an input to demand planning, not sensing, which adjusts based on current signals. * Option B: Forecast Accuracy measuresThis is incorrect. Accuracy measures evaluate forecasts, not serve as direct inputs to sensing. * Option C: Open Sales OrdersThis is correct. Open sales orders provide real-time demand signals, a key input to demand sensing, per SAP IBP's documentation. * Option D: Consensus DemandThis is correct. The Consensus Demand Plan (from S&OP) is a baseline input, adjusted by sensing with short-term data, per SAP IBP's process. Thus, C and D are inputs, per SAP IBP's official demand sensing scope.
Question 17
You set up time-series integration using SAP Cloud Integration for Data Services. During the integration process of master data, an error occurred. In the Data Integration app the job failed with the status "Fatal Error." How can you find more details about the error?
Correct Answer: C
SAP Cloud Integration for Data Services (CI-DS) integrates master data into SAP IBP, with errors logged in the Data Integration Jobs app, per SAP IBP's integration documentation. * Option A: Navigate to the Master Data Workbook in Excel and open the LogThis is incorrect. The Excel Master Data Workbook doesn't provide integration job logs; it's for manual maintenance. * Option B: Navigate to the Manage Master Data app and open the LogThis is incorrect. The Manage Master Data app manages data, not integration job logs. * Option C: Download the Initial Problem Report in the Data Integration appThis is correct. The Data Integration Jobs app provides detailed error reports (e.g., "Initial Problem Report") for failed jobs like "Fatal Error," per SAP IBP's troubleshooting guides. * Option D: Download the Rejection Report in the Data Integration appThis is incorrect. The Rejection Report details rejected records, not the full error context of a "Fatal Error." Thus, C is the correct method, per SAP IBP's official integration error handling.
Question 18
What is an example of a commonly used time-independent key figure?
Correct Answer: C
In SAP IBP, key figures can be time-dependent (e.g., forecast quantities over weeks) or time-independent (static values not tied to time periods). Time-independent key figures are often used for constants or attributes in planning calculations. * Option A: A special key figure marked as an aggregate key figure (aggregate constraint)This is incorrect. Aggregate key figures (e.g., summing demand across products) are typically time-dependent, as they reflect data over a planning horizon, not static values. * Option B: A unit of measure key figure, such as UoM Conversion FactorThis is incorrect in this context. While UoM Conversion Factor is time-independent (e.g., 1 kg = 1000 g), it's technically a master data attribute, not a key figure in SAP IBP's standard terminology. Key figures are editable or calculated, whereas UoM factors are static settings. * Option C: Any attribute as a key figureThis is correct. In SAP IBP, attributes (e.g., Product Category, Customer Priority) can be configured as time-independent key figures via the "Attribute as Key Figure" feature. For example, a Product's "Safety Stock Target" could be a static key figure used across all periods, a common practice in supply planning, as per SAP IBP's configuration options. * Option D: A currency conversion key figure, such as Exchange RateThis is incorrect. Exchange rates can vary over time (e.g., monthly rates), making them time-dependent in most cases. Even if static, they're typically master data or external inputs, not a "commonly used" key figure example in SAP IBP. Thus, C is the best example of a commonly used time-independent key figure, aligning with SAP IBP's flexibility to model attributes as static key figures.
Question 19
Which processes are embedded in the sample planning areas SAP6 and SAP3?
Correct Answer: C
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 Planning This 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.
Question 20
The S&OP Operator Profiles app is used to configure different types of algorithms. Which algorithm-specific settings are unique for the Time-Series-Based Supply Optimizer? Note: There are 2 correct answers to this question.
Correct Answer: A,C
The S&OP Operator Profiles app in SAP IBP configures planning algorithms (e.g., heuristics, optimizer). The Time-Series-Based Supply Optimizer has unique settings reflecting its optimization approach. * Option A: DiscretizationThis is correct. Discretization (e.g., binary or integer variables for lot sizes) is specific to the optimizer, enabling discrete decisions (e.g., full truckloads), a feature not in heuristics, per SAP IBP's optimizer documentation. * Option B: Time profile levelThis is incorrect. Time profile level applies to all time-series planning (heuristics and optimizer), not unique to the optimizer. * Option C: Global cost factorsThis is correct. The optimizer uses global cost factors (e.g., non- delivery, inventory holding costs) to balance trade-offs across the network, a unique setting compared to heuristics, per SAP IBP's configuration guides. * Option D: Processing modeThis is incorrect. Processing mode (e.g., batch vs. interactive) is a general job setting, not algorithm-specific to the optimizer. Thus, A and C are unique settings for the Time-Series-Based Supply Optimizer, per SAP IBP's official documentation.
