You created a key figure and want to add calculations. Which of the following rules do you consider? Note: There are 2 correct answers to this question.
Correct Answer: A,D
Key figure calculations in SAP IBP, configured in the Planning Areas app, follow specific rules, per SAP IBP' s calculation engine documentation. * Option A: All key figure calculations have calculation inputs, which can be marked as stored or calculatedThis is correct. Calculations (e.g., KF3 = KF1 + KF2) use inputs that are either stored (persisted data) or calculated (derived), a fundamental rule, per SAP IBP's guides. * Option B: The calculation chain for a key figure must always result in a calculated key figureThis is incorrect. The chain can result in a stored key figure if configured to persist, notalways calculated. * Option C: Aggregation calculations using SUM or MAX functions must be based on a higher aggregation levelThis is incorrect. Aggregation can occur at any level, not strictly higher; it depends on the planning level definition. * Option D: Key figures can be calculated across the different planning levelsThis is correct. Calculations can span levels (e.g., aggregating from PERPROD to PERPRODLOC), using disaggregation/aggregation, per SAP IBP's flexibility. Thus, A and D are key rules, per SAP IBP's official calculation principles.
Question 2
Manage Analytics Stories introduces advanced visualization features within SAP Integrated Business Planning for Supply Chain. What are some of the main capabilities of the stories? Note: There are 3 correct answers to this question.
Correct Answer: A,C,D
The Manage Analytics Stories app in SAP IBP enables users to create interactive dashboards and visualizations. Its capabilities enhance decision-making by integrating data insights. * Option A: Links to external URLs can be embedded in the storyThis is correct. Analytics Stories support embedding hyperlinks to external resources (e.g., documentation, websites), enhancing context, as per SAP IBP's visualization features. * Option B: The story is structured around one responsive pageThis is incorrect. Stories can span multiple pages or tabs, not just one, allowing complex layouts. The responsive design adapts to devices, but it's not limited to a single page. * Option C: Specific chart and table filters can be applied within the storyThis is correct. Users can apply filters to charts and tables (e.g., by Product, Time) within the story, enabling dynamic data exploration, a core capability in SAP IBP's analytics tools. * Option D: Stories must be re-created in each SAP IBP environmentThis is correct. Analytics Stories are environment-specific (e.g., test vs. production) and cannot be transported directly. They must be recreated or exported/imported manually, per SAP IBP's architecture. Thus, A, C, and D are main capabilities of Manage Analytics Stories, per SAP IBP's official documentation. (Note: Original answer A, C, D matches corrected analysis.)
Question 3
Which apps can be enhanced with analytical charts? Note: There are 2 correct answers to this question.
Correct Answer: C,D
Analytical charts in SAP IBP enhance visualization and decision-making. The apps supporting this depend on SAP IBP's UI framework (Fiori-based). * Option A: Web-based PlanningThis is incorrect. "Web-based Planning" is not a specific SAP IBP app; it's a general term. Planning is primarily via Excel or Planner Workspaces, not a standalone web app for charts. * Option B: Intelligent VisibilityThis is incorrect. Intelligent Visibility is a feature in SAP Supply Chain Control Tower, not an app enhanced with analytical charts in the core IBP planning context. * Option C: Planner WorkspaceThis is correct. Planner Workspaces (Fiori app) can embed analytical charts (e.g., from Analytics Stories) alongside planning data, enhancing the UI, per SAP IBP's documentation. * Option D: Dashboards - AdvancedThis is correct. The Advanced Dashboards app allows users to create and customize analytical charts for insights, a core visualization tool in SAP IBP, per official app descriptions. Thus, C and D are apps enhanced with analytical charts, per SAP IBP's UI capabilities.
Question 4
Which type of master data represents the Master Data Type Component?
Correct Answer: C
Master data types in SAP IBP define planning objects, with "Component" typically referring to a specific type like Production Source Item Component, per SAP IBP's documentation. * Option A: Virtual master data typeThis is incorrect. Virtual types are temporary or derived, not standard for components. * Option B: Compound Master Data TypeThis is incorrect. Compound types (e.g., SOURCECUSTOMER) combine multiple simple types, not specifically "Component." * Option C: Reference Master Data TypeThis is correct. The Component master data type (e.g., in Production Source Item) is a Reference type, linking to a Product, per SAP IBP's master data hierarchy (e.g., referencing Product ID). * Option D: External Master Data TypeThis is incorrect. External types are sourced externally, not a fit for Component. Thus, C is the correct type, per SAP IBP's official master data definitions.
Question 5
How do you achieve rolling aggregation with SAP IBP?
Correct Answer: C
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.
