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

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.

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.

Aphantom assemblyin SAP S/4HANA is a virtual component that is not physically stocked—its components are directly consumed in the higher-level assembly. To set it up:

Select a special procurement type inside the material master(A): In the material master (MRP 2 view, field: Special Procurement), set the value to "50" (Phantom Assembly). Thistells MRP and production to bypass stocking the phantom material and explode its BOM directly into the next level (e.g., in CO01 or MD02).

Define the special procurement type inside the material BOM (bill of material)(D): In the BOM (CS02), for the phantom component, set the "Special Procurement" field (Item Detail screen) to "50." This overrides the material master setting for that specific BOM usage, ensuring the phantom behavior applies only in that context.

Use a special item category(B) like "L" (Stock Item) or "N" (Non-Stock) in the BOM (CS01, Item Category) defines component handling but does not designate a phantom—phantom status comes from procurement type.Select a special MRP type(C) (MRP 1 view) controls planning (e.g., "PD" for MRP), not phantom behavior. This is per SAP’s phantom assembly configuration.

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.

The material type in SAP S/4HANA (selected in MM01, configured via OMS2) defines a material’s properties and behavior:

Which document types and class categories are allowed(A): Material type determines which business documents (e.g., purchase orders, production orders) can be created and which classification categories (e.g., batch, variant) apply. For example, "FERT" allows production orders, while "NLAG" (non-stock) restricts inventory documents (configured in Logistics - General > Material Master > Define Attributes of Material Types).

Which material master screens appear and in which sequence(C): Material type controls the views available in the material master (e.g., MRP for "FERT," no Sales view for "ROH") and their order, based on Customizing (OMS2, field selection and view sequence). This tailors the interface to the material’s purpose.

Plant-specific and plant-independent statuses(B) are managed via material status (Basic Data view), not material type—type defines broader attributes.Whether produced in-house or procured(D) is set by the Procurement Type (MRP 2 view), not directly by material type, though type may imply defaults (e.g., "ROH" for procurement). This is per SAP’s material type definition.

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.

In SAP S/4HANA repetitive manufacturing, confirming a finished product (e.g., via transaction MFBF) triggers default actions based on the REM profile (Customizing, OSP2):

Post the goods receipt for the finished product(A): When saving a confirmation (MFBF,Backflush tab), the system posts a goods receipt (movement type 101) for the finished product into stock (e.g., unrestricted use), assuming backflushing is active in the REM profile (field: Backflush Mandatory).

Reduce run schedule quantities(B): The confirmed quantity reduces the openrun schedule quantities(planned orders in MD04 or MF50), aligning the planned production with actual output to prevent overproduction.

Update statistics for the Business Information Warehouse(D): Confirmation data (e.g., quantity, time) updates statistical tables (e.g., S031, S032) for reporting in SAP BW or embedded analytics, providing insights into production performance (enabled by default in standard settings).

Post production costs to the planned order(C) is incorrect—costs are posted to aproduct cost collector(KKF6N) in REM, not planned orders, based on the REM profile’s costing settings.Create associated capacity requirements(E) occurs during planning (e.g., MRP), not confirmation—capacity is consumed, not created, at this stage. This is per SAP’s REM confirmation 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, the goal is to plan in-house production of a semi-finished material using planned independent requirements (PIRs), with those PIRs consumed by dependent requirements from the finished good’s production:

Planning at assembly level (70)(D): Strategy 70 (material master, MRP 3 view, Strategy Group: 70) is designed for subassemblies or semi-finished materials. PIRs are entered for the semi-finished material (MD61), triggering in-house production (planned orders via MRP). When a sales order for the finished good is received, the dependent requirements (from BOM explosion) consume these PIRs within the consumption period (MRP 3 view), aligning production of the semi-finished material with higher-level demand.

Assembly processing with production orders (82)(A) is an MTO strategy tied to sales orders, not PIRs.Planning with final assembly (40)(B) applies to finished goods, where PIRs are consumed by sales orders, not dependent requirements of semi-finished items.Production by lot size (30)(C) focuses on lot-size-based production without consumption logic. Strategy 70 is explicitly designed for this scenario per SAP documentation.

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.