SAP Integrated Business Planning (C_IBP_2601): System Tasks & Free Practice Questions 2026

Step-by-Step Execution:

1. Open the Manage ABC/XYZ Segmentation Rules app and create a new segmentation profile.
2. Set the Target Attribute for Segmentation Results to the ABC code attribute of your master data.
3. Select the segmentation measure and set the calculation level.
4. Define the segmentation method as "By Pareto Principles (Sorted and Cumulated %)".
5. Specify the threshold percentages for segments A, B, and C, ensuring XYZ segmentation is turned off.
6. Save the profile and navigate to the Application Jobs app.
7. Schedule the ABC/XYZ Segmentation job, selecting your newly created profile in the parameters.
8. Open the Manage Master Data app to verify that the ABC codes have been successfully assigned to the products.

Example Values:

• Target Attribute: ABCCODE
• Segmentation Measure: Actuals Qty
• Segmentation Method: (1) By Pareto Principles (Sorted and Cumulated %)
• ABC Segments (Thresholds): A = 20%, B = 50%, C = 30%

Expected Result: The ABC/XYZ Segmentation application job runs successfully, calculating the segments and updating the Product master data with the correct ABC classification codes based on the chosen thresholds.

Quick Mistakes:

• Selecting an attribute combination for classification that is not a proper subset of the attributes in the base planning level of the selected key figure.
• Using the "By Segmentation Measure (Single Values)" method when the goal is to sort and cumulate data, as this method sums values and compares them one by one to absolute thresholds instead of relative percentages.

Exam Insight:

• Configuration parameters of ABC/XYZ segmentation profiles and application jobs.
• Understanding the business benefits of segmentation, such as assigning appropriate forecast models, defining segment-specific alerts, and analyzing forecast accuracy by product segments.

Step-by-Step Execution:

1. Select your configured planning area from the list on the left side of the screen.
2. Choose Check, then select the With Dependencies option.
3. Review the application log by clicking the hyperlink in the Last Action Status column to ensure no errors exist.
4. Choose Activate, then select Full Scope, With Dependencies.
5. Confirm the system warning popup that asks if you are sure you want to activate.
6. Monitor the Application Logs to verify the activation was successful.

Expected Result: The planning area transitions from an inactive to an active state, creating generated objects in the database and a new full historical state.

Quick Mistakes:

• Ignoring errors in the consistency check log and trying to force an activation, which will fail.
• Activating without dependencies when new foundational objects (like a new time profile or master data type) were just added to the scope.
• Forgetting that an active planning area must contain at least one stored key figure.

Exam Insight:

• Tests the understanding that modifying operations are grouped, and all affected objects validate their relationships internally and externally before transitioning from an inactive to an active state.
• This is a core administrative concept because missing key figure request-level calculations or inconsistent attribute assignments will block the entire model from being used.

Step-by-Step Execution:

1. Open the Master Data Types app and choose New, then select Compound.
2. Enter the new ID, Name, and Description in the header fields.
3. In the Add Simple Master Data Types area, select the two component simple master data types you wish to combine.
4. Verify that the key attributes of the chosen component master data types are automatically added and set as keys under Assigned Attributes.
5. Add any additional non-key attributes if necessary for this compound level.
6. Choose Save to finalize the creation.

Example Values:

• ID: T##CUSTOMERPRODUCT
• Components: T##CUSTOMER and T##PRODUCT
• Automatically Assigned Keys: T##CUSTID, T##PRDID

Expected Result: The compound master data type is successfully saved, automatically inheriting the key attributes of its component simple master data types.

Quick Mistakes:

• Forgetting to activate the component master data types before using them in a compound master data type.
• Attempting to set a decimal attribute as a key attribute.
• Trying to assign a virtual master data type as a component, which is not permitted.

Exam Insight:

• Tests the understanding that a compound master data type must have all key attributes of its component master data types set as keys and cannot have any additional key attributes.
• This is important because it dictates how SAP IBP validates combinations of planning attributes during data loads.

Step-by-Step Execution:

1. In the Master Data section of the SAP IBP ribbon, choose Master Data Workbook and select Create.
2. Select the Production Source Header master data type and choose OK.
3. Enter the Co-Product ID, Location ID, and the exact Source ID used by the main product.
4. Set the Output Product Coefficient to represent the yield ratio and enter C in the Production Source Type Indicator field.
5. Choose Save Changes to update the database.
6. In the Application Jobs section, choose SOP Operator, then Run, select the Time-Series-Based Supply Planning Heuristic, and choose Run.

Example Values:

• Co-Product ID: T-C##
• Output Product Coefficient: 2
• Production Source Type Indicator: C

Expected Result: Following the heuristic run, the Production Receipts key figure for the co-product updates proportionally based on the primary product's production volume, without requiring additional component inputs.

Quick Mistakes:

• Setting the Production Source Type Indicator to P (Production) instead of C (Co-Product) for the secondary product.
• Using a different Source ID for the co-product; both the main product and co-product must share the exact same Source ID.
• Expecting the infinite heuristic to trigger production based on demand for the co-product (the heuristic only triggers production based on net demand for the main product).

Exam Insight:

• Evaluates the understanding of co-product modeling within SAP IBP.
• Tests the critical knowledge that co-products must share the Source ID with the main product, use indicator 'C', and that the heuristic satisfies co-product demand solely from stock generated by main product production.

Step-by-Step Execution:

1. On the SAP IBP ribbon, choose Master Data Workbook and select Edit.
2. Select the Production Source Header master data type from the drop-down list and choose OK.
3. Filter the view for your specific Location ID and Product ID.
4. Locate the specific Source ID associated with the external vendor.
5. Enter 0.3 in the Production Ratio field to represent 30% of the net demand.
6. Set the Source Type indicator to U (Unspecified) and choose Save Changes.

Example Values:

• Location ID: 2300
• Source ID: T-B3##_2300_VEND
• Production Ratio: 0.3
• Source Type: U

Expected Result: During the next supply heuristic run, 30% of the net demand for the product at the specified location is fulfilled via the Unspecified Receipts/External Procurement key figure, bypassing normal upstream network propagation.

Quick Mistakes:

• Setting the Source Type to P (Production) for the vendor, which would prompt the heuristic to look for lower-level components rather than assuming unlimited external supply.
• Failing to ensure that the sum of all sourcing quotas (P-rules, T-rules, and U-rules) for the product at that location exactly equals 1 (or 100%).

Exam Insight:

• Tests the candidate's understanding of multi-sourcing capabilities and the specific function of the U-Rule.
• Highlights the critical concept that U-rules stop upstream network propagation while still making supply available from an external, unspecified source.