Learn, Practice, and Improve with SAP C_TS422_2022 Practice Test Questions

Explanation:

In SAP S/4HANA, Dependent Requirements represent the demand for components derived from the production of a higher-level assembly.

Precision in Advanced Planning (Option A):
While classic MRP typically plans in daily buckets, Advanced Planning (PP/DS) uses continuous scheduling. Because it considers finite capacity and exact machine speeds, it calculates the requirement down to the hour and second. This ensures that the component is staged exactly when the operation starts.

The MRP Planning Run (Option C):
Dependent requirements are the direct result of a BOM Explosion during the planning run. When MRP processes a finished good, it identifies the components in the BOM and creates these requirements at the assembly or raw material level to trigger procurement or production.

Why the Other Options are Incorrect

Option B:
This is a timing error. Creating a Planned Independent Requirement (PIR) for a finished product only creates the Demand for the top level. The dependent requirements for components do not exist until the MRP Live or Classic MRP run actually "explodes" that demand down the structure.

Option D:
The word "only" makes this false. Dependent requirements are generated for any BOM, whether it has ten levels (multilevel) or just one level (single-level).

References

SAP Learning Hub: Course S4210 (Basic Processes in SAP S/4HANA Production Planning).

Explanation:

Collective orders in SAP S/4HANA Production Planning allow you to group multiple production orders that belong to different levels of a multilevel bill of material (BOM). For example, if a finished product requires a subassembly, which in turn requires raw materials, you can create separate production orders for each level and link them into one collective order. This provides a consolidated view of the entire production process, simplifies monitoring, and enables integrated confirmations and goods movements across all levels.

❌ Why Other Options Are Incorrect:

B. To combine order management of co-products and by-products with the main product
Incorrect. Co-products and by-products are managed using process orders with a special co-product planning strategy, not collective orders. Collective orders link dependent orders in multilevel production, not different product types.

C. To post production costs on a cost collector instead of the production order
Incorrect. This describes a run schedule cost collector, which is used in repetitive manufacturing to collect costs periodically. Collective orders still post costs to individual production orders, not a separate cost collector.

D. To post any component withdrawal as single backflush with order confirmation
Incorrect. This describes backflushing, where components are automatically issued during confirmation. Backflushing can be used in production orders, but it is not the purpose or function of collective orders.

📚 Reference:
SAP Help Portal: Collective Orders
SAP S/4HANA Production Planning Documentation
Transaction Codes: CO01 (Create Production Order), CO02 (Change Production Order) - Collective Order field available

Explanation:

The same base unit of measure is used (Option B):
The Base Unit of Measure (UoM) is the "foundation" of the material master. If you have existing stock or open purchase orders, the system cannot recalculate those quantities into a new base UoM during a type change. Therefore, the new material type must support the exact same base UoM as the old one to ensure consistency in inventory management.

The quantity and value updates are the same (Option C):
Material types define whether a material is managed by quantity, by value, or both (defined in transaction OMS2). If you change a material from a "Stocked" type (like RAW) to a "Non-stock" type (like NLAG) while stock exists, the system would lose the ability to value that inventory. To change the type with existing stock/documents, the "Quantity updating" and "Value updating" flags for the relevant Plant must be identical in both the old and new material types.

Why the Other Options are Incorrect

Option A (Batch Management Level):
While batch management is important, the "level" (Client, Material, or Plant level) is a system-wide setting in and is not a strict blocker for changing a material type in the same way UoM or Valuation is.

Option D (Account Category):
This is a distractor. The Account Category Reference determines which Valuation Classes are allowed. While it influences accounting, the system allows you to change the material type even if the category differs, provided you re-assign a valid Valuation Class that fits the new type's constraints.

References
SAP Learning Hub: Course S4500 (Business Processes in SAP S/4HANA Sourcing and Procurement) and S4210.

Explanation:

In SAP, co-products and by-products are both outputs of a production process, but they are represented differently in the Bill of Material (BOM). Co-products are identified with a special BOM item category (usually item category L). They are primary products planned and manufactured together with the main product. By-products, however, are typically assigned a negative quantity in the BOM with standard item categories and are not considered primary products for planning purposes.

❌ Why Other Options Are Incorrect:

B. Only co-products can be manufactured in isolation from the main product
Incorrect. Both co-products and by-products are produced simultaneously with the main product in a joint production process. Neither is typically manufactured in isolation.

C. Only co-products have a zero inventory valuation
Incorrect. By-products often have zero inventory valuation or are valued at a lower price (scrap value), while co-products have their own valuation and material master records with standard prices.

D. Only co-products appear in the process or production order settlement rule
Incorrect. Both co-products and by-products appear in the settlement rule. Co-products receive credit from production variances, while by-products reduce production costs by crediting the order with their value.

Reference:
SAP Help Portal: Co-Products and By-Products
SAP S/4HANA Production Planning - Joint Production Configuration: Define item categories for BOMs (transaction OSP4)

Explanation:

A. The Finite Scheduling indicator is NOT set in the strategy profile.
The Strategy Profile (defined in Customizing) controls how the system behaves during dispatching. If "Finite Scheduling" is not checked, the system performs "Infinite Planning." It will place as many operations as requested on the same date/time without checking if the work center has the capacity to handle them. Essentially, it assumes the work center has "limitless" availability.

B. The work center has several individual capacities.
A work center is not always a single machine; it can represent a group of five identical machines (individual capacities). If a work center has, for example, 3 individual capacities, the system can legally schedule 3 different operations at the exact same start and end time. Each operation is assigned to one of the individual capacity "slots" within that work center.

Why the Other Options are Incorrect

C. The Change Planning Direction indicator is set:
This indicator only determines if the system searches for free capacity in a forward or backward direction from the desired date. It changes where an operation is placed, but it does not cause multiple operations to overlap on its own.

D. Alternative work centers are fully occupied:
This is a consequence, not a cause. If alternatives are full, the system might try to put the order on the primary work center, but whether it overlaps depends entirely on the Finite Scheduling setting (Option A). If Finite Scheduling were active, the system would simply fail to dispatch the order rather than creating multiple commitments on the same date.

References
SAP Learning Hub: Course S4210 (Basic Processes in SAP S/4HANA Production Planning) – Unit on Capacity Planning.

Explanation:

When a material is created with both in-house production (production lead time defined) and external procurement (information record exists) as possible procurement types, MRP must decide which procurement type to use. In SAP, MRP prioritizes in-house production over external procurement by default. This is determined by the Procurement Type field (in material master MRP1 view) and the Special Procurement field. If both are possible, MRP assumes you will produce the material internally unless manually overridden or configured otherwise.

❌ Why Other Options Are Incorrect:

A. The MRP run assumes external procurement
Incorrect. External procurement is only assumed when the procurement type is set to "F" (External) or when in-house production is not possible (e.g., no BOM or routing exists).

C. The MRP run does NOT consider the material; it has to be planned interactively
Incorrect. MRP will consider the material and plan it automatically based on the procurement type determination logic. Interactive planning is not mandatory.

D. The MRP run plans the material only if a quotation has been maintained
Incorrect. Quotations are relevant for procurement optimization and source determination, but MRP will generate planned orders regardless of quotations if the material is MRP-relevant.

Reference:
SAP Help Portal: Procurement Type Determination in MRP
Material Master MRP1 View: Fields - "Procurement Type" and "Special Procurement"
Transaction Codes: MM01 (create material), MD04 (stock/requirements list)

Explanation:

B. By mass processing
In high-volume environments, checking orders one by one is inefficient. Using Mass Processing (Transaction COHV), you can select a large group of production orders and trigger an availability check for all of them at once. This can also be scheduled as a background job to run periodically (e.g., every night) to ensure the latest stock levels are reflected in the orders.

C. By order release
This is the most common automated trigger. In Customizing (OPJK), you can configure the system so that the moment an order is released, it automatically triggers a "Checking Control." If components are missing, the system can be set to either issue a warning or prevent the release entirely. This ensures that no order reaches the shop floor unless the materials are ready. +1

Why the Other Options are Incorrect

A. By capacity planning:
Capacity planning deals with the availability of Work Centers (Machines/Labor), not the availability of physical materials. While you might perform a capacity check, it does not automatically trigger a material BOM check.

D. By order confirmation:
This is too late in the process. A "Confirmation" (CO11N/CO15) happens when work is already being done or is finished. The material check must happen before production starts (at creation or release) to be effective. At the confirmation stage, you are typically posting actual "Goods Issues," not checking for availability.

References
SAP Learning Hub: Course S4220 (Production Orders in SAP S/4HANA).
SAP Help Portal: "Availability Check for Material Components in Production Orders."
Customizing Path: Production > Shop Floor Control > Operations > Availability Check > Define Control.