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

Explanation:

A. The deletion flag must NOT be set for the bill of material (BOM) or the routing.
A production version is only a reference to other master data. If the underlying BOM or Routing has been marked for deletion (either at the header or item level), the production version becomes "invalid." The system performs a consistency check to ensure the linked objects are active and available for production.

B. The lot size range must be within the lot size range of the assigned routing.
Production versions have defined "Minimum" and "Maximum" lot sizes. To be consistent, these must be a subset of (or equal to) the lot size range defined in the Routing header. If the Production Version allows a lot size of 1,000 but the Routing is only valid up to 500, the system cannot verify the processing times for the remaining 500 units, leading to an inconsistency. +1

C. The assigned routing and bill of material (BOM) must be valid in the entire validity period.
A production version has a "Valid From" and "Valid To" date. For the version to be usable, both the BOM and the Routing must exist and be valid for that entire duration. If a Routing expires on December 31st but the Production Version is set to expire on January 31st, the version will fail the consistency check for that final month. +1

Why the Other Options are Incorrect

D. The assigned routing must be a rate routing:
This is incorrect. While Rate Routings are common in Repetitive Manufacturing (REM), a Production Version can also link to a Standard Routing (for Discrete Manufacturing) or a Master Recipe (for Process Manufacturing).

E. The assigned routing must NOT have alternative sequences:
This is false. A routing can absolutely have alternative sequences (parallel or branch). The Production Version simply points to the Routing Header; it does not restrict the internal structure of the routing itself.

References
SAP Learning Hub: Course S4210 (Basic Processes in SAP S/4HANA Production Planning).
SAP Help Portal: "Production Version" – Prerequisites and Consistency Check.
S/4HANA Simplification List: Note that Production Versions are now mandatory for all sources of supply in S/4HANA.

Explanation:

A. Queue (Option A):
The Queue Time is the time an order sits at a work center waiting to be processed. It is considered a "buffer" time. In the configuration of a Reduction Strategy (Transaction OPU5 or OPU3), you can specify a percentage reduction for the normal queue time. This is often the first element the system reduces because it does not affect the actual machine "touch time."

C. Move Time (Option C):
Move Time is the time required to transport a material from one work center to the next. Like Queue time, this is an "interoperation" time. The reduction strategy can reduce this to the "Minimum Move Time" defined in the routing or apply a percentage reduction to speed up the transition between operations. +2

Why the Other Options are Incorrect

B. Teardown time & D. Setup Time:
These are Execution Times (also known as Operation Segments). While they are part of the operation, the standard Reduction Strategy focuses on buffers (Queue/Move/Wait). Reducing Setup or Teardown would imply changing the actual physical requirement of the machine or labor, which is usually not handled by a simple scheduling reduction. To reduce these, you would typically use Splitting or Overlapping, which are different mechanisms than the Reduction Strategy levels.

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

Explanation:

B. Planning strategy
The Planning Strategy (defined in the Material Master, MRP 3 view) is the "master switch" for how a material is produced and sold. It determines whether a material follows Make-to-Stock (MTS), Make-to-Order (MTO), or Planning with Assembly. The strategy contains the logic for how (or if) consumption occurs. For example, Strategy 40 (Planning with Final Assembly) allows sales orders to consume PIRs, whereas Strategy 10 (Make-to-Stock) does not.

D. Requirements type
The Planning Strategy points to a specific Requirements Type (e.g., VSF for planning, KSV for sales orders). It is the Requirements Type that carries the technical configuration (controlled via Transaction OVZH) that tells the system: "This specific demand is allowed to consume independent requirements." When a sales order is created, its requirements type is compared against the PIR's requirements type to see if they are compatible for consumption.

Why the Other Options are Incorrect

A. Order type:
The Order Type (such as PP01 for production orders) determines how an order is processed, costed, and settled. While it identifies a "requirement," it does not dictate the consumption logic against the forecast; that logic is purely handled within Demand Management settings.

C. Requirements profile:
This is a common distractor. While profiles exist in various SAP modules (like specialized ATP profiles), the actual mechanism that links a Sales Order to a PIR is the combination of Strategy and Requirement Type, not a "Requirements Profile."

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

Explanation:

A. In the Bill of Material (BOM)
The system checks the BOM header and item data to ensure validity. Specifically, it looks at the BOM Status (to see if it is active for production) and the Selection Power settings. If multiple BOMs exist for a material, the selection parameters in the BOM (such as "Selection ID") determine which one is prioritized during order creation. +1

D. In the Routing
Similar to the BOM, the Routing contains selection criteria. The system checks the Routing Status (e.g., "Released for Order") and the Usage (e.g., "Production"). If the routing is not released or is intended only for "Plant Maintenance" or "Testing," the system will not select it for a production order.

E. In the Production Version
In SAP S/4HANA, the Production Version is mandatory. It is the primary "anchor" that links a specific BOM and Routing together. During the creation of planned or production orders, the system first looks for a valid Production Version. If one exists that matches the lot size and date, the system automatically pulls the associated BOM and Routing defined within that version.

Why the Other Options are Incorrect

B. In the Work Centers:
While work centers are used within the routing to calculate capacity and costs, they do not dictate the "Selection Settings" for which master data (BOM/Routing) the order should use. They are recipients of the data, not the selectors of it.

C. In the MRP Controller:
The MRP Controller is a person or group responsible for the material. While they can influence planning parameters in the Material Master, the system does not look "into" the MRP controller settings to decide which BOM or Routing to select during the technical creation of an order.

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

Explanation:

B. To simplify the structure of bills of material
Phantom assemblies allow you to group related components into a single sub-assembly without creating a warehouse requirement. This prevents the "over-inflation" of a finished product's BOM by nesting related items. Instead of seeing 50 individual screws and brackets on the top-level BOM, you see one "Fastening Kit" phantom.

D. To make the assignment of components easier
When assigning components to operations in a Routing, it is much faster to assign one phantom assembly than to manually assign dozens of individual parts. During the production order creation, the system "explodes" the phantom, and all its child components are automatically assigned to the same operation where the phantom was placed.

E. To reduce the number of changes required in bills of material
If a specific sub-group of components is used in 100 different finished products, and one of those components changes, you only have to update the one phantom BOM. Without the phantom, you would have to manually update 100 different finished product BOMs. This significantly reduces the administrative overhead and the risk of data entry errors.

Why the Other Options are Incorrect

A. To increase the number of planning levels:
This is actually the opposite of what phantoms do. Phantoms are used to flatten the planning and inventory levels. Because the phantom itself is never produced as a stocked item, it does not create a separate production level in terms of warehouse movement or logistics.

C. To reduce the number of material masters:
To use a phantom assembly, you must create a Material Master for the phantom itself (typically with a special Special Procurement Key "50"). Therefore, using phantoms actually increases the total number of Material Masters in the system.

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

Explanation:

A. Add the agreement to the source list and mark it for MRP relevance.
To automate procurement through a scheduling agreement, the system must know which agreement to use. In the Source List (Transaction ME01), you must enter the scheduling agreement number and item. Crucially, the "MRP" column must be set to "2" (Record relevant to MRP, scheduling agreement schedules are created automatically). This links the material’s requirement to that specific vendor agreement during the planning run.

D. Set the creation indicator for delivery schedule lines on the initial screen of the MRP run.
Even if your master data is perfect, the MRP run itself must be told to generate schedule lines instead of standard purchase requisitions. On the initial screen of the MRP run (e.g., MD01 or MDBT), the field "Schedule Lines" must be set to either "3" (Schedule lines) or "2" (Schedule lines in opening period). If this is left as "1" (Purchase requisitions), the system will ignore the scheduling agreement and simply create requisitions.

Why the Other Options are Incorrect

B. Set the creation indicator for purchase requisition:
Setting this indicator would result in the creation of Purchase Requisitions (Banfs), which would then require manual or further automated processing to become schedule lines. It does not fulfill the requirement of creating schedule lines directly.

C. Add the agreement to the quota arrangement:
While a Quota Arrangement (MEQ1) can split requirements among multiple vendors, it is not the primary mechanism for generating schedule lines in Classic MRP. The Source List is the mandatory prerequisite for determining the specific "source of supply" for scheduling agreements.

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

Explanation:

B. Assign the alert profile to the overall profile.
The Overall Profile is the highest level of configuration for the Planning Board or the Alert Monitor. To ensure that the system knows which specific alerts to look for (e.g., "Order Late" or "Quantity Shortage"), you must link a specific Alert Profile to that Overall Profile. This creates a tailored environment for the planner.

C. Create an object selection variant for production-planning-related alerts.
For the Alert Monitor to work, it needs to know which objects it should monitor (e.g., specific Products, Resources, or Production Groups). You define this through an Object Selection Variant. This variant filters the data so the planner only sees alerts for the specific production area they are responsible for, rather than every alert in the entire system.

Why the Other Options are Incorrect

A. Create an object selection variant for priority-category-related alerts:
This is a distractor. Object selection is based on master data (Products, Locations, Resources), not on the priority or category of the alerts themselves. The priority/category of an alert is defined within the Alert Profile, not the Selection Variant.

D. Assign the overall profile to the authorization profile:
In SAP, Overall Profiles are typically assigned to User Profiles (via User Parameters) or used directly in transactions. They are not assigned to "Authorization Profiles" (which are security/basis objects managed via transaction PFCG).

References
SAP Learning Hub: Course S4215 (Advanced Planning in SAP S/4HANA).
SAP Help Portal: "Alert Monitor Profile" under Advanced Planning and Optimization.