C_TS422 Exam Questions: Free SAP System Tasks [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.

Resolution:

1. Open the material BOM in change mode.
2. Select the component item with the incorrect category and delete it.
3. Create a new component item using the correct item category and save the BOM.

Prevention Tip: Always verify the item category (e.g., stock, non-stock, variable-size) before saving the BOM, as this cannot be modified later.

Resolution:

1. Open the component overview tab in the production order.
2. Enter a valid goods issue storage location for the backflushed component.
3. Postprocess the error record from the failed automatic goods movement to complete the issue.
4. Interaction path: Component Overview tab / COGI

Prevention Tip: Maintain the issue storage location in the material master or assign it via the production supply area to enable automatic determination.