SAP Updated C_TS422_2023 Exam Questions and Answers by ozzy

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.

In SAP S/4HANA repetitive manufacturing,reporting point confirmation(e.g., via transaction MFBF) tracks progress at specific milestones. Prerequisites include:

Activating the reporting point backflush in the work centers(B): The work center (transaction CR02, Basic Data tab, field: Backflush) must have backflushing activated (e.g., "Reporting Point Backflush" indicator). This enables goods movements (e.g., component consumption) at reporting points during confirmation, a key REM feature.

Defining the operations as reporting points using the control key(D): In the rate routing (CA21), operations designated as reporting points require a control key (field: Control Key) with the "Reporting Point" indicator checked (configured in OPJ8). This marks the operation as a confirmation milestone (e.g., RP01 control key).

Order-dependent parameters(A) apply to discrete manufacturing (OPL8), not REM, where the REM profile (OSP2) governs backflushing, not reporting points specifically.Defining work centers in the routing(C) is standard but insufficient without the control key specifying reporting points. This is per SAP’s REM confirmation process.

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.

The material type in SAP S/4HANA (selected in MM01, configured via OMS2) defines a material’s properties and behavior:

Which document types and class categories are allowed(A): Material type determines which business documents (e.g., purchase orders, production orders) can be created and which classification categories (e.g., batch, variant) apply. For example, "FERT" allows production orders, while "NLAG" (non-stock) restricts inventory documents (configured in Logistics - General > Material Master > Define Attributes of Material Types).

Which material master screens appear and in which sequence(C): Material type controls the views available in the material master (e.g., MRP for "FERT," no Sales view for "ROH") and their order, based on Customizing (OMS2, field selection and view sequence). This tailors the interface to the material’s purpose.

Plant-specific and plant-independent statuses(B) are managed via material status (Basic Data view), not material type—type defines broader attributes.Whether produced in-house or procured(D) is set by the Procurement Type (MRP 2 view), not directly by material type, though type may imply defaults (e.g., "ROH" for procurement). This is per SAP’s material type definition.