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

In SAP S/4HANA Cloud Private Edition, theKanban processmanages material replenishment using control cycles (transaction PKMC). Supply sources are configured as follows:

Use run schedule quantities for in-house production(A): For in-house production, the Kanban control cycle (PKMC) can specify a production supply area and a production version (MRP 4 view). When a Kanban is set to "Empty," the system generatesrun schedule quantities(planned orders in repetitive manufacturing, confirmed via MFBF), replenishing stock from the production line.

Use stock transfer reservations for stock transfer(B): For stock transfer between storage locations, the control cycle defines a replenishment strategy (e.g., "0002" - Stock Transfer). When triggered, astock transfer reservation(visible in MB23) is created to move stock from a source storage location to the Kanban bin, managed via goods movement (e.g., MIGO).

Use purchase orders for external procurement(C): For external procurement, the control cycle links to a scheduling agreement or contract (ME31K). Setting a Kanban to "Empty" generates apurchase orderor schedule line (visible in ME38), triggering replenishment from the vendor.

Use quotations(D) isn’t a standard Kanban supply source—quotations (ME47) are pre-procurement documents, not direct replenishment triggers.Use purchasing costs for automated source prioritization(E) isn’t a Kanban feature—source selection is manual or via control cycle settings, not cost-based automation. This is per SAP’s Kanban setup documentation.

In SAP S/4HANA Cloud Private Edition, Advanced Planning (PP/DS) integrates with core master data, and the "Advanced Planning" flag activates PP/DS-specific planning. This flag can be set in:

Work center(A): In the work center (transaction CR02, Basic Data tab, field: Advanced Planning), checking this flag (or integrating with a resource in APO/PP/DS) enables detailed scheduling and capacity planning in PP/DS. It designates the work center as a resource for finite scheduling (e.g., in /SAPAPO/RES01).

Material(D): In the material master (MM02, Advanced Planning tab, field: PP/DS Planning), activating this flag makes the material relevant for PP/DS planning. It enables features like detailed scheduling, heuristics, and integration with APO or embedded PP/DS functionalities.

Plant(B) doesn’t have an Advanced Planning flag—PP/DS activation is at the system or object level (e.g., via CIF integration model), not plant-specific.Production version(C) (MRP 4 view) links BOMs and routings but lacks a specific PP/DS flag—its relevance comes from the material and work center settings. This is per SAP’s PP/DS master data setup.

In SAP S/4HANA, MRP usesbackward schedulingto calculate the basic dates for dependent requirements (e.g., components needed for production). Backward scheduling starts from the requirement date of the finished product and works backward to determine when components must be available. The key time elements considered are:

Planned delivery time(A): This is maintained in the material master (MRP 2 view, field: Planned Delivery Time) for externally procured materials. It represents the time required by the vendor to deliver the material, and MRP uses it to calculate the start date for procurement to ensure the component is available when needed.

In-house production time(D): For materials produced in-house, this is maintained in the material master (MRP 2 view, field: In-house Production Time). It defines the total time required to produce the material, independent of quantity, and MRP uses it to determine the start date of production for dependent requirements.

Total replenishment lead time(B) (MRP 2 view, field: Total Replenishment Lead Time) is an optional field that includes all procurement and production times but is typically used as a fallback or for special cases, not as a standard element in backward scheduling for components.Operation duration(C) is specific to routing data (e.g., setup, processing times) and is considered in detailed scheduling (e.g., production order scheduling), not MRP’s basic date calculation, which relies on material master data. This aligns with SAP’s MRP scheduling logic as per official documentation.

Material Requirements Planning (MRP) in SAP S/4HANA calculates net requirements to determine material shortages or surpluses by comparing the available stock and scheduled receipts against requirements. During this calculation, MRP considers existingproduction orders(A) because they represent firm commitments to produce materials, and their quantities directly influence the availability of components and finished goods. Similarly,planned orders (firmed)(B) are included as they are confirmed planning proposals that have been manually or automatically fixed, ensuring they are treated as reliable supply elements in the net requirement calculation.

Planned orders (unfirmed)(C) are not considered firm receipts because they are still tentative and subject to change during subsequent MRP runs, so they are excluded from the net calculation unless firmed.ATP (Available-to-Promise) quantities(D) are used in availability checks for sales orders, not directly in MRP’s net requirement calculation, which focuses on stock and scheduled receipts rather than promise-based quantities. This aligns with SAP’s MRP logic as outlined in the SAP S/4HANA Production Planning documentation, emphasizing firm supply elements.

In SAP S/4HANA, when multiple valid production versions (maintained in the material master, MRP 4 view, or transaction MM02) exist during production order creation, the system follows a predefined selection logic:

Alphanumeric or quota arrangement(A): By default, the system selects the production version with the lowest alphanumeric identifier (e.g., "0001" before "0002") if no other criteria are specified. Alternatively, if aquota arrangement(transaction MEQ1) is maintained and marked as MRP-relevant, the system uses the quota percentages to distribute production across versions, overriding the alphanumeric logic. This is configured in Customizing (Production > Master Data > Production Versions).

Option B (Planned order or material number) is incorrect—planned orders inherit versions from MRP, and material number is irrelevant to version selection.

Option C (Validity period or sales order) is partially true—validity period ensures only active versions are considered—but sales orders do not directly influence version selection unless linked via a specific requirement (e.g., variant configuration), which is not standard.

Option D (Lot size or material cost) influences version selection only if defined in the production version’s lot size range, but it’s not the primary method unless customized.

This behavior is documented in SAP’s production order creation process.

Before creating a bill of material (BOM) in SAP S/4HANA (transaction CS01), certain prerequisites must be clarified:

Is the material type allowed in the BOM?(B): The material type (material master, MM01) determines whether a material can be used in a BOM. For example, "FERT" (finished goods) or "HALB" (semi-finished) are typical header materials for production BOMs, while "ROH" (raw materials) are components. This is configured in Customizing (Logistics - General > Material Master > Define Attributes of Material Types), and the system checks this during BOM creation.

What status does the BOM have?(D): The BOM status (CS01, header data, field: BOM Status) must be defined—e.g., "1" (Active) for production use or "2" (Inactive) for testing. This status controls whether the BOM can be used in MRP or production orders, and it must be decided upfront to ensure correct application.

In which storage location is the BOM required?(A) is irrelevant—BOMs are plant-specific, not storage-location-specific (storage location is relevant for stock, not BOM structure).Which base unit of measure does the material have?(C) is important for component quantities but is a material master attribute (Basic Data view) checked during entry, not a pre-creation question. This is per SAP’s BOM creation process.

In an SAP S/4HANA Cloud Greenfield project,clean corefocuses on a standardized, extensible system with high-quality data. Key aspects for data quality include:

Efficiency(A): Clean core principles prioritize efficient processes and data structures, minimizing customizations that could degrade performance or complicate upgrades. Efficient data quality ensures streamlined operations (e.g., fast MRP runs) and leverages standard SAP functionalities effectively.

Stability(D): Maintaining a stable core with consistent, reliable data (e.g., master data integrity in MM03) prevents disruptions during updates or extensions. Stability ensures the system remains robust and predictable, a cornerstone of clean core in a Greenfield implementation.

Accuracy(B) is critical for data quality in general (e.g., correct BOM quantities), but clean core emphasizes systemic qualities over content accuracy, which is assumed.Timeliness(C) matters for operational data (e.g., stock updates), but it’s less tied to clean core’s structural focus. This is per SAP’s clean core guidelines.

In SAP S/4HANA, changing the material type (transaction MMAM) is restricted if stocks, reservations, or purchasing documents exist, but it’s allowed under specific conditions:

The quantity and value updates are the same(A): The old and new material types must have identical quantity and value update settings in their valuation areas (configured in OMS2, Material Type Customizing). For example, both must update quantity and value (e.g., "FERT" to "HALB"), or neither (e.g., "NLAG" to "DIEN"). If these differ, the change is blocked due to inconsistencies in stock valuation.

The same base unit of measure is used(C): The base unit (material master, Basic Data 1 view) must remain unchanged between material types. Changing it (e.g., from "PC" to "KG") would invalidate existing stock or document quantities, so the system requires consistency to allow the type change.

The same batch management level(B) (e.g., plant or material level, configured in OMCT) is not a strict requirement—batch settings can differ as long as other conditions are met.The same account category(D) (e.g., General Ledger account determination) influences posting but isn’t a prerequisite—account assignment can be adjusted post-change. This is per SAP’s material type change rules.

In SAP S/4HANA, dispatching operations (e.g., in CM21 or PP/DS Planning Board) assigns them to work centers. Multiple commitments on the same date indicate overlapping schedules, caused by:

The Finite Scheduling indicator is NOT set in the strategy profile(A): In PP/DS (strategy profile, /SAPAPO/CDPSC11) or capacity planning (OPU5), if finite scheduling isn’t active (e.g., work center CR02, Capacity tab, "Relevant to Finite Scheduling" unchecked), the system schedules operations infinitely, ignoring capacity limits and allowing overlaps on the same date.

The work center has several individual capacities(B): If the work center (CR02, Capacity tab) has multiple individual capacities (e.g., 3 machines, field: No. of Individual Capacities), operations can be scheduled in parallel on the same date, each assigned to a separate capacity, resulting in multiple commitments.

Alternative work centers fully occupied(C) might force scheduling onto one center but doesn’t inherently cause overlaps—it’s a capacity issue, not a scheduling logic flaw.Change Planning Direction indicator(D) (e.g., Forward/Backward in strategy profile) affects sequence, not overlapping commitments. This is per SAP’s scheduling behavior.

In SAP S/4HANA Cloud Private Edition, thetabular planning tablefor capacity planning (transaction CM22) offers chart-based views to analyze capacity:

Capacity requirements chart(B): This chart (accessible in CM22, graphical view) displays the capacity requirements (e.g., in hours) for operations across work centers over time, showing demand against available capacity to identify overloads or gaps.

Work center capacities chart(D): This chart shows the available capacity of work centers (defined in CR02, Capacity tab) over a time period, allowing planners to compare it with requirements and adjust dispatching (e.g., visible in the capacity overview tab).

Order (pool) chart(A) represents undispatched orders in the pool (e.g., in CM21), not a specific tabular chart type in CM22, which focuses on dispatched operations.Orders (dispatched) chart(C) isn’t a distinct chart—dispatched orders are part of the requirements chart. This is per SAP’s capacity planning table documentation.

In SAP S/4HANA, a production order (transaction CO01) requires a valid production version (material master, MRP 4 view). If none can be selected, possible reasons include:

The order lot size is NOT within the validity range of a production version(A): Each production version specifies a lot size range (e.g., 100-1000 units). If the order quantity (entered in CO01) falls outside this range, the version is invalid, and the system cannot select it.

All production versions for the material are locked(C): If production versions are locked (MRP 4 view, field: Lock indicator), they are excluded from planning and order creation, even if otherwise valid, preventing selection.

NO production lines assigned(B) is irrelevant—production versions link BOMs and routings, not production lines (a repetitive manufacturing concept).NO BOMs assigned(D) would invalidate a version, but the system checks BOM validity within the version, and this is typically caught during version creation (C223), not order creation. This is per SAP’s production version validation rules.

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.

Planning withplanned independent requirements(PIRs) in SAP S/4HANA (entered via MD61) for finished materials offers benefits in a make-to-stock or forecast-driven environment:

Reduced delivery times(A): By planning PIRs in advance (e.g., strategy 10 or 40), production can start before sales orders arrive, ensuring finished goods are available in stock. This shortens the time between order receipt and delivery, improving customer service levels.

Reduced times for final assembly(B): In strategies like 40 (Planning with Final Assembly), PIRs trigger procurement and production of components early. When sales orders arrive, only final assembly is needed, reducing the overall lead time for completion.

Option to forecast planning for production resources(C) is a byproduct of capacity planning (e.g., CM01), not a direct benefit of PIRs—PIRs focus on material demand.Option to use make-to-order production(D) contradicts PIRs, which are for make-to-stock or forecast-based planning (e.g., strategies 10, 40), not MTO (e.g., strategy 20). This is per SAP’s demand management benefits.

In SAP S/4HANA, MRP can be configured to exclude certain materials from planning runs to optimize processing or reflect specific business needs. One method is to use aspecific material status(B), maintained in the material master (e.g., under the MRP view). A status such as "Blockedfor Procurement/Production" (configured in Customizing under Logistics - General > Material Master > Settings for Key Fields > Define Material Statuses) prevents the material from being planned in MRP, effectively excluding it from the run.

Another method is to assign aspecific MRP type(D), such as "ND" (No Planning), in the material master (MRP 1 view). This MRP type instructs the system not to generate requirements or planned orders for the material, excluding it from MRP processing.Using a specific MRP list(A) is not a valid exclusion method, as the MRP list is an output of the MRP run, not a control mechanism. Similarly,using a specific material group(C) does not inherently exclude materials from MRP, as material groups are for classification and reporting, not MRP control. These options align with SAP’s standard MRP configuration settings.

In SAP S/4HANA Cloud Private Edition, tracking materials with varying characteristics across manufacturing processes and logistics requires:

Batch management(D): Batch management (activated in material master, MM01, General Plant Data/Storage view, field: Batch Management) assigns unique batch numbers to materials (e.g., via MSC1N). It tracks characteristics (e.g., viscosity, color) via classification (CL02, linked in MSC2N), ensuring this information is available in all logistics areas—production (e.g., CO11N goods issue), inventory (MMBE), and sales (VA01 batch determination). This is ideal for materials like chemicals with process-specific traits.

Process order management(A) (COR1) executes production but relies on batch management for characteristic tracking—it’s not the tracking tool itself.Engineering change management(B) (CC01) manages design changes, not runtime characteristics.Quality management(C) (e.g., QA01) inspects batches but doesn’t track characteristics across logistics—batch management underpins it. This is per SAP’s batch management capabilities.

Cost Object Controlling (COC) in SAP S/4HANA for production orders can be configured as order-related (each order is a cost object) or product-related (costs are collected at the product level via a product cost collector). Key considerations include:

In product-related COC, all costs are debited and credited to a product cost collector(B): In this approach (configured via transaction KKF6N or Customizing: Production > Product Cost Controlling > Product Cost Collectors), all production costs (material, labor, overhead) for a material are aggregated on a single cost collector, regardless of individual orders. This simplifies cost tracking for repetitive manufacturing scenarios.

Order-related COC is beneficial in a flexible production environment(D): In flexible or make-to-order production, where each order has unique specifications or costs (e.g., varying BOMs or routings), order-related COC (configured in the order type, OPL8) assigns costs to individual production orders, providing detailed visibility and control.

Product-related COC for co-products(A) is incorrect—co-products typically use order-related COC with a settlement rule to apportion costs, not product-related collectors.In order-related COC, individual production orders do NOT have cost segments(C) is false—each order has its own cost segments (e.g., material, activity) for detailed analysis. This aligns with SAP’s cost controlling documentation.

In SAP S/4HANA process manufacturing (using process orders, transaction COR1), managing production flow for liquid chemicals in physically connected tanks requires:

Resource selection(B): In the master recipe (C201) or process order (COR2), you can define resource selection conditions (e.g., via classification in the resource, CRC1, Basic Data tab). This ensures only suitable tanks (e.g., based on attributes like material compatibility or capacity) are selected for operations, restricting production to physically appropriate resources.

Resource network(D): A resource network (Customizing, Production > Process Order > Master Data > Define Resource Networks) defines the physical connections between resources (e.g., tanks, pipes) in a plant. It specifies valid flow paths (e.g., Tank A to Tank B), ensuring process orders (COR1) schedule operations only on connected tanks, enforced during scheduling or dispatching.

Resource hierarchy(A) (CR21) aggregates capacities for planning, not physical connections.Resource matrix(C) isn’t a standard SAP term—it might refer to custom setups, but it’s not a defined feature for tank connectivity. This is per SAP’s process manufacturing controls.

Engineering Change Management (ECM) in SAP S/4HANA (transaction CC01/CC02) manages changes to objects like BOMs, routings, and materials with a structured process:

To save multiple changes for an object(C): ECM allows multiple changes (e.g., to a BOM’s components) to be grouped under one change number (field: Change Number in CS01). These changes are saved and applied together on a specified date (Valid From), ensuring coordinated updates across objects.

To monitor document object changes(D): ECM tracks changes to objects (e.g., materials, BOMs) linked to a change number, providing an audit trail (transaction CC03, History tab). This monitors who changed what and when, supporting compliance and traceability.

To monitor document table changes(A) is vague—“document” likely means BOM or routing, but ECM focuses on object changes, not table-level monitoring (e.g., database logs).To enable integration into a sales order(B) is incorrect—ECM integrates with production or procurement, not directly with sales orders (VA01). This is per SAP’s ECM functionality.

In SAP S/4HANA, the item category in a BOM (transaction CS01/CS02, field: Item Category) classifies components and determines their handling in production and procurement. Standard item categories include:

Variable-size item(A): Item category "R" (Variable-Size Item) is used for components with dimensions (e.g., sheets, pipes) where quantity is calculated based on size data (entered in the Variable-Size Item Data tab). It’s common in manufacturing for materials cut or sized during production.

Preliminary item(C): Item category "V" (Preliminary Item) is a placeholder for components not yet fully specified (e.g., during design phase). It allows BOM creation to proceed, with details added later, and is valid for planning purposes.

Work item(B) is not a standard BOM item category—"L" (Stock Item) or "N" (Non-Stock Item) might apply to work-related components, but "Work Item" isn’t a defined term.WBS item(D) (Work Breakdown Structure, category "W") relates to Project Systems (PS) BOMs, not standard production BOMs in PP, requiring PS integration. This is per SAP’s BOM item category definitions.

Dependent requirements in SAP S/4HANA represent the demand for components or assemblies triggered by the production of higher-level materials. These arecreated on assembly level during the planning run(B) in classic MRP when the system explodes the bill of material (BOM) of afinished product or assembly, calculating requirements based on independent requirements (e.g., sales orders or planned independent requirements) and the BOM structure. This occurs in transactions like MD01/MD02, where MRP generates dependent requirements for all relevant levels.

InAdvanced Planning (PP/DS), dependent requirements arecreated with exact times(C) due to the detailed scheduling capabilities of PP/DS. Unlike classic MRP, which uses daily or weekly buckets, PP/DS schedules requirements with precise timestamps, aligning them with production and procurement timelines. Option A is incorrect because dependent requirements are derived from independent requirements, not created simultaneously. Option D is false, as dependent requirements apply to any BOM structure, not just multilevel ones.

SAP S/4HANA offers automation options to streamline production order processing:

You can use trigger points to automatically create rework orders via confirmations(A): Trigger points (configured in routing via CA02, Extras > Trigger Points) are events linked to operations. For example, a trigger point can be set to create a rework order (order type defined in Customizing) automatically when a confirmation (e.g., CO11N) indicates a quality issue, enhancing process efficiency.

You can use mass processing to set production orders to technically complete(B): Transaction COHV (Mass Processing of Production Orders) allows users to select multiple orders and execute the "Technically Complete" function (TECO), automating status updates without manual intervention per order.

The production scheduling profile(C) (Customizing: Production > Shop Floor Control > Master Data > Define Production Scheduling Profile) controls scheduling and confirmation settings but cannot automatically set orders to "Technically Complete"—this requires manual or mass action.Mass processing to read PP master data(D) is not a standard function—COHV updates order data, not reads master data for automation. This is per SAP’s production automation features.

Creating a material master (referred to here as a "product master") in SAP S/4HANA Cloud Private Edition (transaction MM01) requires mandatory fields to establish the material’s identity and usage:

Base unit of measure(A): This field (Basic Data 1 view, field: Base Unit of Measure) is mandatory and defines the primary unit (e.g., "PC," "KG") for stockkeeping, procurement, and production. Without it, the system cannot process quantities, making it a required input during creation.

Industry sector(B): Selected on the initial MM01 screen (field: Industry Sector), this determines the material’s business context (e.g., "M" for Mechanical Engineering) and influences the available views and field layouts. It’s mandatory to proceed with material creation.

Selection screen for views(C) is a step in MM01 where you choose views (e.g., MRP, Purchasing), but it’s not "information" entered—it’s a navigation choice.Product type(D) is likely a misnomer for "Material Type" (e.g., FERT, ROH), which is required on the initial screen, but the question’s phrasing aligns with SAP’s term "Material Type," not "Product Type." A and B are the clearest matches per SAP’s material creation process.

In SAP S/4HANA PP/DS, theInsert Operationscheduling mode (configured in the strategy profile, e.g., /SAPAPO/CDPSC11) is a finite scheduling option that inserts a new operation into an existing schedule while respecting capacity constraints. Effects include:

Scheduling of an operation takes place as close as possible to the desired date(A): The system schedules the operation (e.g., in /SAPAPO/PPDS_DISP) at the earliest feasible time slot near the desired date (specified in the order or planning parameters), considering finite capacity and resource availability.

Neighboring operations can be moved in both directions in order to create a slot(C): To accommodate the new operation, the system shifts existing operations forward or backward (within tolerances defined in the strategy profile), ensuring a feasible slot without overloading the resource.

Sequencing on multi-activity resources(B) isn’t automatically updated—this requires a separate heuristic (e.g., /SAPAPO/HEUR_SEQUENCE).Changes in the complete collective order(D) don’t occur automatically—collective orders require explicit rescheduling of linked orders, not an inherent feature of Insert Operation. This is per SAP’s PP/DS scheduling documentation.

In SAP S/4HANA,lead time schedulingfor a production order (e.g., in CO01, Scheduling Type: Lead Time Scheduling) calculates detailed operation dates using routing data and buffers. Relevant time elements include:

Float after production(C): Defined in the material master (MRP 2 view, field: Float After Production) or scheduling margin key (Customizing, OPPT), this buffer time after the last operation ensures flexibility before the order’s end date (e.g., for quality checks), extending the total lead time.

Setup time(D): Maintained in the routing (CA01, Standard Values, field: Setup Time), this is the time to prepare the work center for an operation. It’s included in the operation duration (calculated via work center formulas, CR02), directly impacting the lead time schedule.

Opening period(A) (MRP 2 view) is a buffer before production starts, relevant for order release, not lead time scheduling within the order.Total replenishment lead time(B) (MRP 2 view) is a high-level estimate for MRP, not detailed operation scheduling. This is per SAP’s lead time scheduling rules.