Mon – Sat: 9:00 AM – 7:00 PM IST
SAP

What is SAP PP?

SAP's production planning module — from demand through planned orders to a confirmed production order.

In short

SAP PP (Production Planning) covers demand management, material requirements planning, capacity planning and production order execution. It uses bills of material and routings to explode demand into component requirements and operations, creates planned orders, and converts them to production orders that the shop floor confirms against.

Why It Matters

Why this matters in practice

PP is where the plan meets the factory, and it is the module most sensitive to master-data quality. A wrong BOM produces wrong purchase suggestions; a wrong routing produces wrong capacity and wrong labour absorption. Implementations that rush master data reach go-live with a planning engine producing confident nonsense.

Explodes demand through BOMs into component requirements
Routings drive capacity planning and cost absorption
Planned orders convert to production orders for execution
Confirmations feed WIP, costing and stock in one step
How It Works

How it works in practice

1

Demand management

Forecast and firm requirements combine into the demand programme that MRP plans against.

2

MRP run

Explodes requirements, nets against stock and open orders, offsets by lead time, and proposes planned orders and purchase requisitions.

3

Capacity planning

Work centre capacity compared against the operations the routings require. Overload surfaces here, before the shop floor finds it.

4

Production order

Converted from a planned order. Components are reserved, operations scheduled, costs collected against it.

5

Confirmation and settlement

Operations confirmed, goods receipt of finished product, order settled and variance cleared.

Worked example

A worked example: a schedule that could not be built

MRP produces a plan that looks reasonable on paper. The shop floor cannot execute it, and the planners begin overriding it daily until the system is effectively bypassed.

The cause is that capacity was never modelled. Work centre available capacity was left at the default, routing times were copied from an old system and never verified, and setup times were omitted entirely because they seemed small. MRP, which plans materials rather than capacity, happily produced a schedule requiring one work centre to run thirty-one hours in a day.

Fixing it means doing unglamorous work: timing operations, recording real setup times, setting honest available capacity including maintenance and breaks, then running capacity levelling so infinite plans become finite ones. The underlying point is that production planning is only as good as the routing data, and routing data is the thing most likely to have been migrated from an old system without anyone checking whether it was ever right.

Key terms

The vocabulary, briefly

Term What it means
Work centre Where an operation is performed, carrying capacity and cost rates.
Routing The sequence of operations to make a material, with times and work centres.
Production order The authorisation and cost collector for a specific manufacturing run.
Confirmation Reporting progress against an operation — quantities, times, scrap.
Capacity levelling Smoothing load against available capacity so the plan is executable.
What Goes Wrong

Common mistakes worth avoiding

BOMs and routings not maintained

Every output of PP derives from them. Engineering changes that never reach SAP make the plan fiction.

Production orders never settled

Unsettled orders hold value in WIP and distort both inventory and cost of sales.

Capacity ignored

Running MRP without capacity planning produces a material plan the factory cannot execute.

Discrete configuration used for process industry

Formulas, co-products and potency need PP-PI. Forcing discrete configuration onto a process plant causes costing problems that are hard to unpick.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Schedule adherence Orders completed in the planned period. The honest measure of whether planning works.
Capacity utilisation by work centre Where the real constraint is, which is often not where it is assumed.
Routing time accuracy Confirmed times against planned. Persistent gaps invalidate every schedule.
Order confirmation lag How long after work happens it is recorded. Long lags make WIP and progress unreliable.
FAQ

Questions we are asked about this

PP suits discrete manufacturing — assembled items with BOMs and routings. PP-PI suits process industries with recipes, batches, co-products and potency-based materials.
MRP's proposal: a suggestion that something be made, with quantity and date, not yet a commitment. Converting it to a production order is the decision to actually make it.
Discrete manufacturing makes countable units from a bill of materials through a routing — machines, assemblies, devices. Process manufacturing produces quantities from recipes with batch characteristics, co-products and by-products — chemicals, food, pharmaceuticals. SAP provides PP for discrete and PP-PI for process, and the difference is not cosmetic: using discrete manufacturing for a genuinely process business means modelling batch attributes and yield variability by workaround.
If any work centre is ever a bottleneck, yes — and almost every real factory has one. Without capacity modelling, MRP plans material availability only and will produce schedules that cannot be executed. Planners then override the system, which is both a waste of the system and a loss of visibility, because overrides live in people's heads rather than in the plan.
The production order is the cost collector: material issues, confirmed labour and absorbed overhead accumulate against it, and on settlement the balance moves to stock or to variance accounts. This means confirmation discipline is a costing issue as well as a planning one — late or inaccurate confirmations produce both an unreliable schedule and unreliable product costs, and finance usually notices the second before operations notices the first.
Backflushing consumes components automatically on confirmation, based on the bill of materials, rather than issuing them individually. It saves substantial transaction effort and is appropriate where the BOM is accurate and consumption is predictable. Where the BOM is wrong, backflushing propagates that error onto every order silently, which is why BOM accuracy should be measured before backflushing is enabled rather than after.
Related

Where to read next

What is a bill of materials?

Read more

What is MRP?

Read more

Our SAP consulting services

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.