C-TS422-2023 SAP Practice Questions

The Alert Monitor is a central tool for exception-based planning in PP/DS. It does not solve problems automatically but actively identifies and displays them based on a configurable alert profile. Planners use the monitor to see issues like date conflicts, capacity overloads, and pegging problems, and can often navigate directly from the alert to the relevant planning tool to resolve the issue.

True. A Master Recipe can be created with a 'charge quantity' and can have multiple materials assigned to it in the material-recipe assignment. This allows a single recipe, which defines the process steps, to be used for a family of similar products that follow the same production process, even if their component quantities or finished product codes differ. The specific product is determined when the process order is created.

Long-Term Planning (LTP) is the standard tool used for simulative planning runs. It allows planners to create one or more inactive planning scenarios, copy demand programs (like forecasts), and run a simulative MRP. The results (simulative planned orders, capacity loads) are stored in separate planning tables and do not impact the live, operative MRP environment. This allows for what-if analysis on future demand.

This is the correct and complete setup. The core of reporting point functionality lies in the rate routing. The specific operations that serve as reporting points must be assigned a control key that is configured for milestone/reporting point confirmation. This tells the system that quantities will be confirmed at these steps. The Repetitive Manufacturing Profile assigned to the material must also be configured to allow for reporting point backflushing, which controls the posting of activities and goods issues.

The most efficient way to handle this requirement is by using a planning heuristic combined with a correctly configured strategy profile. The strategy profile allows you to define priorities for different demand categories (like sales orders vs. forecasts). Setting 'Sales Order' as the top priority and enabling the 'Insert operations' or 'Reschedule operations' setting ensures the heuristic will automatically de-allocate and reschedule capacity from lower-priority orders to fulfill high-priority demands. The optimizer could also work but is more complex to set up and computationally intensive for a standard nightly run. A background MRP Live run and fixing pegging relationships are related but do not directly address the automatic preemption of capacity.

Even if the change number is correctly configured, the production version itself plays a key role. If the production version selected for the order has a validity that starts before the change number's effectivity and is not set up to be sensitive to engineering change management, the system may use the BOM structure that was valid when the production version was created or last maintained. To resolve this, the existing production version might need to be updated with a new validity period or a new production version created that is valid from the change number's effective date.

The automatic KANBAN calculation based on dependent requirements is specifically designed for this purpose. The system analyzes the dependent requirements (generated by MRP from planned/production orders for finished goods) within a specified evaluation period. It then proposes the number of KANBANs and the KANBAN quantity needed to cover that demand, considering the replenishment lead time and a safety factor. This allows the KANBAN loop to be self-adjusting to actual demand fluctuations.

Regenerative planning is achieved by using Planning Mode '3 - Delete and Recreate Planning Data', which re-explodes the BOM and routings for all selected materials. To limit the scope of the run to materials managed by a specific MRP controller, a filter must be applied in the 'Material Scope' section of the MRP Live parameters. This ensures only the intended materials are planned.