Which of the following are features of lag-based snapshots? Note: There are 2 correct answers to this question.
Correct Answer: C,D
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.
Question 22
Which Supply Planning processes are part of the tactical planning level within a planning hierarchy? Note: There are 2 correct answers to this question.
Correct Answer: C,D
In SAP IBP, the planning hierarchy includes strategic (long-term), tactical (medium-term), and operational (short-term) levels. Tactical planning (e.g., monthly horizon) focuses on mid-term supply chain decisions. * Option A: Order PrioritizationThis is incorrect. Order prioritization is an operational-level process, typically in SAP IBP for Response and Supply, dealing with short-term order allocation, not tactical planning. * Option B: Stock ReplenishmentThis is incorrect. Stock replenishment is operational, focusing on short-term actions (e.g., daily/weekly restocking), not tactical mid-term planning. * Option C: Inventory Build and ReductionThis is correct. Tactical planning involves decisions like building inventory ahead of demand peaks or reducing excess stock over months, aligning with SAP IBP's Inventory Optimization and S&OP processes at this level. * Option D: Balancing Supply and DemandThis is correct. Balancing supply and demand over a medium-term horizon (e.g., via S&OP or supply heuristics) is a core tactical process in SAP IBP, ensuring resource alignment, per official planning hierarchy definitions. Thus, C and D are tactical supply planning processes, per SAP IBP's planning framework.
Question 23
You create a planning filter using an SAP IBP Fiori app. Which of the following objects can it be applied to? Note: There are 2 correct answers to this question.
Correct Answer: A,B
Planning filters in SAP IBP, created via the Manage Planning Filters app (Fiori-based), define subsets of data (e.g., by Product, Location) for use across various applications. Their applicability depends on SAP IBP's functional scope. * Option A: Planning view templates in the SAP IBP, add-in for Microsoft ExcelThis is correct. Planning filters can be applied to planning view templates in the Excel add-in to restrict data displayed or edited (e.g., show only products in Region X). This is a core feature for planners, as per SAP IBP's Excel integration documentation. * Option B: Jobs in the Application Jobs appThis is correct. Planning filters can be parameters in application jobs (e.g., Copy Operator, Purge Data) to limit the scope of data processed (e.g., purge data for specific Locations). This is a standard capability in the Application Jobs app, per SAP IBP's job management guides. * Option C: Compare function in the Planning Areas appThis is incorrect. The Planning Areas app manages planning area configurations, and while it has a "Compare" function to analyze differences, planning filters are not applied here. Filters are for runtime data, not configuration comparison. * Option D: Supply chain graph in Supply Chain Network appThis is incorrect. The Supply Chain Network app visualizes the network (e.g., Locations, Transportation Lanes), but planning filters are not directly applied to this graph. Filters affect data views, not network visualizations. Thus, A and B are the correct objects where planning filters can be applied, per SAP IBP's official functionality.
Question 24
Model configuration allows the attributes of a master data type to be assigned as key figures. Which feature is relevant for this type of object?
Correct Answer: C
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 plans This is incorrect. This describes alerts or KPIs, not attribute key figures. Thus, C is the relevant feature, per SAP IBP's official definition.
Question 25
Which conditions have to be fulfilled as a prerequisite to maintain a key figure disaggregation? Note: There are 2 correct answers to this question.
Correct Answer: C,D
Disaggregation in SAP IBP distributes aggregated key figure values to lower levels, configured in the Planning Areas app. Prerequisites depend on the key figure's properties, per SAP IBP's documentation. * Option A: The key figure is calculated and system editableThis is incorrect. Calculated key figures derive values and aren't typically disaggregated; they're outputs, not inputs for disaggregation. * Option B: The key figure is calculated and all editableThis is incorrect. Calculated key figures aren't manually editable (all editable), and disaggregation applies to stored key figures. * Option C: The key figure is stored and system editableThis is correct. A stored key figure (persisted data) that's system editable (e.g., via operators) can be disaggregated, a valid condition, per SAP IBP's rules. * Option D: The key figure is stored and all editableThis is correct. A stored key figure that's fully editable (e.g., manually in Excel) supports disaggregation, as users can input aggregated values to split, per SAP IBP's documentation. Thus, C and D are prerequisites, per SAP IBP's official disaggregation requirements.
