SAP C_TS422_2023 Practice Test Questions Answers

In SAP S/4HANA PP/DS, achieving a feasible production plan under capacity constraints involves:

Determine a time period with available capacity on the planning board(C): Using the DS Planning Board (/SAPAPO/CDPS0), planners can visually identify periods with free capacity on resources and manually or automatically schedule orders into those slots, ensuring feasibility.

Increase the capacity supply in a time-phased interval(D): In the work center (CR02, Capacity tab) or PP/DS resource (/SAPAPO/RES01), you can define additional capacity (e.g., shifts, overtime) for specific time intervals via capacity variants, allowing more orders to fit within constraints.

Form optimum sequences to reduce setup times(E): Using heuristics (e.g., SAP_PP_020) or the PP/DS Optimizer, you can sequence operations on resources to minimize setup times (defined in routing, CA02), maximizing throughput and resolving capacity bottlenecks.

Execute an infinite planning run(A) ignores capacity constraints, creating an unfeasible plan requiring later adjustment—not a solution.Reduce the planning time interval(B) (e.g., horizon in /SAPAPO/CDPSC11) limits scope but doesn’t address capacity directly. This is per SAP’s PP/DS capacity planning strategies.

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.

In SAP S/4HANA Advanced Planning (PP/DS),peggingis a key concept that links supply (receipts) to demand (issues) across the production structure. It is defined as:

An evaluation that is ordered according to the bill-of-material structure of all related products and represents the relationship between the receipt and the issue elements(A): Pegging (visible in /SAPAPO/RRP3 or Product View) assigns receipt elements (e.g.,planned orders, stock) to issue elements (e.g., sales orders, dependent requirements) based on the BOM hierarchy. It follows the BOM structure (top-down or bottom-up) to ensure each demand is covered by a specific supply, maintaining traceability and sequence (e.g., fixed or dynamic pegging).

Option B (overstock situations) relates to stock analysis, not pegging’s core purpose. Option C (network structure) is inaccurate—pegging uses BOM, not a network, and focuses on assignment, not just coverage. Option D (shortages) is a result of planning, not pegging’s definition, which is about linking, not identifying gaps. This aligns with SAP’s PP/DS pegging documentation.

In SAP S/4HANA, the MRP planning file (table MDVM, visible via MD05) tracks changes that trigger MRP to re-evaluate a material’s planning situation. Entries are created when:

Changing the procurement type in the product master(C): The procurement type (material master, MRP 2 view, field: Procurement Type) determines whether a material is produced in-house ("E"), procured externally ("F"), or both ("X"). Changing it (e.g., via MM02) affects how MRP generates planned orders or purchase requisitions, so an entry is added to the planning file (e.g., NETCH or NETPL indicator) to prompt recalculation.

Changing the stock in inventory management(D): Any stock change (e.g., goods receipt via MIGO, goods issue via MB1A) updates the available stock (MD04). This triggers an MRP planning file entry because it alters the net requirements calculation, requiring MRP (MD01/MD02) to reassess supply versus demand.

Changing the delivery address in transportation management(A) affects logistics execution (e.g., shipment documents), not MRP planning directly—no entry is created.Changing the storage bin in warehouse management(B) (e.g., via LT10) is a WM-level movement that doesn’t impact MRP unless stock quantity changes, which falls under (D). This is per SAP’s MRP planning file logic.

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.