Learn, Practice, and Improve with SAP C_IBP_2502 Practice Test Questions

Explanation:

A. Correct.
In SAP IBP, every key figure calculation defines operands (inputs) that must be specified as either stored (persistent in the database) or calculated (derived from another formula). This classification is mandatory and determines data persistence and calculation sequence.

D. Correct.
IBP enables calculations across different planning levels using the LOOKUP function. For example, you can reference a product-level forecast rate from a corporate-level plan. This cross-level capability is fundamental for multi-tier planning.

Incorrect Options:

B. Incorrect.
A calculation chain can output to either a calculated or a stored key figure. Stored key figures are often the final target for planning results (e.g., saving a calculated order quantity into a persistent key figure). The output destination is configurable.

C. Incorrect.
Aggregation functions like SUM or MAX roll up data from a lower (more granular) planning level to a higher level, not the reverse. For example, summing weekly product-location data to monthly product-region totals. The opposite operation—disaggregation—uses functions like PROPORTIONAL.

Reference:
SAP Help – "Defining Key Figures" emphasizes that defining the storage type for each operand is a required step in calculation configuration.
SAP Help – "Using Lookups in Key Figure Calculations" details the use of LOOKUP and EXTEND functions for cross-level data retrieval.

Explanation:

B. Splitting the values from aggregated to detailed level using multiplication by the proportions
– This is a standard disaggregation method. The aggregated value is multiplied by proportional weights (derived from historical data, planning data, or reference key figures) to distribute the value accurately to the detailed PERPRODCUST level.

D. Splitting the values from aggregated to detailed level, based on a stored split-factor key figure
– This approach uses a dedicated key figure that stores split factors for each detailed level. The system multiplies the aggregated value by these factors to derive detailed values. It is particularly useful when proportional weights are predefined or based on external business rules.

Incorrect Options:

A. Splitting the values from detailed to aggregated level by using a copy operator
– Copy operators are used for aggregation from detailed to higher levels, not for disaggregation. Using them would move values bottom-up, which is the opposite of the requirement.

C. Splitting the values from aggregated to detailed level, based on the time profile attribute
– Time profile attributes are used for distributing values over the time dimension, not for organizational or customer-level disaggregation. This does not address the PERPRODCUSTREGION → PERPRODCUST split.

References:
SAP Help Portal: Key Figure Formulas in SAP IBP
SAP IBP Planning Operators Guide – Disaggregation and Copy Functions

Explanation:

The "logical progression" in SAP IBP represents the transformation of raw data into a validated business plan.

The Starting Point (Statistical Forecast Qty):
The process begins with Demand Sensing or Statistical Forecasting. The system calculates this key figure using historical data (Actuals) to create an objective baseline. It represents the "first" signal in the demand cycle before any manual overrides or market intelligence are applied.

The Final Goal (Consensus Demand Plan Qty):
The ultimate objective of the demand phase in S&OP is to reach a Consensus. This involves reconciling the Statistical Forecast with inputs from Sales, Marketing, and Finance. Once these stakeholders agree on a single "one-number" plan, it is stored in the Consensus Demand Plan Qty key figure. This value is critical because it serves as the "demand signal" that triggers the Supply Review phase (Heuristics or Optimizer).

Why Other Options Are Incorrect

A & C (Local Demand Plan):
In the SAPIBP1 model, the "Local Demand Plan" is an intermediate step. It represents the specific input from regional sales teams. Starting with a "Local Plan" would bypass the essential baseline provided by the Statistical Forecast, which is the industry-standard starting point for IBP.

D (Global Demand Plan Qty):
While "Global Demand" represents an aggregation of regional views, it is not the terminal step of the S&OP process. The "Consensus" step is the formal culmination where the business commits to the plan. "Global Demand" may exist, but without the "Consensus" designation, it hasn't officially completed the collaborative S&OP cycle.

References:
SAP Help Portal: S&OP Process Overview in SAPIBP1.
Course IBP200: SAP IBP – Platform Features and Configuration (Unit 3: Demand Planning).
SAP Best Practices for SAP IBP: S&OP – Demand Review (Process Diagram).

Explanation:

To implement UOM conversion in SAP IBP, you must align your master data and configuration with the system's architectural rules:

Attribute of Master Data (C):
In SAP IBP, the base unit of measure (e.g., EA, KG) is defined as an attribute within a master data type, typically the Product master data. This attribute (e.g., UOMID) tells the system what the "home" unit is for a specific planning object before any conversion is applied.

Time Independence (D):
Unlike currency exchange rates, which fluctuate daily or monthly, UOM conversion factors (e.g., 1 Box = 12 Units) are generally static. Therefore, UOM conversions are not time-dependent in the standard configuration. If a product's packaging changes over time, it is usually handled as a new product ID or a specific lifecycle change rather than a time-phased conversion factor.

Analytics Flexibility (A):
SAP IBP is designed to be user-friendly for global reporting. In the Analytics and Dashboard apps, users have the native capability to select a "Target Unit of Measure." The system then performs the math "on-the-fly" using the conversion factors defined in your master data.

Why the other options are incorrect:

B (Usually not time-independent):
This is the opposite of the truth. UOMs are time-independent; currencies are the ones that are time-dependent.

E (Handled by the Excel add-in):
This is a common "trick" question. While the user triggers the selection in the Excel add-in, the actual calculation/conversion logic is handled by the SAP IBP backend (HANA engine), not the local Excel installation.

References
SAP Help Portal: Configuring Unit of Measure Conversion.
SAP IBP200 Training: Unit 4: Master Data and Attributes.

Explanation:

C. Correct.Within a single planning view in the SAP IBP Excel Add-in, you can select all time levels available in the time profile assigned to the planning area. For example, if your time profile contains levels like Year, Quarter, Period (Month), and Week, you can configure a view to show data simultaneously aggregated at any combination of these levels (e.g., show Years in columns and Weeks in rows).

Incorrect Options:

A. Incorrect.
Time levels are not restricted to the base planning level of the key figures. The time profile operates independently, allowing aggregation and disaggregation across its defined time hierarchy regardless of the key figure's storage granularity.

B. Incorrect.
There is no global configuration parameter that restricts the number of time levels selectable in a view. The only restriction is the set of levels defined in the active time profile.

D. Incorrect.
While adding many time levels can impact performance, there is no system restriction to four. Performance is influenced by data volume and view complexity, but the design allows full flexibility from the time profile.

Reference:
SAP Help – "Creating Planning Views" explicitly states that when configuring a view, you can "select the time levels you want to use" from the time profile. There is no inherent system limit per view; the constraint is the structure defined in the time profile itself.

Explanation:

The Planner Workspaces app is designed for high productivity and collaboration. Here is why these two options are the correct capabilities:

Embedding Analytic Stories (C):
Planner Workspaces allow you to combine different "components" in one view. You can embed Analytics Stories (created in the Manage Analytics Stories app) directly alongside your planning views. This gives planners the ability to see high-level strategic visualizations and deep-dive transactional data in the same workspace.

Sharing with Users/Groups (D):
To foster collaboration, a workspace is not restricted to the creator. Once you have configured a workspace with specific workbooks, variants, and components (like planning views or alerts), you can share it with specific colleagues or entire user groups. This ensures that a team of planners is looking at the same synchronized data and layout.

Why the other options are incorrect:

A (Simulating changes):
While you can change data and see the results of formulas, formal Planning Simulations (like running a Heuristic or Optimizer in simulation mode) are primary features of the Excel Add-in or specific application jobs. While the app is evolving, the "simulation of effect" in the context of this exam question is traditionally attributed to the Excel interface or the Manage Scenarios functionality.

B (Excel Favorites):
This is a common point of confusion. You can import a template or favorite from the Excel add-in when creating a component in Planner Workspaces, but the app does not natively "support" or sync them as live Excel favorites. Once imported, they become workspace-specific components. Changes made to a favorite in Excel do not automatically update the Workspace component and vice versa.

References
SAP Help Portal: Planner Workspaces - SAP Integrated Business Planning.
Course IBP200: Unit 2: User Interface - Planner Workspaces.

Explanation:

B. Correct.
Time profile levels are internally assigned PERIODID indexes. In a time profile with levels ordered as 1: Day, 2: Technical Week, 3: Week, 4: Month, 5: Year, the WEEK level is PERIODID4. To check if a record belongs to the current week, you compare PERIODID4 to the system variable PERIODID4CU (Current Week). This condition allows differentiating values for the current week bucket from others.

Incorrect Options:

A. PERIODID2 refers to Technical Week, not the standard Week level.
A condition based on PERIODID2CU would isolate the current technical week, which may not align with the business week in the planning view.

C. PERIODID3 refers to the Week level if counting from the top (Year=1).
However, PERIODID indexes are assigned from the bottom up (most granular = 1). With Day as level 1, Week is level 4, making PERIODID3 likely Month, not Week.

D.PERIODID1 refers to the most granular level: Day.
A condition on PERIODID1CU would isolate the current day, not the current week.

Reference:
SAP Help – "Time Condition Functions" specifies that PERIODID and PERIODIDCU are used to reference time profile levels and their current period in calculations. Level numbering starts at 1 from the lowest (most granular) level.