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

In SAP S/4HANA Advanced Planning (PP/DS - Production Planning and Detailed Scheduling), infinite planning assumes unlimited capacity availability during the initial planning phase. When the documentation states that "new orders are created through infinite planning," it means that MRP generates planned orders without checking the existing capacity load on work centers. Thus,MRP creates the capacity requirements without considering existing load on the work centers(B). This approach prioritizes material availability and scheduling over capacity constraints, leaving capacity leveling to a subsequent step (e.g., using heuristics or manual adjustments in PP/DS).

Option A is incorrect because infinite planning does not sequence capacity requirements after the last operation; it ignores capacity entirely. Option C is not accurate, as "earliest possible time" implies a finite scheduling logic, which contradicts infinite planning. Option D is also incorrect, as infinite planning does not consider available capacity for assignment. This is consistent with SAP’s PP/DS documentation, where infinite planning is a preliminary step before finite scheduling.

A production version in SAP S/4HANA (material master, MRP 4 view) links a BOM and routing for production. For it to be valid and consistent:

The deletion flag must NOT be set for the bill of material (BOM) or the routing(A): If the BOM (CS02) or routing (CA02) has a deletion flag, it cannot be used in production planning or execution, rendering the production version invalid. This is a basic integrity check in SAP.

The assigned routing and bill of material (BOM) must be valid in the entire validity period(C): The production version’s validity period (e.g., Valid From/To dates) must align with the BOM and routing’s validity. If either expires or is invalid during the version’s timeframe, the system cannot use it (checked in MRP or order creation).

The lot size range must be within the lot size range of the assigned routing(E): The production version’s lot size (MRP 4 view) must fall within the routing’s lot size range (CA02, header data). If the order quantity exceeds this range, the version is inconsistent for planning.

The consistency check(B) (transaction C252) is a manual validation tool, not a requirement for validity—it’s optional.Same validity period(D) is not mandatory; overlapping validity is sufficient, as long as both are valid when needed. This is per SAP’s production version documentation.

In SAP S/4HANA Cloud Private Edition, alternative items in a BOM (transaction CS01/CS02) allow substitution of components based on predefined strategies. These are maintained in the BOM item data (Alternative Item Group and Strategy fields). The available strategies are:

Manual maintenance(C): This strategy (Strategy field: "1" - Manual Maintenance) allows planners to manually select which alternative item to use during production order processing (e.g., in CO02). The system does not automate selection, relying on user intervention based on availability or preference.

100% check(D): This strategy (Strategy field: "2" - 100% Check) ensures that only one alternative item is used per order, with the system checking availability (via ATP) for 100% of the required quantity. If the first item isn’t fully available, it moves to the next in the priority sequence (Priority field).

First in first out (FIFO)(A) is a stock management concept (e.g., in WM or batch determination),not a BOM alternative item strategy.Simultaneous(B) is not a standard strategy—alternative items are sequential or selective, not used simultaneously unless custom-developed. This aligns with SAP’s BOM functionality documentation.

In SAP S/4HANA, theplanning table for repetitive manufacturing(transaction MF50) is a tool for managing production quantities and schedules in a repetitive production environment. Planners can:

Change the assignments of production quantities to production lines(A): In MF50, planners can reassign planned production quantities (e.g., run schedule quantities) from one production line (defined in the production version, MRP 4 view) to another within the same material, adjusting the distribution based on capacity or availability (visible in the "Assignment" view).

Reschedule and deallocate operations(D): Planners can reschedule production quantities to different dates (e.g., drag-and-drop in the graphical view) or deallocate them from a line (e.g., by setting quantities to zero or removing assignments), providing flexibility to adapt to changes in demand or capacity.

Create new production quantities(B) is typically done via demand management (MD61) or MRP, not directly in MF50, which adjusts existing plans.Dispatch operations to work centers(C) applies to discrete manufacturing (e.g., in CM21 or PP/DS), not repetitive manufacturing, where operations are tied to production lines in the planning table. This is per SAP’s repetitive manufacturing 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, the validity of a bill of material (BOM) (transaction CS01/CS02) can be restricted as follows:

By plant(B): BOMs are plant-specific by default (field: Plant in CS01). A BOM created for one plant (e.g., 0001) is not valid in another (e.g., 0002) unless copied or extended (CS07), limiting its applicability to the specified plant.

By period(C): The BOM header (CS02) includes "Valid From" and "Valid To" dates, restricting its use to a specific time range. MRP and production orders only select BOMs valid on the required date, allowing versioning or phase-outs (e.g., engineering changes via ECM).

By material type(A) influences which materials can be included in a BOM (e.g., FERT for finished goods), but it doesn’t limit the BOM’s validity—it’s a material attribute.By material status(D) (material master, Basic Data) can block a material from use, but it affects the material, not the BOM’s validity directly. This aligns with SAP’s BOM management rules.

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

For a make-to-order (MTO) scenario in SAP S/4HANA without forecasting, where components have different procurement behaviors:

Choose planning strategy 20 (Make-to-Order) and select the corresponding Individual/Collective indicator(D): Strategy 20 (material master, MRP 3 view, Strategy Group: 20) is pure MTO, where production is triggered by sales orders (VA01) without PIRs—fitting the "no forecasting" requirement. TheIndividual/Collective indicator(material master, MRP 4 view, field: Ind./Coll.) is set to "1" (Individual Requirements) for the component procured per sales order, generating separate dependent requirements per order, and "2" (Collective Requirements) for the component procured jointly, aggregating requirements across all orders into a single planned order or requisition.

Planning strategy 50 (Planning without final assembly)(A, C) relies on PIRs for subassemblies, conflicting with the "no forecasting" condition.Mixed MRP indicator(B, C) (MRP 4 view) applies to mixed MTS/MTO scenarios (e.g., strategy 11), not pure MTO, and doesn’t address the individual/collective split directly. Strategy 20 with the indicator meets SAP’s MTO configuration standards.

In SAP S/4HANA PP/DS, restricting planners to specific resources for planning is achieved through:

Use a resource group(A): Resource groups (defined in /SAPAPO/RES_GROUP or Customizing) aggregate specific resources (e.g., work centers from CR02 flagged for PP/DS). Planners can be assigned to a resource group via authorization profiles (PFCG),limiting their planning scope in tools like the Planning Board (/SAPAPO/CDPS0) or Product View (/SAPAPO/RRP3) to only those resources, ensuring controlled access.

Use a planning group(B) isn’t a standard PP/DS term—MRP groups exist in classic MRP, but not for resource restriction in PP/DS.Use a propagation range(C) (in /SAPAPO/CDPSC11) defines the scope of planning changes (e.g., horizon), not resource access.Use a planning area(D) (e.g., in APO) organizes data but doesn’t restrict resource-specific planning—it’s more for data segmentation. Resource groups align with SAP’s PP/DS security model.

In SAP S/4HANA, acollective orderis a network of production orders where a top-level order (for a finished product) is directly linked to subordinate orders (for assemblies), created automatically via special procurement key 52 (material master, MRP 2 view). The advantages include:

To perform availability checks across the entire collective order(A): When a collective order is created (e.g., via CO01 with "Collective Order" indicator), the system performs a material availability check (configured in OPL8) across all levels of the order hierarchy. This ensures components are available for the entire structure before release, reducing partial shortages.

To post confirmations for the entire collective order(D): Confirmations (e.g., via CO11N or CO15) for the top-level order can automatically trigger goods movements (goods receipt for the finished product, goods issue for components) across all linked orders. This streamlines shop floor processing by consolidating confirmations.

To coordinate orders in the planning board(B) is not specific to collective orders—it’s a general PP/DS or capacity planning feature (e.g., DS Planning Board), not an inherent advantage.To show the flow of batches(C) is possible via batch tracing (e.g., MB56), but it’s not a unique benefit of collective orders, which focus on production linkage, not batch visibility. This aligns with SAP’s collective order documentation.

In SAP S/4HANA and its broader ecosystem, forecasting for supply chain planning is supported by advanced tools:

Integrated Business Planning (IBP)(A): SAP IBP is a cloud-based solution designed for advanced supply chain planning, including demand forecasting. It uses statistical models, machine learning, and real-time data integration to predict demand, making it a primary tool for forecasting (e.g., SAP IBP for Demand).

Supply Chain Management (SCM)(B): SAP SCM, particularly its Advanced Planning and Optimization (APO) module (e.g., Demand Planning - DP), provides robust forecasting capabilities using historical data and planning algorithms. While SAP is transitioning APO functionalities to IBP, SCM remains relevant in on-premise or hybrid setups.

Material Requirements Planning (MRP)(C) in S/4HANA focuses on material planning based on existing demand (e.g., PIRs or sales orders) and does not perform forecasting itself; it relies on inputs from Demand Management.Capacity Requirements Planning (CRP)(D) deals with capacity leveling and scheduling, not demand forecasting. These distinctions are clear in SAP’s supply chain planning documentation.

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 SAP S/4HANA repetitive manufacturing, aline hierarchy(transaction LDM1) organizes production lines for planning and execution:

A production line with more than one work center(A): A line hierarchy represents a complex production line comprising multiple work centers (defined in CR01/CR02) linked in a hierarchical structure. For example, a main line (top node) might include sub-lines or work centers (e.g., assembly, testing), allowing detailed capacity planning and quantity assignment in MF50 or PP/DS.

Alternative sequence in the routing(B) (CA21, Alternative Sequence) defines optional operation paths, not a line hierarchy.Parallel sequence in the routing(C) (Parallel Sequence) splits operations concurrently, unrelated to line hierarchy structure.Prioritized alternative work centers(D) is managed via production versions or PP/DS mode selection, not line hierarchies, which focus on physical line organization. This is per SAP’s REM line hierarchy definition.

The Alert Monitor in SAP S/4HANA PP/DS (transaction /SAPAPO/AMON1) highlights planning issues. Configuration steps include:

Assign the alert profile to the overall profile(A): In Customizing (/SAPAPO/ALERT_PROFILE), you define an alert profile (e.g., specifying alert types like capacity overload) and assign it to an overall profile (e.g., in /SAPAPO/CDPSC11). This links alert settings to planning applications (e.g., Planning Board).

Create an object selection variant for production-planning-related alerts(D): You create a variant (e.g., in /SAPAPO/AMON_SETTING) to filter objects (e.g., materials, resources) for which alerts are monitored, tailoring it to production planning issues (e.g., late orders, shortages).

Assign the overall profile to the authorization profile(B) is incorrect—overall profiles link to planning, not authorization (handled via PFCG roles).Object selection variant for ATP categories(C) relates to availability checks, not production planning alerts, which focus on PP/DS issues. This is per SAP’s Alert Monitor setup.

Forecasting in SAP S/4HANA’s demand planning cycle, managed via transaction MC87 or MD61, generates planned independent requirements (PIRs) based on historical data and external factors. The process includes:

One-off events(A): These are special occurrences (e.g., promotions, trade shows) that can be manually entered or factored into forecast models (e.g., using event-based forecasting in the forecast profile) to adjust demand predictions.

Market intelligence(D): This refers to external data or insights (e.g., market trends, competitor actions) that planners can incorporate into forecasting models, often manually or via integration with tools like SAP Integrated Business Planning (IBP).

Past sales order quantities(E): Historical sales data (from transaction MD73 or LIS) is a core input for statistical forecasting models (e.g., constant, trend, seasonal models), allowingthe system to predict future demand based on past consumption.

Past production planning quantities(B) are not typically used in demand forecasting, as they reflect supply rather than demand.Past quotation quantities(C) could influence sales forecasting in some scenarios but are not a standard input in SAP’s demand planning cycle, which focuses on confirmed sales orders. This aligns with SAP’s forecasting methodology in Demand Management.

In SAP S/4HANA, a routing (transaction CA01/CA02) defines operation times for production, calculated using standard values and work center formulas. The time elements include:

Wait time(A): Defined in the routing (Operation Details, Standard Values), wait time is the duration an operation must wait after processing before moving to the next step (e.g., drying time). It’s part of interoperation times and affects scheduling.

Processing time(C): Also in the routing (Standard Values, e.g., Machine Time), this is the core time to perform the operation (e.g., machining), calculated via the work center’s processing formula (CR02, Capacity tab). It’s quantity-dependent and critical for lead time.

Setup time(E): Entered in the routing (Standard Values), setup time is the duration to prepare the work center (e.g., tool change), independent of quantity. It’s calculated using the setup formula in the work center and impacts total operation duration.

Float before production(B) is a scheduling margin in the material master (MRP 2 view) or production order, not an operation-specific time in the routing.Pick time(D) is not a standard routing term—it may relate to warehouse processes (e.g., WM), not production operations. This is per SAP’s routing structure.

In SAP S/4HANA PP/DS,standard heuristicsare predefined algorithms (e.g., SAP_PP_002 for planning standard lots) executed in the planning run (/SAPAPO/CDPSB0) or interactively (/SAPAPO/RRP3). Their purpose is:

To solve planning problems for defined objects(C): Heuristics address specific planning tasks for objects like materials, resources, or orders. For example, SAP_PP_002 creates planned orders to cover shortages, SAP_PP_020 sequences operations, and SAP_PP_007 adjusts schedules—each solving a distinct problem (e.g., demand coverage, capacity conflicts) based on defined parameters.

Automate material movements in staging(A) is handled by WM or Kanban, not PP/DS heuristics.Set default values in production master data(B) is a master data maintenance task (e.g., MM02), not a heuristic function.Optimize costs and times(D) is possible with optimization tools (e.g., PP/DS Optimizer), not standard heuristics, which focus on rule-based planning. This is per SAP’s PP/DS heuristic documentation.

In SAP S/4HANA, MRP determines whether to createplanned orders(for in-house production) orpurchase requisitions(for external procurement) based on specific master data settings in the material master. Theprocurement type(A), maintained in the MRP 2 view (field: ProcurementType), is a key determinant. For example, procurement type "E" (In-house production) triggers planned orders, while "F" (External procurement) generates purchase requisitions, and "X" (Both) allows MRP to decide based on additional settings like quotas.

Thematerial type(B), defined during material creation and linked to configuration (Logistics - General > Material Master > Basic Settings > Define Material Types), also influences this decision indirectly. For instance, material types like "FERT" (Finished Goods) are typically produced in-house, favoring planned orders, while "ROH" (Raw Materials) are procured externally, favoring purchase requisitions.MRP type(C) controls whether MRP runs (e.g., "PD" for MRP planning), but it does not directly determine the order type.MRP group(D) groups materials for planning parameters but does not directly dictate planned orders versus purchase requisitions.

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 Cloud Private Edition, supporting aGood Manufacturing Practice (GMP)compliant production process (common in industries like pharmaceuticals) involves features to ensure traceability, quality, and regulatory adherence:

Digital signature(A): SAP supports digital signatures (configured in Customizing, Cross-Application Components > General Application Functions > Digital Signature) for critical process steps (e.g., order release in CO02 or confirmation in CO11N). This ensures authorized personnel approve actions, meeting GMP requirements for accountability andaudit trails.

Recipe approval(C): In process manufacturing, recipes (process orders use Production Process Models or Master Recipes, transaction C201) require approval (status change, e.g., from "Created" to "Released" via ECM or C202). This ensures only validated production instructions are used, a key GMP compliance step.

Batch record(E): The electronic batch record (EBR, transaction COEBR or integrated in process order management) documents all production details (e.g., materials, quantities, quality checks). It’s mandatory for GMP to provide a complete, auditable history of each batch (configured via process order settings).

Approved resources(B) isn’t a standard SAP term—resources (work centers, CR02) can be quality-checked, but approval is process-driven, not a distinct feature.GMP-compliant flag(D) doesn’t exist as a specific field—GMP compliance is achieved through process controls, not a single indicator. This is per SAP’s GMP support documentation.

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 PP/DS, achieving a feasible production plan under capacity constraints involves:

Determine a time period with available capacity on the planning board(C): Using the DS Planning Board (/SAPAPO/CDPS0), planners can visually identify periods with free capacity on resources and manually or automatically schedule orders into those slots, ensuring feasibility.

Increase the capacity supply in a time-phased interval(D): In the work center (CR02, Capacity tab) or PP/DS resource (/SAPAPO/RES01), you can define additional capacity (e.g., shifts, overtime) for specific time intervals via capacity variants, allowing more orders to fit within constraints.

Form optimum sequences to reduce setup times(E): Using heuristics (e.g., SAP_PP_020) or the PP/DS Optimizer, you can sequence operations on resources to minimize setup times (defined in routing, CA02), maximizing throughput and resolving capacity bottlenecks.

Execute an infinite planning run(A) ignores capacity constraints, creating an unfeasible plan requiring later adjustment—not a solution.Reduce the planning time interval(B) (e.g., horizon in /SAPAPO/CDPSC11) limits scope but doesn’t address capacity directly. This is per SAP’s PP/DS capacity planning strategies.

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.