SAP PP explained: manufacturing in SAP

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 10 October 2026 · facts checked against the SAP Help Portal, October 2026

SAP PP (Production Planning), called Manufacturing on S/4HANA, decides what a plant builds, when, from which components and on which work centres, and records what happened when it was built. It holds the master data of making, the planning runs that turn demand into orders, and the execution of those orders up to the receipt of finished stock.

Two things changed with S/4HANA. Planning now runs as MRP Live, transaction MD01N, which does its work inside the HANA database, while classic MRP remains available and takes over the materials MRP Live cannot plan; and detailed scheduling and optimisation no longer need a separate APO system, because Production Planning and Detailed Scheduling (PP/DS) is embedded in S/4HANA, though Advanced Planning has to be activated, and licensed, first. Both appear under Manufacturing in SAP's S/4HANA guides, linked from the Help Portal.

What is SAP PP?

SAP PP is the production planning and control component of SAP ERP and S/4HANA — the searcher's "SAP production planning module" — and four master-data objects carry the whole of it. The bill of material lists what goes into a product, with a usage that separates the engineering view from the one production and costing read, alternatives for different lot sizes, and item categories that matter more than they look: a phantom assembly is exploded straight through and never exists as stock, and a non-stock item triggers a purchase requisition when the order is created.

The routing lists the operations, each on a work centre, each with a control key deciding whether the operation is scheduled, costed, confirmed or sent outside for external processing. Standard values — setup, machine, labour — are the numbers scheduling and costing both consume, and they reach Controlling through the activity types on the work centre's cost centre, which is why a wrong standard value shows up as a variance months later. The production version pairs one bill of material alternative with one routing for a validity period and a lot size range, and on S/4HANA it is mandatory for in-house production: planning and order creation find the bill of material and the routing only through a valid production version, which surprises consultants arriving from ECC.

What does an MRP run actually decide?

It decides three things per material: whether there is a shortage, how big the proposal covering it should be, and when it must start. Everything else is settings that steer those three. The MRP type says whether planning is deterministic against real demand or consumption-based against a reorder point or a forecast; the lot size procedure says whether the proposal is exactly the shortage, a fixed quantity, or everything needed in a week; safety stock and the scrap fields inflate every quantity downstream.

The output is a planned order for anything made in house and a purchase requisition for anything bought, which is the handover to Procurement. Above it sits the planning strategy: make to stock consumes planned independent requirements as sales orders arrive, make to order plans each order separately, and the strategy group on the material master is where the decision is recorded. On S/4HANA the run happens in the database rather than in the application server, which changed the runtime enough that nightly-only planning stopped being the assumption.

How does a production order move from release to completion?

Through a status chain: created, scheduled, components checked by the availability check, released, printed or issued as a paperless list, confirmed operation by operation, received into stock, technically completed, settled. Converting a planned order is what creates the order in the first place, and the order type brings its own settlement profile, number range and status behaviour.

Two of those steps generate most of the support tickets. The availability check refuses to release an order because a component is short, which is a planning conversation dressed as an error message. Technical completion closes an order that will never be finished, and the difference between technically completing an order and setting a deletion flag is the kind of distinction an interviewer uses to separate people who have run a plant from people who have read about one.

Does SAP plan capacity finitely?

Not by default: standard scheduling is infinite, and it will happily plan three orders onto one machine in the same shift, because capacity requirements are recorded but not enforced. Basic scheduling uses in-house production time from the material master; lead time scheduling uses the routing and produces real operation dates.

Making them enforced is the argument that runs through every manufacturing design. Capacity levelling and the planning table can be worked by hand; detailed scheduling with heuristics and a real constraint model sits in PP/DS, which is embedded in the core on S/4HANA rather than living in a neighbouring planning system. The honest position is that finite scheduling is worth it only where the plant will maintain the constraint data, and plenty of plants will not.

Discrete, process or repetitive: which manufacturing type?

Discrete is the default; process is chosen where a batch must be provable and repetitive where a line runs at a rate, and the choice sets the order object, the costing object and the paperwork for the life of the plant.

• Discrete — the production order, one order per batch of output, full traceability of what each order consumed and cost. The default when products vary.
• Process (PP-PI) — process orders, master recipes with phases and resources, control recipes and process instruction sheets going down to the plant and results coming back. Standard where a batch must be provable, so it usually arrives with Quality Management beside it.
• Repetitive — rate-based production against a production version, backflushed at reporting points, costs collected on a product cost collector instead of on orders. Less paperwork, less traceability.
• KANBAN — replenishment triggered by a control cycle and a signal from the line rather than by planning at all, used inside any of the above.
• Variant configuration — a configurable material whose characteristics select components and operations per order, so the bill of material and the routing are super-structures with dependencies rather than fixed lists.

Why does backflushed stock go missing?

Because the confirmation posts while the failed goods movement waits quietly in COGI, the postprocessing list for faulty goods movements, until someone clears it. Components can leave stock in two ways: staged and issued against the order, or backflushed automatically when a confirmation is posted. The second is faster and is where inventory accuracy goes to die, because a backflush that fails — no stock in the storage location, a batch not determined — leaves the order confirmed and the stock untouched, and COGI has no owner unless somebody was named.

This is also the border where manufacturing and the warehouse have to agree. Production supply areas, control cycles and staging methods belong jointly to PP and warehouse execution, and the design that works is the one the shift lead can carry out without a screen in front of them.

Where does a production order touch costing and inspection?

Everywhere it posts, because a production order is a cost object as well as an instruction. Components issued to it and time confirmed against its operations debit it, the receipt of the finished goods at standard price credits it, and whatever is left over becomes a variance somebody in Controlling must explain, which is why product costing is only ever as good as the bills of material and routings a manufacturing consultant maintains.

In-process inspection lives inside the order as an inspection lot tied to an operation. Downwards, confirmations and machine data increasingly come from a manufacturing execution layer rather than from a person typing, so interface literacy — what the plant sends up, what the core sends down, what happens when the queue stops — is now part of the functional job rather than a technical afterthought.

What gets a manufacturing consultant hired?

One plant described end to end: its manufacturing type, how deep the bills of material go, whether confirmations are typed or machine-fed, and what broke in the first week. Production planners, schedulers and manufacturing engineers make the strongest converts, because the configuration is the easier half to learn and the floor is not; key users who ran their plant's planning through a go-live follow (the key-user route). Interviewers linger on cutover, because it is physical: work in progress closed or carried, stock counted, a freeze window negotiated with people who lose money for every idle hour (how projects are shaped).