Free C_TS422_2601 Production Planning Practice Questions 2026

Step-by-Step Execution:

1. Enter transaction code MD74 to adjust requirements.
2. Specify the reorganization key date to set unassigned quantities to zero and flag them for reorganization.
3. Enter transaction code MD75 to reorganize schedule lines.
4. Execute the deletion of schedule lines that have a quantity of zero before the key date.
5. Enter transaction code MD76 to delete the history.
6. Determine a further key date and execute the permanent deletion of the requirements history from the database.

Example Values:

• Reorganization key date: A specified date in the past or future to limit the data removal.

Expected Result: Old and unconsumed Planned Independent Requirements are successfully adjusted, schedule lines are removed, and the history is permanently deleted from the database.

Quick Mistakes:

• Confusing the permanent reorganization deletion process with routine MRP group adjustments where planned independent requirements are ignored but still retained in the database.
• Forgetting to execute all three transaction steps in the correct sequence, which can leave zero-quantity schedule lines or history lingering in the system.

Exam Insight:

• This task tests the administrative maintenance of Demand Management and the exact transaction sequence (MD74, MD75, MD76) for PIR reorganization.
• It is important because unmanaged PIRs can cause data inconsistencies, making periodic reorganization crucial for SAP S/4HANA planning strategies.

Step-by-Step Execution:

1. Open the target SAP Fiori application from the launchpad and select the user profile icon to open the user action menu, then choose Adapt UI.
2. Right-click on a field you want to remove and select Remove to hide it from the screen.
3. Hold the Shift key, select two related fields, right-click, and choose Combine to display them side-by-side.
4. Select the Navigation tab to test the application changes as an end user.
5. Select the wand icon in the top left corner to activate a new version of the app.
6. Select the truck icon to publish the UI changes to the transport log.

Example Values:

• Application: Plan Customer Projects
• Action: Remove field, Combine fields

Expected Result: The application UI is updated to reflect the new layout, and the published changes are captured in the Extensibility Inventory app so they can be added to a software collection for export.

Quick Mistakes:

• Attempting to adapt the UI without having the Administrator or Extensibility Specialist business role assigned to your user.
• Forgetting to select the truck icon to publish the changes, meaning the adaptation will not be logged for transport to the quality or production systems.
• Making changes to the original base app when the customer only requires the changes for a specific user group or region, which requires creating a variant first.

Exam Insight: Tests knowledge of Key User In-App Extensibility capabilities, specifically runtime authoring, and the prerequisites for enabling, activating, and transporting UI adaptations.

Step-by-Step Execution:

1. Open the standard routing in change mode and navigate to the operation overview.
2. Select the specific operation that will act as the trigger (for example, a quality check operation).
3. Navigate to the operation details and open the Trigger Point assignment screen.
4. Assign a standard trigger point or copy a trigger point group designed to trigger the function.
5. Save the routing to activate the trigger point logic.

Example Values:

• Trigger Point Function: Release succeeding operations

Expected Result: A trigger point is successfully assigned to the routing operation. When a production order is executed, confirming this specific operation will automatically release all operations that follow it.

Quick Mistakes:

• Assigning the trigger point to the wrong operation, causing premature or delayed release of shop floor activities.
• Manually recreating trigger point parameters instead of copying a standard trigger point or trigger point group, which increases the risk of setup errors.

Exam Insight:

• Evaluates the ability to automate production order functions (like releasing operations, inserting reference operation sets, or starting workflows) directly from routing master data using trigger points.

Step-by-Step Execution:

1. Open the Custom Business Objects app and select New to create a new object.
2. Enter the Name for the custom business object.
3. Check the User Interface box under the Features section to instruct the system to generate an app UI.
4. Navigate to the Fields tab and add the necessary attributes to capture the asset data.
5. Select Publish to generate the object, database tables, and its corresponding UI.
6. Select the Maintain Catalogs link to jump to the Custom Catalog Extensions app and assign the object to an existing business catalog.
7. Select the Go to Generated UI link to view and test the new application.

Example Values:

• Name: Fleet Vehicle
• Feature: User Interface
• Field 1: License Plate (Text)

Expected Result: The custom business object is published, underlying database tables are generated, and a ready-to-use SAP Fiori UI is created and assigned to a catalog so users can input data.

Quick Mistakes:

• Failing to check the "User Interface" feature box before publishing, resulting in no front-end application being generated.
• Forgetting to assign the generated business object to a business catalog via the Custom Catalog Extensions app, making it completely inaccessible to users on the launchpad.
• Creating a custom business object for something that already exists in the system without checking the Graph Navigator first to see if a standard entity could simply be extended.

Exam Insight: Tests your knowledge of key user in-app extensibility, specifically the Custom Business Objects tool's capability to generate database tables, APIs, and UIs simultaneously without the need for Developer (ABAP) coding.

Step-by-Step Execution:

1. Open the MRP Live execution transaction or Fiori app.
2. Define the general planning scope for the target plant.
3. Navigate to the material selection or exclusion criteria fields.
4. Enter the specific MRP Planner assigned exclusively to the PP/DS materials in the exclusion parameters.
5. Execute the MRP Live run to process the remaining non-PP/DS materials.

Example Values:

• Plant: 1010
• Excluded MRP Planner: PPD

Expected Result: MRP Live successfully plans all standard S/4HANA materials but skips the excluded PP/DS materials, ensuring the results from the detailed PP/DS heuristic planning run are preserved.

Quick Mistakes:

• Assigning the special MRP type "X0" to the PP/DS materials to exclude them (this was the correct method in legacy SAP ECC/APO, but is no longer valid in SAP S/4HANA).
• Forgetting to execute the detailed scheduling heuristics before running MRP Live, leaving the PP/DS materials completely unplanned.
• Using a generic material selection criterion that accidentally excludes standard S/4HANA materials from the MRP Live run.

Exam Insight: This task tests your knowledge of the architectural changes in SAP S/4HANA PP/DS integration, specifically highlighting that you must use planning scope exclusions (like material numbers or MRP Planners) instead of the legacy "X0" MRP type to protect PP/DS results during an MRP Live run.