Free Practice Questions for SAP C_TS422_2023 Exam

In SAP S/4HANA PP/DS,mode selectionrefers to choosing between alternative production modes(combinations of resources and recipes) within detailed scheduling (e.g., /SAPAPO/CDPS0 or heuristics). It is used:

When alternative resources are used within one operation(B): In the PP/DS resource (mapped from work center, CR02) and operation (routing, CA02), modes define different resource options (e.g., Machine A vs. Machine B) for the same operation. Mode selection (configured in the PPM or PDS, /SAPAPO/RES01) allows PP/DS to pick the best resource based on availability, priority (Mode Priority field), or cost during scheduling.

Several operations for one product(A) involves operation sequencing, not mode selection.Several production versions(C) (MRP 4 view) define BOM/routing combinations at the material level, not within an operation.Multiple planned orders in parallel(D) relates to resource loading, not mode-specific choices. This is per SAP’s PP/DS scheduling options.

When a new MRP-relevant material in SAP S/4HANA supports both in-house production and external procurement (procurement type "X" in the MRP 2 view), MRP defaults to a specific behavior unless overridden by additional settings (e.g., source list, quota arrangement). By default,the MRP run assumes in-house production(B). This is because SAP’s standard logic prioritizes in-house production (procurement type "E") over external procurement ("F") when both are possible,unless a valid source of supply (e.g., scheduling agreement, contract) explicitly directs it to external procurement.

Option A is incorrect because external procurement requires a source list or quota arrangement to take precedence. Option C is false, as quotations are not a prerequisite for MRP planning; they are optional for external procurement. Option D is also incorrect—MRP will plan the material automatically based on its master data, not require interactive planning. This behavior is documented in SAP’s MRP processing rules.

In SAP S/4HANA Advanced Planning (Production Planning and Detailed Scheduling, PP/DS), a production planning run (transaction /SAPAPO/CDPSB0 or heuristics) generates supply elements to cover demand. Possible results include:

Planned order(A): PP/DS creates planned orders (visible in /SAPAPO/RRP3) for in-house production to meet requirements (e.g., sales orders, dependent requirements). These are detailed with exact timings and can be converted to production orders later (e.g., via /SAPAPO/PROD).

Scheduling agreement schedule line(B): For external procurement with a scheduling agreement (maintained in ME31L), PP/DS generates schedule lines (visible in ME38 or /SAPAPO/RRP3) to request delivery from vendors, aligning with precise scheduling needs.

Production order(C) is not a direct result—PP/DS creates planned orders, which are then converted to production orders manually or via a separate process (e.g., CO41).Purchase order(D) is possible in classic MRP for external procurement, but PP/DS typically generates purchase requisitions or schedule lines, not direct POs. This is per SAP’s PP/DS planning output documentation.

In SAP S/4HANA, a material availability check ensures components are available before production proceeds. This check can be triggered automatically:

By order release(C): When a production order is released (transaction CO02 or mass release via CO05N), the system can perform an availability check based on settings in the order type-dependent parameters (Customizing: Production > Shop Floor Control > Define Order Types). The "Availability Check" field (e.g., "2 - Check at Release") triggers this automatically, ensuring materials are reserved or shortages are flagged.

By mass processing(D): Using transaction COHV (Mass Processing of Production Orders), planners can execute availability checks for multiple orders simultaneously. The function "Check Material Availability" can be scheduled or run manually, automating the process across orders.

By capacity planning(A) focuses on work center capacity, not material availability.By order confirmation(B) may trigger a check for remaining quantities, but it’s not a standard automatic trigger point—it’s more relevant for backflushing or goods issue. This is outlined in SAP’s production order management documentation.

In SAP S/4HANA, when multiple valid production versions (maintained in the material master, MRP 4 view, or transaction MM02) exist during production order creation, the system follows a predefined selection logic:

Alphanumeric or quota arrangement(A): By default, the system selects the production version with the lowest alphanumeric identifier (e.g., "0001" before "0002") if no other criteria are specified. Alternatively, if aquota arrangement(transaction MEQ1) is maintained and marked as MRP-relevant, the system uses the quota percentages to distribute production across versions, overriding the alphanumeric logic. This is configured in Customizing (Production > Master Data > Production Versions).

Option B (Planned order or material number) is incorrect—planned orders inherit versions from MRP, and material number is irrelevant to version selection.

Option C (Validity period or sales order) is partially true—validity period ensures only active versions are considered—but sales orders do not directly influence version selection unless linked via a specific requirement (e.g., variant configuration), which is not standard.

Option D (Lot size or material cost) influences version selection only if defined in the production version’s lot size range, but it’s not the primary method unless customized.

This behavior is documented in SAP’s production order creation process.

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.

Phantom assemblies in SAP S/4HANA (special procurement type 50, material master MRP 2 viewor BOM item) are virtual components not physically stocked—their BOM is exploded directly into the higher-level assembly. Benefits include:

To simplify the structure of bills of material(A): By treating a group of components as a phantom (e.g., a kit), the BOM avoids an extra level of assembly, reducing complexity in planning and documentation (e.g., one BOM level instead of two).

To reduce the number of changes required in bills of material(B): Changes to a phantom’s components (CS02) automatically propagate to all higher-level BOMs using it, minimizing maintenance effort compared to updating separate subassembly BOMs.

To make the assignment of components easier(D): In production orders (CO01), phantom components are directly assigned to the parent operation, simplifying goods issue and confirmation by eliminating subassembly steps.

To reduce the number of material masters(C) is incorrect—phantoms still require a material master with type (e.g., HALB) and procurement key 50, so the count remains unchanged.To increase the number of planning levels(E) is false—phantoms reduce planning levels by bypassing subassembly production. This is per SAP’s phantom assembly usage.

In SAP S/4HANA, awork center hierarchy(transaction CR21/CR22) organizes work centers for capacity planning and evaluation:

A group of alternative work centers providing a cumulative available capacity for production(B): A work center hierarchy groups multiple work centers (e.g., CR01-defined centers) into a tree structure (e.g., a top node with sub-nodes). The system aggregates their capacities (visible in CM01) into a cumulative total, allowing planners to evaluate or assign production across the group as a single capacity pool, often used in bottleneck analysis or reporting.

Hierarchy levels by priorities(A) isn’t correct—priorities are set in routings or PP/DS, not hierarchies, which focus on capacity aggregation.Work centers in a production line sequence(C) reflects routing (CA01) or REM line hierarchy (LDM1), not a work center hierarchy.Parallel sequence for splitting quantities(D) is a routing concept (Parallel Sequence), not a hierarchy function. This is per SAP’s capacity planning documentation.

In SAP S/4HANA, an operation withDispatchedstatus (set in CM21 or PP/DS after scheduling) is assigned a fixed time slot on a work center. Options for rescheduling include:

You can reschedule the operation using finite scheduling in a planning table(C): In the capacity planning table (CM21) or PP/DS Planning Board (/SAPAPO/CDPS0), you can manually drag-and-drop or use heuristics to reschedule a dispatched operation, respecting finite capacity constraints (work center, CR02, "Relevant to Finite Scheduling").

You can reschedule the operation in the Manage Work Center Capacity app(D): This Fiori app (SAP GUI equivalent: CM25) allows planners to adjust dispatched operations’ schedules by shifting them within available capacity slots, maintaining finite scheduling rules and updating the operation’s time.

Lead time scheduling(A) (e.g., in CO02) recalculates the entire order’s basic dates, not individualdispatched operations—it’s not used post-dispatch.Infinite scheduling in a planning table(B) (e.g., ignoring capacity) isn’t typical for dispatched operations, which are already capacity-constrained. This is per SAP’s dispatching options.

In SAP S/4HANA repetitive manufacturing,line loadinginvolves planning production quantities and capacities across production lines. Options include:

Run MRP with quota arrangement(B): MRP (MD01/MD02) with a quota arrangement (MEQ1, marked MRP-relevant) distributes production quantities across multiple production lines (production versions) based on predefined quotas (e.g., 60% Line A, 40% Line B). This plans quantities and implicitly considers capacity via the linked work centers, visible inMF50.

Run PP/DS heuristics for repetitive manufacturing(D): PP/DS heuristics (e.g., SAP_PP_002 in /SAPAPO/CDPSB0) plan both quantities (e.g., creating planned orders) and capacities (e.g., finite scheduling on production lines) for REM scenarios. This integrates detailed scheduling with line loading, optimizing resource use.

Assign planned orders manually in the planning table(A) (MF50) adjusts existing quantities but doesn’t inherently plan capacities—it’s a manual tweak.Run MRP with automatic selection of production version(C) selects one version (e.g., via alphanumeric order), planning quantities but not dynamically balancing capacities across lines. This is per SAP’s REM planning options.