SAP Process Manufacturing Tutorial (Part 1)

Discrete manufacturing (assembling cars, electronics) uses bills of material and routings tied tightly to individual materials and operations performed by machines or labor. Process manufacturing (chemicals, pharma, food, beverage) is different: production is defined by formulas or recipes that describe proportions of ingredients, phases of a continuous or batch process (heating, mixing, reacting, cooling), and quality-critical parameters like temperature, pH, or pressure that must be recorded, not just quantities consumed. SAP's PP-PI (Production Planning for Process Industries) component was built specifically to model this reality, and it remains conceptually present, though technically converged, in S/4HANA.

The three foundational master data objects are the master recipe, the resource, and the material list (formula). The material list is the process-industry equivalent of a bill of material: it lists the ingredients (components) and their quantities or percentages needed to produce a batch of the finished product, and it can include by-products and co-products naturally, which is common in chemical reactions. The resource is broader than a discrete work center: resources model not just machines but process units, storage tanks, or lines with capacities, and they carry standard values for process instructions like duration or rates. The master recipe ties these together: it defines the sequence of phases and operations, links to resources responsible for executing them, references the material list for component consumption, and embeds process instructions and characteristics that will later print on a Process Instruction Sheet (PI sheet) used by the plant operator or captured through automation interfaces.

At runtime, when a process order is created (either manually or from planned orders via MRP), the system copies the master recipe, material list, and resource assignments into the order, similar to how a discrete production order copies a routing and BOM. The process order then carries phases (not just operations) as the level at which confirmations, goods movements, and PI sheet data are recorded. A phase is a self-contained unit of work with its own control key that determines whether it triggers scheduling, costing, or PI sheet generation. This phase-based structure is a hallmark of process manufacturing and is the reason many QM inspection lots and batch determination logics attach at the phase level rather than the header.

Why this matters for a consultant: process industries operate under tighter regulatory and quality obligations (batch genealogy, electronic batch records, environmental limits) than typical discrete manufacturing, so incorrect recipe design or resource assignment can cause not just planning inefficiency but compliance failures. Understanding the recipe-resource-material list triangle is the prerequisite for every later topic in this module: PI sheets, batch management integration, process order confirmation, and costing by phase.

In S/4HANA, the underlying data model for PP-PI has been harmonized under the umbrella of production planning, and the transactions and master data concepts remain largely familiar to ECC consultants, though embedded analytics and Fiori apps provide newer ways to monitor process orders. Consultants should always verify with the client's specific S/4HANA release which classic transactions are still supported versus redirected to Fiori equivalents, since SAP has been progressively simplifying and, in some areas, restricting classic GUI transactions in newer public cloud releases.

A specialty chemicals manufacturer implementing S/4HANA needed to model a multi-phase reaction process where an intermediate product is produced, held in a reactor, then further processed into two co-products. The consultant built a master recipe with three phases mapped to two different resources (a reactor and a finishing unit), used the material list to define the primary input plus two co-products with valuation-relevant apportionment, and validated that process orders created from planned orders correctly inherited phase-level control keys so that goods movements and confirmations would post at the right operation.

• Treating the material list purely as a BOM copy without accounting for co-products and by-products particular to the reaction.
• Assigning all phases to a single generic resource, losing the ability to schedule and cost distinct process steps separately.
• Forgetting to set the correct control key on phases, which then fails to trigger PI sheet generation or milestone confirmation.
• Confusing routing operations (discrete) with recipe phases (process) when consultants move between projects, leading to incorrect assumptions about confirmation logic.

• Design master recipes with phases that reflect real physical process steps to support meaningful confirmations and quality checks.
• Use resources rather than simple work centers when process-specific capacity or standard values (e.g., batch cycle time) matter.
• Keep material lists aligned with actual chemistry/formulation documentation to avoid discrepancies between engineering and SAP master data.
• Validate control key settings on every phase before moving a recipe to production status.

Interviewers often ask candidates to explain the difference between a BOM/routing pair and a material list/master recipe pair, and why phases exist instead of operations. A strong answer highlights that phases carry control keys enabling PI sheets, batch and quality integration, and that process industries require recipe-level modeling of by-products and process parameters that discrete manufacturing does not need.