SAP SAP Certified Application Specialist C_TS422_2023 New Questions

SAP S/4HANA offers automation options to streamline production order processing:

You can use trigger points to automatically create rework orders via confirmations(A): Trigger points (configured in routing via CA02, Extras > Trigger Points) are events linked to operations. For example, a trigger point can be set to create a rework order (order type defined in Customizing) automatically when a confirmation (e.g., CO11N) indicates a quality issue, enhancing process efficiency.

You can use mass processing to set production orders to technically complete(B): Transaction COHV (Mass Processing of Production Orders) allows users to select multiple orders and execute the "Technically Complete" function (TECO), automating status updates without manual intervention per order.

The production scheduling profile(C) (Customizing: Production > Shop Floor Control > Master Data > Define Production Scheduling Profile) controls scheduling and confirmation settings but cannot automatically set orders to "Technically Complete"—this requires manual or mass action.Mass processing to read PP master data(D) is not a standard function—COHV updates order data, not reads master data for automation. This is per SAP’s production automation features.

In SAP S/4HANA’sgraphical planning table(e.g., CM21 or PP/DS Planning Board, /SAPAPO/CDPS0), inserting an operation withforward planning direction(start from a fixed date and schedule forward) at a specific time on a work center with an existing operation:

The new operation is inserted at the desired time; the previously dispatched operation is moved forward(C): With forward scheduling (configured in the strategy profile, e.g., /SAPAPO/CDPSC11, Planning Direction: Forward), the system inserts the new operation at the specified time (e.g., via drag-and-drop). To maintain capacity feasibility, the previously dispatched operation is shifted forward (later in time) to avoid overlap, respecting the work center’s finite capacity (CR02, "Relevant to Finite Scheduling" checked).

Options A and B (leaving the existing operation unchanged) would violate finite scheduling rules, causing overlaps. Option D (moving backward) contradicts forward planning, which schedules from the start point onward. This is per SAP’s dispatching behavior in graphical tools.

Material Requirements Planning (MRP) in SAP S/4HANA calculates net requirements to determine material shortages or surpluses by comparing the available stock and scheduled receipts against requirements. During this calculation, MRP considers existingproduction orders(A) because they represent firm commitments to produce materials, and their quantities directly influence the availability of components and finished goods. Similarly,planned orders (firmed)(B) are included as they are confirmed planning proposals that have been manually or automatically fixed, ensuring they are treated as reliable supply elements in the net requirement calculation.

Planned orders (unfirmed)(C) are not considered firm receipts because they are still tentative and subject to change during subsequent MRP runs, so they are excluded from the net calculation unless firmed.ATP (Available-to-Promise) quantities(D) are used in availability checks for sales orders, not directly in MRP’s net requirement calculation, which focuses on stock and scheduled receipts rather than promise-based quantities. This aligns with SAP’s MRP logic as outlined in the SAP S/4HANA Production Planning documentation, emphasizing firm supply elements.

For a make-to-order (MTO) scenario in SAP S/4HANA without forecasting, where components have different procurement behaviors:

Choose planning strategy 20 (Make-to-Order) and select the corresponding Individual/Collective indicator(D): Strategy 20 (material master, MRP 3 view, Strategy Group: 20) is pure MTO, where production is triggered by sales orders (VA01) without PIRs—fitting the "no forecasting" requirement. TheIndividual/Collective indicator(material master, MRP 4 view, field: Ind./Coll.) is set to "1" (Individual Requirements) for the component procured per sales order, generating separate dependent requirements per order, and "2" (Collective Requirements) for the component procured jointly, aggregating requirements across all orders into a single planned order or requisition.

Planning strategy 50 (Planning without final assembly)(A, C) relies on PIRs for subassemblies, conflicting with the "no forecasting" condition.Mixed MRP indicator(B, C) (MRP 4 view) applies to mixed MTS/MTO scenarios (e.g., strategy 11), not pure MTO, and doesn’t address the individual/collective split directly. Strategy 20 with the indicator meets SAP’s MTO configuration standards.