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

Explanation:

In SAP IBP, a Compound Master Data Type is a relationship-based object. It does not have its own unique primary key; instead, its primary key is formed by combining the keys of other "Simple" MDTs.

SOURCELOCATION (A):
This defines a transport lane. Its key is a combination of Product ID, Ship-To Location ID, and Ship-From Location ID. Because it relies on these external keys to exist, it is a compound type.

SOURCECUSTOMER (C):
This defines the supply link to a customer. Its key is a combination of Product ID, Customer ID, and Ship-From Location ID. Like SOURCELOCATION, it represents a specific valid combination of existing simple master data.

Why the Other Options are Incorrect

B. SOURCECUSTGROUP:
In the SAPIBP1 sample model, this is typically a Simple Master Data Type. While it relates to sourcing, it is defined by its own unique identifier (Source ID) to represent a group, rather than being a mandatory concatenation of other master data keys.

D. SOURCEPRODUCTION:
This is a Simple Master Data Type. It uses a unique Source ID (the Production Source ID) as its primary key. While it contains attributes like "Production Lead Time," it is an independent entity in the data model rather than a compound of Product and Location keys.

References
SAP Help Portal: Refer to Model Configuration > Master Data Types > Compound Master Data Types.

Explanation:

B. Jobs in the Applications Jobs app is correct.
The SAP IBP 2305 release introduced features for targeted job management. Administrators can now define job definitions that control the parameters and complexity of application jobs. These definitions can be assigned to users, and planners can trigger and manage these defined jobs directly from their planning interface without needing to navigate the full Application Jobs app . This creates a direct link between planning filters and specific, pre-defined jobs.

C. Planning view templates in the SAP IBP add-in for Microsoft Excel is correct.
The 2305 update for the SAP IBP add-in for Microsoft Excel enhanced filtering capabilities across planning views. You can now use a workbook filter that applies attribute-based filters to all worksheets (planning views) within a workbook. This allows you to manage filters at the workbook level and use saved planning filters to ensure consistency across multiple planning views .

❌ Incorrect Answers Analysis

A. Supply chain graph in Supply Chain Network app is incorrect.
While the 2305 release introduced features for supply chain modeling like subcontracting, there is no information in the provided documentation indicating that planning filters can be applied directly to the visual supply chain graph itself. This feature is more closely related to master data and network modeling rather than data filtering .

D. Snapshot operator in the SAP IBP add-in for Microsoft Excel is incorrect.
The Snapshot operator is a planning function used for copying and freezing key figure data at a specific point in time. While the new workbook filtering capabilities apply to planning views, they do not directly interact with or filter the results of planning operators like the Snapshot operator .

Reference
These features are documented in the SAP IBP 2305 release highlights, specifically under "Efficient Filtering Across Planning Views in the SAP IBP, add-in for Microsoft Excel" and "Targeted Job Management using Job Definitions in Planner Workspaces"

Explanation:

A. Transportation Lead Times:
The heuristic always respects time offsets. If it takes 2 weeks to ship a product from a DC to a Customer, the heuristic will correctly offset the Net Demand at the source to meet the Customer Demand on time.

C. Minimum Lot Size:
Even though the heuristic is "infinite" regarding capacity, it respects basic inventory lot-sizing rules. If the net demand is 50 units but the Minimum Lot Size is 100, the heuristic will calculate a supply of 100 units.

D. Adjusted Transport Receipts:
This is a "Manual Override" key figure. If a planner manually enters a value in an Adjusted key figure, the heuristic is forced to respect that value as a hard constraint, overriding its own calculated supply.

Why the Other Options are Incorrect

B. Maximum Lot Size:
Interestingly, the Infinite Heuristic ignores Maximum Lot Sizes. It focuses on fulfilling all demand; therefore, it will not "cap" the supply. Only the Optimizer or the Finite Heuristic typically respect maximum constraints to prevent overloading.

E. Aggregated Constraints:
These are advanced constraints (like total market capacity or product group limits) used exclusively by the Supply Planning Optimizer. The Heuristic calculates supply purely at the location-product level and does not recognize multi-level aggregated limits.

References
SAP Help Portal: Time-Series-Based Supply Planning > Heuristic vs. Optimizer Comparison Table.

Explanation:

B. Supply Heuristics in SAP IBP for sales and operations is correct.
The safety stock outputs calculated by the Multistage Inventory Optimization (IO) operator are fundamental inputs for downstream supply planning processes. After inventory optimization determines the optimal safety stock levels across the multi-echelon network, these recommended values (typically stored in key figures like RECSAFETYSTOCK) are consumed by supply planning heuristics and optimizers to create a feasible time-series supply plan that accounts for these target stock levels .

D. Demand Sensing with Gradient Boosting (Full) is correct.
While Demand Sensing and Inventory Optimization are distinct modules, they are part of an integrated planning flow. The Demand Sensing operator uses advanced machine learning (Gradient Boosting) to generate short-term, forward-looking forecasts. These more accurate sensing outputs serve as critical inputs to the Multistage Inventory Optimization process. In other words, the safety stock calculation depends on the forecast error and demand variability generated by Demand Sensing .

❌ Incorrect Answers Analysis

A. Decoupling Points determination in SAP IBP for demand-driven replenishment is incorrect.
Decoupling point determination is a concept within Demand-Driven MRP (DDMRP) used to position inventory buffers in the supply chain to protect against variability. While SAP IBP supports these concepts, the direct outputs of the Multistage Inventory Optimization (like recommended safety stock) are not sent to determine decoupling points; rather, they are the result of positioning strategies and network modeling. The optimization algorithm calculates safety stock for nodes that are already defined in the network model .

C. Charts creation in SAP Supply Chain Control Tower is incorrect.
The SAP Supply Chain Control Tower is an analytics and monitoring application that visualizes data, creates charts, and manages alerts based on planning data . While the Control Tower can display inventory-related charts and KPIs (like safety stock levels), the safety stock outputs themselves are not "sent" to the Control Tower for chart creation as a primary process. Chart creation is a downstream visualization activity, not a receiving process for safety stock calculations .

Reference
The sequence of operations in SAP IBP for inventory is well-documented: (1) Calculate forecast error (e.g., from Demand Sensing or historical data), (2) Run Global (Multistage) Inventory Optimization to calculate safety stock, and (3) Use those outputs in Supply Heuristics or other planning operators . The recommended safety stock becomes a target for the supply plan to meet .

Explanation:

C. Sourcing in Production Source Item:
The algorithm verifies that for every Production Source Header, there are corresponding Production Source Items (components). Without this link, the system cannot "explode" the Bill of Materials (BOM) to calculate component demands.

D. Detection of Cycles:
A "cycle" occurs when Product A is a component of Product B, and Product B is simultaneously a component of Product A (circular logic). The Check Mode identifies these loops in the supply chain network, which would otherwise cause the planning heuristic to run indefinitely or fail.

E. Planning Level Master Data:
This checks the alignment between Key Figures and Master Data. If a Key Figure is populated at a specific planning level (e.g., Product-Location-Customer), but the corresponding Master Data records for those combinations are missing, the Check Mode will flag this discrepancy.

Why the Other Options are Incorrect

A. Customer Sourcing Rules:
While the heuristic uses these rules to calculate supply, the Check Mode specifically focuses on the structural integrity of the master data (like missing entries or circularity) rather than validating the logical "connectedness" of every possible customer sourcing path.

B. Location Resource Cycles:
In SAP IBP, cycles are generally checked at the node level (Location-Product) where material flows, rather than focusing on "Location Resources" forming a cycle. Resources are capacity constraints, not flow-directing entities that create network loops.

References
SAP Help Portal: Time-Series-Based Supply Planning > Preprocessing and Master Data Validation > Check Mode.

Explanation:

SAP IBP provides several methods for ABC segmentation, which are accessible when creating a segmentation profile in the Manage ABC/XYZ Segmentation Rules app. These methods determine how planning objects (like products or location-products) are grouped based on the value of a selected key figure, such as revenue or sales volume .

A. By Number of Items (Sorted Values) is correct.
This method calculates the segments based on the number of items that produce various shares of the segmentation measure. Specifically, "By Number of Items (Sorted Values)" uses the absolute count of items to determine the segments. For example, you might assign the top 100 products by revenue to segment A, the next 200 to segment B, and the rest to segment C .

B. By Pareto Principle (Sorted and Cumulated %) is correct.
This is a commonly used method based on the Pareto principle (the 80/20 rule). It ranks planning objects in descending order of their contribution to the total value of the segmentation measure (e.g., revenue). The system then cumulates the percentages of these values and assigns them to segments (A, B, C, etc.) based on predefined percentage thresholds. For instance, the top items contributing to the first 70% of total revenue might be classified as 'A' .

❌ Incorrect Answers Analysis

C. By Number of Items (Sorted Average) is incorrect.
"Sorted Average" is not a recognized method for ABC segmentation in SAP IBP. The two methods based on the number of items are "By Number of Items (Sorted %)" and "By Number of Items (Sorted Values)" .

D. By Pareto Principle (Sorted and Calculated Values) is incorrect.
The two valid methods based on the Pareto principle are "By Pareto Principle (Sorted and Cumulated %)" and "By Pareto Principle (Sorted and Cumulated Values)". "Calculated Values" is not a standard term used for these methods .

Reference:

These segmentation methods are standard features in SAP IBP for demand and inventory planning, as documented in SAP Learning materials and the SAP Help Portal . The complete list of ABC segmentation methods in SAP IBP includes:

Explanation:

The Inventory Optimization suite calculates several specific key figures to help planners understand why inventory is being held. The "Calculate Target Inventory Components" operator specifically outputs:

A. Target Cycle Stock:
This represents the inventory held to satisfy demand between replenishment orders. It is calculated based on the frequency of orders and the batch sizes (lot sizes) defined in the system.

B. Recommended Safety Stock:
This is the most critical output. It represents the "buffer" required to protect against uncertainties in demand (forecast error) and supply (lead time variability) to meet a specific service level.

C. Target Pipeline Stock (E):
This accounts for the inventory currently "in transit" between two nodes in the supply chain (e.g., from a factory to a distribution center) or inventory currently in the production process.

Why the Other Options are Incorrect

C. Component Usage:
This is typically an input or a calculation related to the Bill of Materials (BOM) explosion in supply planning. While Inventory Optimization uses BOM data to understand demand propagation, "Component Usage" is not a primary output of the Target Inventory Components operator.

D. Reorder Point:
In SAP IBP, the Reorder Point is a specific type of replenishment logic attribute. While IO provides the inputs (like safety stock) that could be used to calculate a reorder point, the operator itself focuses on the Inventory Components (Safety, Cycle, Pipeline) rather than calculating a traditional "Reorder Point" value.

References
SAP Help Portal: Inventory Optimization > Inventory Operators > Calculate Target Inventory Components.