Free Practice Questions for SAP C_TS422_2023 Exam

Planning strategy 40 (Planning with Final Assembly) in SAP S/4HANA (material master, MRP 3 view, Strategy Group: 40) uses planned independent requirements (PIRs) to forecast demand, which are then consumed by actual sales orders. The prerequisite for this consumption is:

A sales order is created(D): In strategy 40, PIRs (entered via MD61) are reduced when a sales order (transaction VA01) is created within the consumption period (defined in MRP 3 view, e.g., Consumption Mode and Period). The system matches the sales order quantity and date against PIRs, reducing them accordingly to align production with actual demand.

MRP creates a dependent requirement(A) occurs downstream for components, not as a trigger for PIR consumption.A sales order is delivered(B) is too late—consumption happens at order creation,not delivery (VL01N).MRP creates a planned order(C) is a result of PIRs or sales orders, not a prerequisite for consumption. This is per SAP’s demand management logic for strategy 40.

In SAP S/4HANA Demand Management,planned independent requirements(PIRs) represent forecasted demand for finished products. Their consumption by other requirements (e.g., sales orders) depends on settings in the material master:

Requirements type(C): This is determined by the planning strategy and specifies the type of PIR (e.g., VSF for forecast-based planning). It is maintained in the material master (MRP 3 view) or derived from the planning strategy. The requirements type dictates how PIRs are consumed (e.g., by sales orders) and is visible in demand management (transaction MD61). For example, requirements type "LSF" (from strategy 40) allows consumption by sales orders.

Planning strategy(D): Defined in the material master (MRP 3 view, field: Strategy Group), the planning strategy (e.g., 40 - Planning with Final Assembly) controls whether and how PIRs are consumed. For instance, strategy 10 (Make-to-Stock) does not allow consumption, while strategy 40 reduces PIRs based on incoming sales orders within the consumption period.

Order type(A) relates to production or sales order processing, not PIR consumption logic.Requirements profile(B) is not a standard SAP term in this context and does not directly influence consumption (it may refer to custom settings, but it’s not part of SAP’s standard demand management). This is detailed in SAP’s official Demand Management documentation.

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, when a raw material batch has a quality deviation and has been used in production, you can trace its impact on finished goods using batch management tools:

Use the Batch Information Cockpit(B): The Batch Information Cockpit (transaction BMBC) provides a centralized view of batch data, including where-used information. By entering the raw material batch number, you can trace its usage through production orders (e.g., CO03) to identify all affected finished goods batches in stock (e.g., via the "Batch Usage" tab).

Use the batch where-used list(C): The batch where-used list (transaction MB56 or embedded in MSC2N, "Batch Usage" function) tracks a batch’s consumption across production orders or material movements (e.g., goods issue 261). It shows the hierarchy from the raw material batch to finished goods batches, pinpointing affected stock (e.g., in MMBE).

Batch determination(A) (e.g., in COB1) is for selecting batches during production or sales, not tracing past usage.Batch derivation(D) (Customizing, Logistics - General > Batch Management > Derivation) transfers batch attributes from raw to finished goods but doesn’t identify affected stock retrospectively—it’s a forward process. This is per SAP’s batch traceability features.