SAP Concepts: Plan-to-Produce in SAP: BOM, MRP, Production Order, Settlement (PP, MM, FI)

If you've been following the SAP Concepts series, you've now seen the two processes every company runs — Procure-to-Pay (buying) and Order-to-Cash (selling). Both were clean linear flows across two or three modules.

Plan-to-Produce is different. It's the process that turns raw materials into finished goods, and it only applies to companies that physically make things. It's also, by some margin, the most complex of the three core business processes — because making things in the real world is fundamentally messier than buying or selling them.

This is episode six of our SAP Concepts series, and we're going to walk the full manufacturing cycle from forecast to finished goods. You'll meet the MRP engine, the production order as a cost-collector, the movement types that post goods issues to production and goods receipts from production, and — critically — the settlement step at period-end that reconciles actual cost against standard.

If manufacturing sounds intimidating, don't worry. The shape is coherent. Let's walk it.

The six-step shape

Plan-to-Produce in SAP has roughly six steps, which span three modules (PP, MM, FI).

1. Demand trigger — a forecast or sales order creates a need to produce
2. MRP run — the planning engine explodes the BOM and creates planned orders
3. Production order — a planner converts the plan into a committed work order
4. Goods issue to production — raw materials leave the warehouse for the shop floor
5. Confirmation — the shop floor reports completed work (labour and machine time)
6. Goods receipt from production — finished goods arrive at the warehouse, and period-end settlement posts variance

Each step has its own posting rhythm. Let's walk them.

Step one: the demand trigger

A manufacturing business needs something to trigger production. Usually it's one of two things:

Sales forecast. The sales team projects demand for a product over the next quarter. Planning works backward from the forecast to figure out production volumes and timing.

Stock minimum reached. A material's inventory drops below its reorder point. The system automatically creates a demand signal to replenish.

In both cases, the result is a number: we need X units of this finished product, by this date. That number becomes the input to the next step — the MRP run.

Step two: the MRP run

MRP — Material Requirements Planning — is where the planning software earns its keep. It's the engine that takes a finished-good demand number and figures out exactly what to buy, what to make, and when.

The MRP algorithm explodes the bill of materials (BOM) for the finished product. If we need 100 chairs, and the BOM says each chair has one seat, four legs, sixteen screws, and one cushion, MRP calculates the raw-material demand: 100 seats, 400 legs, 1,600 screws, 100 cushions.

Then for each component, MRP checks inventory: how many do we have on hand? How many are already on open purchase orders? How long is the lead time to get more? And based on that, it time-phases the purchases: "order the legs by next Monday so they arrive before the production start date of the 20th."

The MRP run produces two kinds of output:

• Planned purchase orders — signals to procurement to buy specific raw materials
• Planned production orders — signals to manufacturing to start specific production runs

Notice the word "planned". MRP's outputs are proposals, not commitments. A human — the planner — reviews them and converts them into real orders. No financial posting happens during the MRP run itself; it's a pure calculation.

In S/4HANA, MRP was rewritten as MRP Live, which runs on HANA directly and is dramatically faster than the older ECC batch-based MRP. A large company's MRP run used to be an overnight job; on MRP Live it's minutes.

Step three: the production order

A planner reviews the planned production order and converts it into a real production order. This is the formal commitment: we will produce this quantity of this product, in this plant, with these materials, using this routing (the sequence of operations), targeting this completion date.

At production order release, three things happen automatically:

Materials are reserved. The raw materials the BOM calls for are logically reserved in inventory — other orders can't plan to consume the same stock.

Capacity is booked. The work centres (machines, assembly stations) named in the routing have their capacity reduced for the scheduled dates. If you try to schedule another order at the same time, the system warns about capacity conflicts.

A statistical plan cost is calculated. The production order becomes a cost collector: every material consumption and every hour of labour will accrue against this specific order number. The plan cost is the target against which actual cost will be measured at settlement.

No FI posting yet. The production order sets up the scaffolding — the reservations, the capacity, the cost collector — but no journal entry has happened.

Step four: goods issue to production

The production order is released and work is about to begin. The shop floor needs the raw materials from the warehouse, so a goods issue is posted.

The goods issue uses movement type 261 — "goods issue to production order". Two things happen:

MM decreases inventory. Raw material stock drops by the issued quantity. The materials are now logically on the shop floor, not in the warehouse.

FI posts a journal entry:

Dr  Raw material consumption             €9,840
    Cr  Raw materials inventory                €9,840

Raw materials inventory is credited (it goes down). Raw material consumption — an expense account — is debited. The consumption is assigned to the production order, so the production order's actual cost is now €9,840 of consumed raw material.

The material value comes from the material ledger — in a moving-average valuation, it's the current average price; in a standard-cost valuation, it's the standard cost. Either way, the amount is deterministic and traceable.

Step five: confirmation (labour and machine time)

The shop floor doesn't just consume materials — workers and machines spend time on the order. Each operation in the routing (say, "assemble", "test", "pack") has a target time, and the shop floor reports actual time via confirmations.

Each confirmation triggers what's called an activity allocation in CO — the work centre's cost centre transfers cost to the production order.

Dr  Production order (cost collector)    €6,500
    Cr  Work centre cost centre               €6,500

The amount is calculated as hours × activity rate (from master data — typically something like €42/hour for labour, €28/hour for machine time). The production order accumulates both the material cost from step four and the activity cost from step five.

Importantly, this is a CO posting — a secondary cost posting, moving cost between internal cost objects. It doesn't yet hit the FI primary ledger. The production order is building up an internal cost balance, which will be reconciled to FI at period end.

Step six: goods receipt and settlement

Finally the production is complete. Finished goods are delivered to the warehouse, using movement type 101 (goods receipt from production).

Two things happen at goods receipt:

MM increases finished goods inventory. Stock of the produced product goes up.

FI posts at the standard cost of the finished good:

Dr  Finished goods inventory          €15,000
    Cr  Factory output (credits the order)     €15,000

Inventory goes up by the standard cost. The production order is credited by the same amount — essentially, the standard value is "taken off" the order.

But the order might have accumulated more or less than €15,000 of actual cost. From step four we added €9,840 of materials. From step five we added maybe €6,500 of labour and machine time. That's €16,340 of actual cost, but we only credited €15,000 at goods receipt. The difference — €1,340 — is the production variance.

At month-end, the production order is settled (transaction KO88). The settlement posts the remaining balance (the variance) to FI:

Dr  Production variance                  €1,340
    Cr  Production order (cost collector)         €1,340

The variance lands in FI and CO, typically split into components (material variance, labour variance, etc.) and assigned to a profit segment for margin analysis. The production order balance clears to zero.

Why this matters

Plan-to-Produce is where the financial picture of a manufacturer is really shaped. The difference between standard cost (what finance planned for) and actual cost (what the factory consumed) is the variance — and variance analysis is how management understands whether the factory is operating efficiently.

Positive variance (actual higher than standard) means the factory is more expensive than expected. Could be a materials problem — scrap, yield issues. Could be a labour problem — overtime, inefficiency. Could be a pricing problem — raw materials cost more than the standard. Variance analysis gets the business to the root cause.

For SAP consultants, PP is the most specialised of the logistics modules. It combines master-data heavy setup (BOMs, routings, work centres) with transactional flows (orders, confirmations, settlement) and tight integration with MM (materials) and CO (activity-based costing). A PP specialist is valuable because they can see across all three.

What's next

That's Plan-to-Produce. Demand through MRP, planned order through production order, materials and labour accruing against a cost collector, goods receipt at standard, and finally variance at settlement.

With P2P, O2C, and Plan-to-Produce under your belt, you now have the three big business processes that run every SAP system. Episode seven shifts gears — we'll look at the organisational structures underneath every transaction. Client, company code, plant, storage location, sales organisation. The skeleton every SAP transaction hangs off.

See you there.