C_TS422_2023 Exam Dumps - SAP Certified Associate - SAP S/4HANA Cloud Private Edition, Production Planning and Manufacturing

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.

In SAP S/4HANA, during the creation of planned orders or production orders, the system relies on specific master data to determine the production process, components, and operations. The system checks the following:

In the bill of material (BOM)(C): The BOM (maintained in transaction CS01/CS02) defines the components required for production. MRP explodes the BOM to generate dependent requirements for planned orders, and production orders inherit this structure. The BOM’s validity (e.g., date, lot size) and usage (e.g., production) are verified during order creation.

In the MRP controller(D): The MRP controller (material master, MRP 1 view, field: MRP Controller) influences master data selection indirectly through its configuration in Customizing (e.g., Production > Material Requirements Planning > Master Data > Define MRP Controllers). It can determine planning parameters and production versions, affecting order creation.

In the routing(E): The routing (maintained in transaction CA01/CA02) specifies the operations, sequence, and work centers for production. During order creation, the system selects the routing to define the production process, ensuring the correct operations are assigned to the order.

In the production version(A) is critical for linking BOMs and routings, but the system checks within the BOM and routing directly once the version is selected, not the version itself as a "check location."In the work centers(B) provides capacity and scheduling data, but the system does not check master data selection settings there—it uses the routing to reference work centers. This aligns with SAP’s production planning master data integration.

In SAP S/4HANA, the Kanban process links supply and demand sources via thecontrol cycle(transaction PKMC). Required information includes:

Replenishment strategy(C): In the control cycle (PKMC, field: Replenishment Strategy), you define how replenishment occurs (e.g., "0001" for in-house production, "0003" for external procurement, "0002" for stock transfer). This strategy specifies the supply source (e.g., production, vendor) and how it meets demand at the Kanban bin.

Production supply area(D): The PSA (defined in Customizing, transaction PK05, and assigned in PKMC) represents the demand source—where the material is consumed (e.g., a specific production line). It connects the Kanban bin to the supply source (e.g., storage location or work center).

Routing(A) (CA21) details operations for production but isn’t directly maintained in the control cycle—it’s referenced via the production version.Work Center(B) (CR02) is linked indirectly via the PSA or production version, not a direct control cycle field. This is per SAP’s Kanban configuration.

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 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.