A team closing dozens of identical production orders every week on a perfectly stable line, and a controller analyzing variances order by order when nothing ever changes: that is the classic symptom of an SAP production type chosen by default.
The wrong choice breaks nothing. It simply makes you pay an administrative overhead every single day. Discrete, repetitive or process: this guide reviews the three SAP production types and, above all, the criteria that actually tip the decision.
- SAP PP offers 3 production types: discrete (order-driven), repetitive (lean flow) and process (recipes and batches).
- The type captures the frequency, complexity and stability of your process: it is one of the first implementation choices, and an expensive one to reverse.
- Repetitive (REM) runs without production orders: planned orders, backflush and period-based costing through the product cost collector.
- Process replaces BOM and routings with master recipes on resources, with batch management and active ingredient handling (exclusive to this type).
- MTS and MTO are supported by all three types: this is not a selection criterion.
Why the SAP PP production type shapes everything that follows
The production type describes how a product is manufactured: how often, with how much complexity, and with how much stability. It is one of the very first decisions in an SAP PP implementation, and it conditions everything downstream: the management objects (orders or no orders), the master data to build, the way production is confirmed and the way costs are posted.
It is also a decision that is hard to reverse. Moving from discrete back to repetitive after go-live means rebuilding master data, retraining teams and reworking production reporting. Hence the value of laying out the right criteria during the scoping workshop, rather than copying the settings from the previous project.
The 3 SAP production types at a glance
Discrete manufacturing produces distinct, often assembled units: each run goes through a production order that specifies components, operations and work centers. Repetitive manufacturing (REM) targets mass production of a stable product on a dedicated line: management is stripped down to the minimum, with no production orders. Process manufacturing covers production by chemical or physical transformation, where you mix, heat and transform quantities rather than assemble parts.
The criteria that actually tip the decision
MTS or MTO? Wrong question: all three types support both strategies. In the discrete vs repetitive vs process manufacturing debate in SAP, the deciding criteria sit elsewhere, and they are measurable on your real process.
| Criterion | Discrete | Repetitive (REM) | Process |
|---|---|---|---|
| Stability and complexity | Complex process, intermediate storage | Very stable, high volumes, no complexity | Complex process, often continuous flow |
| Production flow | Order-driven | Lean, no order types (planned orders) | Order-driven (process orders) |
| Changeovers | Frequent | Rare | Frequent |
| MTS / MTO | Supported | Supported | Supported |
| Batch management | Possible | Possible | Intensive |
| Active ingredient management | Not available | Not available | Available |
| Material quantity calculation | No | No | Yes |
| Component staging | With reference to the order | Periodic and anonymous | With reference to the process order |
Three rows of this grid are often enough to decide. Changeover frequency first: a line that produces the same material for weeks has no business running in discrete. Component staging next: supplying components for a specific order, or feeding the line continuously and anonymously, are two different shop floor organizations. Active ingredients last: if your materials have a variable concentration to compensate batch by batch, process manufacturing is the only type that handles it natively.
Costs by order or by period: how Repetitive Manufacturing (REM) changes controlling
One criterion underestimated in design workshops, yet decisive for daily operations: where production costs accumulate.
In discrete and in process, each order carries its own costs: consumed materials, confirmed times, overhead. The order is settled (settlement), and the controller analyzes variances order by order. That is valuable when every run is different, and exactly what becomes absurd when production never varies.
In repetitive, costs accumulate on a product cost collector, and the analysis runs by period: you compare what the line consumed and produced over the month, not over a single order. Less granularity, far less closing workload. For a stable line, that is the right trade; for complex make-to-order production, it would be a loss of control.
Which SAP production type for which industrial scenario
Three typical scenarios sum up the trade-off as you meet it in scoping.
Assemble-to-order with variants: configured products, bills of material that change with every sales order, specific assembly operations. Discrete wins: the production order precisely traces components, operations and costs for each unit produced. You typically find it in special machinery, aerospace or complex electronics.
The stable mass line: the same material, in high volume, over an extended period, with rare changeovers. Repetitive lets you plan by production rate, confirm through backflush and smooth out cost analysis by period. Automotive series production and consumer goods are its classic ground.
Recipe-based continuous flow: mixtures, reactions, temperatures, precise proportions, batch traceability and active ingredients to compensate. Process manufacturing is built for that, with its master recipes and its process orders. Pharma, chemicals, food and cosmetics live there every day.
Master data and real objects by type: what you will configure
Beyond the principles, each type commits you to concrete objects, and that is where the differences become visible for the key user.
In discrete, the chain is the best known: bills of material (BOM), routings and work centers describe the product and the process; MRP generates planned orders that you convert into production orders; creating the order automatically generates the component reservations and the capacity requirements on the work centers. Upstream planning can rely on a pMRP capacity simulation before those planned orders even exist.
In repetitive, you configure a REM profile, activate the type on the material, and production versions become mandatory: they are what links material, BOM and production line. No order types: the line runs on planned orders, consumption is posted through backflush, and costs converge on the product cost collector. Component planning granularity can be tuned finely, in particular through MRP areas when the plant feeds the line from separate areas.
In process, the master recipe replaces the BOM and routing pair: it describes the ingredients, the phases and the parameters of the process, executed on resources rather than work centers. Process orders drive execution, PI sheets guide the operators, and batch management ensures lot traceability, with active ingredient management when material potency varies.
Decision checklist before you freeze your production type
Before locking the choice in a design workshop, four closed questions sort it out:
- Are your changeovers frequent or exceptional? Frequent: discrete or process. Rare on a stable line: repetitive.
- Are your components staged for a specific order, or is the line fed continuously? Periodic anonymous staging is the signature of repetitive.
- Does order-by-order cost analysis actually teach you anything? If the answer is no, the REM product cost collector will lighten your closings.
- Do you have recipes, batches and active ingredients to compensate? If yes, process manufacturing is the only type natively equipped.
And if several answers contradict each other, remember that an SAP plant is not monolithic: production types are chosen per material and per process, not once for the whole plant. The same plant runs repetitive on its stable lines and discrete in its customization shops. The official concept is covered in the public course Exploring Production Planning in SAP S/4HANA.
The production type is one of those silent decisions that separates an SAP PP setup that supports the shop floor from one that slows it down. Choose on your measured criteria (changeovers, staging, cost granularity), not out of habit. And upstream of execution, a pMRP capacity simulation will tell you whether the demand plan fits on your lines, whatever type you pick.
FAQ: your questions about SAP production types
Can you mix several production types in one SAP plant?
Yes, and it is very common. The production type is set per material and per process, not globally: the same plant can run repetitive on its mass production lines and discrete in its assemble-to-order shops.
What is the difference between a production order and a planned order in repetitive manufacturing?
In repetitive, the planned order generated by MRP is not converted into a production order: the line executes directly on planned orders, and consumption is posted through backflush. That is the whole point of REM: no order type to create, track and close.
Does SAP repetitive manufacturing support make-to-order?
Yes. MTS and MTO are supported by all three production types, repetitive included. The planning strategy is therefore not a criterion for choosing the type: process stability, component staging and cost granularity are what settle it.
Why does process manufacturing use master recipes instead of routings?
Because transformation-based production cannot be described like an assembly: the master recipe combines in a single object the ingredients, the process phases and their parameters (temperatures, durations, proportions), executed on resources. It replaces the BOM and routing pair of discrete manufacturing.
How are costs posted in REM without a production order?
Through the product cost collector: the consumption and confirmations of the line accumulate there, and the analysis runs by period (monthly, for example) rather than order by order. Less granularity, far less closing workload, suited to stable production.
Is active ingredient management available in discrete manufacturing?
No. Active ingredient management, which compensates for variable material potency batch by batch, is exclusive to process manufacturing. If that need exists in your process, the type choice is effectively settled.
Keep reading
SAP PRT: Production Resources and Tools
On an industrial site, the tools shared between production lines are often invisible in SAP. Jigs, probes and technical drawings move from one order to the next, but nobody knows...
Pierre B.
Beginner's guide to batch management in SAP MM
I have seen consultants tick the "Batch management" box on thousands of materials in a MASS run, without realizing the batch level was still set at client level. A few...
Pierre B.
SAP batch determination and management
You are configuring SAP batch determination and the engine does not kick in. You are picking batches in the wrong order even though the sort rule is correctly set up....
Pierre B.
SAP Production Version: setup with C223 and MRP4
https://youtu.be/Bae4g30aZC4 The production version is the SAP object that says "to manufacture this material, you combine this bill of materials with this routing, over this period". On an S/4HANA project,...
Pierre B.