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

Explanation:

When setting up and using Units of Measure (UOM) in SAP IBP, several foundational characteristics and user functionalities must be considered. These are based on how the system is configured to handle conversions and display data.

A. Units of measure are usually not time-dependent. is correct.
In SAP IBP, UOMs are typically treated as time-independent. This means that a product's base unit of measure (e.g., "each") or its conversion factors are not expected to change frequently over time. Because of this, conversion factors are often modeled as time-independent key figures, which store a single value for a planning combination rather than a value for every time period, leading to better performance and efficiency .

B. Unit of measure is an attribute of a master data type, such as Product. is correct.
The unit of measure is fundamentally an attribute that belongs to a master data type. For instance, a "Product" master data type will have attributes defining its base unit of measure. When configuring conversions, you also create additional master data types, such as a "Target Unit of Measure" master data type, and use composite master data types to link products with their conversion factors to target UOMs .

D. Analytics provide the user with the option to select the target unit of measure. is correct.
In SAP IBP, the analytical tools and planning views are designed with user flexibility in mind. When viewing key figures that have been configured for conversion (e.g., using "Automatic" conversion mode), the system allows the end-user to dynamically select the target unit of measure in which they want to see the data displayed, either in the SAP IBP add-in for Microsoft Excel or in Planner Workspaces .

❌ Incorrect Answers Analysis

C. Units of measure are usually not time-independent. is incorrect.
This statement is the direct opposite of the correct consideration. As explained for option A, UOMs and their conversion factors are typically time-independent. Using time-dependent UOMs would be an exception, not the rule .

E. Conversion to the target unit of measure is handled by SAP IBP Excel UI is incorrect.
The SAP IBP Excel add-in is the user interface where the converted data is displayed and where the user can select the target UOM. However, the actual conversion calculation is handled by the SAP IBP system engine. The conversion is performed in the background using functions like IBP_CONVERSION, which are configured in the planning area and applied to the relevant key figures. The Excel UI itself does not perform the mathematical conversion .

Reference
These considerations are standard aspects of UOM configuration in SAP IBP, as documented in the SAP Help Portal and SAP Learning materials. The process involves setting up master data types and attributes, defining conversion factors as time-independent key figures, and configuring the system so that analytics can display the converted values based on user selection

Explanation:

A. New instances of templates allow for re-use of the same processes:
This is the core purpose of a template. Once you define the phases of your S&OP cycle (e.g., Demand Review, Supply Review, Executive S&OP), you do not need to recreate them every month. You simply create a new instance from the existing template for the current month or quarter.

C. Each step depicted in the template can have tasks associated with it:
Within each process step, you can define specific Tasks. These tasks can be assigned to individual users or groups, have due dates, and require formal "completion" in the system to track the progress of the S&OP cycle.

Why the Other Options are Incorrect

B. All process templates are assigned to dashboards:
While you can monitor process progress via the "Process Modeling" or "Manage Process Instances" apps, templates are not required to be assigned to Dashboards. Dashboards are visualization tools for analytics, whereas process templates are structural tools for workflow.

D. The S&OP process step can be started with an application job:
This is a common misconception. While you can schedule Application Jobs (like a Heuristic run or a Forecast run) to occur during a process, the process step itself is typically moved from "Scheduled" to "In Progress" manually by a process owner or automatically based on timing/task completion, rather than being triggered as a background "Application Job."

References

SAP Help Portal: Process Management > Managing Process Templates and Instances.
SAP IBP100 Training Manual: Unit 5, "Process Management," which covers the creation of templates, steps, and tasks.

Explanation:

B. Results of time series analysis is correct.
Demand sensing builds upon the mid- to long-range statistical forecast, which is essentially the "results of time series analysis." The demand sensing process takes the consensus demand plan (which itself is derived from statistical forecasting and time series analysis) as a foundational input . It then refines this baseline forecast by incorporating near-term signals to create a more accurate short-term prediction. The system uses lag-based snapshots of the consensus demand to analyze how past forecasts correlate with actual sales, optimizing the forecast for the near future .

C. Open Sales Orders is correct.
One of the primary inputs to the demand sensing process is the most recent demand signals from internal sources, specifically the quantity in open sales orders . This "open order signal" provides real-time visibility into actual customer demand that has already been placed but not yet fulfilled . By incorporating open sales orders, demand sensing can adjust the statistical forecast to reflect committed demand, significantly improving short-term forecast accuracy.

❌ Incorrect Answers Analysis

A. Forecast Accuracy measures is incorrect.
Forecast accuracy measures (such as MAPE or bias) are typically outputs of the forecasting process used to evaluate performance, not inputs to the demand sensing calculation itself . While these measures help planners monitor and refine forecast models over time, they are not direct data points that the demand sensing algorithm consumes when generating its short-term predictions.

D. Consensus Demand is partially related but incorrect for this specific question.
While consensus demand is indeed a foundational input to demand sensing , the question specifically asks for inputs to the demand sensing process. The results of time series analysis (option B) more accurately represents the statistical forecast that feeds into demand sensing. Consensus demand typically incorporates additional inputs like market intelligence and commercial insights, making it a broader concept than the statistical time series results that serve as the direct algorithmic input.

Reference
According to SAP Learning materials, "The demand sensing algorithm is primarily used for demand forecasts for a shorter period such as four to eight weeks, based on the consensus demand and the most recent demand signals retrieved from the ERP system, for example, the quantity in open sales orders" . The process requires both historical sales signals (past time series data) and current open order signals as mandatory inputs

Explanation:

B. To filter using attributes that have a large number of values:
In large supply chains, a single attribute like "Product ID" might contain thousands of entries. Scrolling through this list is inefficient. A cascading filter allows the system to narrow down these long lists based on a higher-level selection (like "Product Family"), making it manageable for the user.

D. To filter attributes based on other attribute filters:
This is the definition of "cascading." When you select a specific Region (e.g., EMEA) in the first filter, the second filter for Country will automatically update to show only countries within EMEA (e.g., Germany, France) rather than the entire global list.

Why the Other Options are Incorrect

A. To filter attributes based on specific values:
This is the function of a Standard Filter. All filters are used to select specific values; the "cascading" designation specifically refers to the relationship between multiple filters, not just the act of picking a value.

C. To filter data in an Application Job template:
Cascading filters are a Front-End (UI) feature used specifically in the SAP IBP Excel Add-In or Web-Based Planning to improve user experience. Application Job templates use "Value Help" or "Static Filters" but do not utilize the interactive cascading logic found in the Planning View settings.

References
SAP Help Portal: User Interface > Excel Add-In > Using Filters in the Planning View > Cascading Filters.

Explanation:

When you enable the change history feature for a key figure in SAP IBP, the system begins tracking a comprehensive set of metadata whenever the value of that key figure is modified. This creates an audit trail that helps planners understand the evolution of their planning data .

B. Modified date is correct.
The change history functionality explicitly captures the timestamp of when a change occurred. This is tracked as "Modified date" in the change history logs, allowing users to see exactly when specific adjustments were made to key figure values .

D. Reason code is correct.
Reason codes are a key feature integrated with change history in SAP IBP. When users make changes to planning data in interfaces like the Excel add-in, they can specify a reason code at the time of saving. These reason codes are then captured in the change history, providing context about why a particular change was made (for example, "Promotion" or "Market Intelligence") .

E. Attributes is correct.
Change history tracks changes in the context of the planning object's attributes. When viewing change history, you can filter by various attributes (such as Product ID, Customer ID, or Location) to see changes to specific key figures across different dimensions of your planning data .

❌ Incorrect Answers Analysis

A. Key figure type is incorrect.
The key figure type (such as "stored" vs. "calculated") is a configuration property of the key figure itself, not something that change history tracks over time. Change history focuses on tracking changes to values and the circumstances around those changes, not the static technical properties of the key figure .

C. Scenario ID is incorrect.
While SAP IBP does use scenarios for what-if analysis and versioning, Scenario ID is not listed among the standard data elements captured by change history. The change history functionality captures modified by user, modified date, modified value, attributes, key figures, time periods, reason code, and comment, but not Scenario ID .

Reference

According to SAP Learning materials, when change history is enabled for a key figure, the system captures the following data: "Modified by user, Modified date, Modified value, Attributes, Key figures, Time periods, Reason code, Comment" . This confirms that Modified date, Reason code, and Attributes are all trackable data points.

Explanation:

To generate an accurate forecast, SAP IBP uses Forecasting Steps within a Forecast Model. These steps include pre-processing algorithms designed to handle "noise" in historical data.

A. Substitute Missing with Mean or Median in Sales History:
This is a core feature of the Substitute Missing Values pre-processing algorithm. If a data point is missing (e.g., due to a data entry error or system downtime), the algorithm can replace the null value with a mean, median, or a specific constant. This prevents the forecasting model from interpreting a "0" as a genuine drop in demand.

C. Promotion Sales Lift Elimination:
This is handled by the Promotion Elimination pre-processing step. Significant spikes in history caused by one-time marketing promotions are not "organic" demand. This step identifies and removes these "lifts" so the statistical forecast is based on the underlying baseline demand rather than temporary promotional peaks.

Why the Other Options are Incorrect

B. Intermittency Detection and Correction:
While SAP IBP has models specifically designed for intermittent demand (like Croston’s Method), "Intermittency Detection" is not a standalone pre-processing step used to "cleanse" data. It is a characteristic of the demand pattern that the forecast model itself is chosen to handle.

D. Bias Detection and Correction:
Bias is typically calculated as an Ex-Post forecast error measure (comparing a previous forecast to actuals). While you can calculate bias to improve future models, it is not a standard pre-processing algorithm used to cleanse historical sales data before the forecast runs.

References
SAP Help Portal: Demand Planning > Statistical Forecasting > Preprocessing Steps.
SAP IBP100 Training Manual: Unit 4, "Demand Planning," Lesson on "Preparing Historical Data."

Explanation:

When creating a planning view in SAP IBP, the time levels you can select are determined by the time profile associated with your planning area. The time profile defines all available time buckets (such as days, weeks, months, quarters, and years) that can be used for managing planning data .

However, while the time profile makes all these levels technically available, the actual selection in a planning view is restricted by global configuration parameters. Specifically, the planning area configuration includes planning horizons that limit how many periods in the past and future can be displayed for each time level .

Here's why the other options are incorrect:

A. Only base time levels of the planning area ❌
This is incorrect because planning views are not limited to just the base (most granular) time level. You can select any time level defined in the time profile, from the most granular (e.g., days) to the highest aggregation level (e.g., years) .

B. All time levels available in the time profile ❌
This is partially correct but incomplete. While all time levels are technically available from the time profile, the system restricts them through configuration parameters. The global configuration, specifically the planning horizons set in the planning area, defines how many periods can be viewed for each time level .

D. Only time levels from the base planning level of selected key figures ❌
This is incorrect because key figures in SAP IBP can be aggregated or disaggregated across different time levels. The system supports viewing data at various time levels regardless of the base planning level of individual key figures .

Reference
The time profile configuration in SAP IBP defines multiple levels (e.g., day, week, month, quarter, year), and users can select any of these levels when creating a planning view . However, the actual display horizon (how many periods are shown) is controlled by the planning horizons configured in the planning area, which acts as a global configuration parameter restricting the view