- Home
- Modules
- SAP PP
SAP PP: from the plan to the finished goods
Production Planning, explained for users and for consultants from other modules.
MD04FG-500 Lemon soda, 12-packStock400Sales order−300Forecast−250Production order+50010 · Bring process forward1000457CO11N0010 Mix syrupConfirmed0020 Fill and sealRunning0030 PackWaitingOverview
What PP is, if you have never worked with it
SAP PP, Production Planning, is the part of SAP that runs the make side of a company. It turns demand into a plan, works out which materials and capacity the plan needs, and then controls production through orders: what to make, when, with which components and on which machines. SAP’s courses for SAP S/4HANA often say Manufacturing, but transactions, tables and almost everyone on a project still say PP.
This page is for the people who work around PP without being PP consultants: planners, supervisors and key users, and FI, CO, MM or SD consultants who keep meeting production orders. It follows one order from the forecast to the variance, lets you run a small MRP and a production order of your own, and lists the transactions worth knowing.
- SAP ECC 6
- SAP S/4HANA
- SAP S/4HANA Cloud
MD04CO01CO11NUse the User | Consultant switch at the top of the page to show or hide the technical layer: Customizing transactions, tables and the settings behind each step.
The make side of SAP
PP covers plan to produce: demand, MRP, production orders, confirmations and goods movements. MRP plans only where a net requirement exists, creating planned orders for what is made in-house and purchase requisitions for what is bought.
Source: SAP Learning, understanding MRPThree ways to produce
Discrete manufacturing runs on production orders, process industries on process orders (PP-PI), and repetitive manufacturing on run schedules, with costs on a product cost collector instead of an order. The table below compares them.
Source: SAP Help, repetitive manufacturingEvery order is a cost object
A production order collects actual costs: components issued and hours confirmed. The goods receipt credits it at the standard price, and what is left becomes a variance that Controlling settles at month-end. That is why FI and CO consultants meet PP every close.
Source: SAP Learning, settlement of a delivered order
Discrete, process or repetitive
| Discrete | Process (PP-PI) | Repetitive (REM) | |
|---|---|---|---|
| Order | Production order | Process order | Run schedule, planned orders |
| How it is made | Routing | Master recipe | Routing or rate routing |
| Where | Work center | Resource | Production line |
| Confirm with | CO11N | COR6N | MFBF |
| Costs land on | The order | The order | Product cost collector |
Sources: SAP Help, make-to-stock repetitive manufacturing; SAP blogs on PP-PI and on the REM steps with transaction codes.
This page uses one example
FG-500, a 12-pack of lemon soda cans
Made in-house on a filling line from 12 cans and 1 carton per pack. It appears in the process, in the MRP you can run and in the production order whose postings you can follow. Numbers are examples only.
Who PP talks to
A production order touches almost every module, which is why a “production problem” so often ends up on an MM, CO or FI desk.
- MMComponents and purchasingComponent stock, goods issues and the purchase requisitions MRP creates for bought materials.
- SDCustomer demandSales orders as requirements, alongside the forecast.
- CO-PCProduct costingStandard cost estimates, then WIP, variances and settlement of each order.
- FI / MLInventory and variancesA journal entry at every goods movement; price differences on the material with the Material Ledger.
- QMQualityInspections during production; the Manage Production Orders app flags out-of-range results.
- PP/DSDetailed schedulingFinite capacity and exact times, embedded in SAP S/4HANA since release 1610.
Master data
What PP needs before the first order
Before MRP can plan or an order can run, PP must know what the product is made of, how and where it is made, and which combination to use. Most “the order won’t work” problems start here. Pick an object to see what it holds and why CO cares.
Organization
Plant and MRP area
The plant is where production happens and where MRP plans. In SAP S/4HANA, MRP plans only at plant and MRP area level; MRP areas are active by default and replace the old storage location MRP, for example to plan each subcontractor separately.
Example: Plant 1000, with an MRP area for a subcontractor
Why CO cares
A plant belongs to one company code and is the level at which stock is valued, so inventory, production costs and variances all carry the plant.
Consultant toolsOX10OPPQ
Customizing and mass-maintenance tools for each object are in the Consultant view.
Master data
Material master
Four MRP views tell planning how to treat the material: MRP type, lot size, procurement type, safety stock, in-house production time and strategy group. The work scheduling view adds production data such as the production supervisor and the backflush indicator.
Example: FG-500: MRP type PD, lot size EX, procurement type E (in-house)
Why CO cares
The standard price in the accounting view values every goods receipt from production, and the costing views tell the cost estimate how to cost the material.
Maintain inMM02MM03
Consultant toolsOPPR
Customizing and mass-maintenance tools for each object are in the Consultant view.
What goes in
Bill of materials (BOM)
The components and quantities needed to make one base quantity of the product. MRP explodes it to plan the components, and the production order copies it as its component list.
Example: 12 cans and 1 carton for each 12-pack
Why CO cares
The BOM is the material quantity structure of the standard cost estimate: change a quantity and the next cost estimate, and every variance after it, changes too.
Maintain inCS01CS02CS03
Consultant toolsCS20CEWB
Customizing and mass-maintenance tools for each object are in the Consultant view.
How
Routing (master recipe in PP-PI)
The sequence of operations that makes the product, each at a work center with standard values such as setup and machine time. The production order copies it as its operations. Process industries use the master recipe, with phases.
Example: 0010 Mix syrup, 0020 Fill and seal, 0030 Pack
Why CO cares
Standard values times activity prices give the conversion costs in the cost estimate, and the target costs every order is measured against.
Maintain inCA01CA02CA03
Consultant toolsCA85C201
Customizing and mass-maintenance tools for each object are in the Consultant view.
Where
Work center (resource in PP-PI)
A machine, line or group of people where operations run. It holds the available capacity, the formulas for scheduling and costing, and the link to a cost center. In process industries the resource plays the same role.
Example: LINE01, filling line 1
Why CO cares
Each work center is assigned to a cost center and activity types, so confirmed hours become activity allocations priced at the cost center’s planned rate.
Maintain inCR01CR02CR03
Consultant toolsCR06CRC1
Customizing and mass-maintenance tools for each object are in the Consultant view.
The key in SAP S/4HANA
Production version
Ties one BOM alternative to one routing or recipe, with a validity period and a lot-size range. In SAP S/4HANA it is mandatory: it is the only valid source of supply for a manufactured material, so without one, MRP and the production order find no BOM and routing.
Example: Version 0001: BOM alternative 1 with routing group 50000123, from 1 to 99,999 packs
Why CO cares
When several versions are valid, an order created without a planned order takes the alphanumerically first, unless a quota arrangement says otherwise. Keep the version costing uses aligned with the one production uses, or the variances will show the difference.
Maintain inC223MM02
Consultant toolsCS_BOM_PRODVER_MIGRATION02
Customizing and mass-maintenance tools for each object are in the Consultant view.
Sources: SAP Learning, master data selection for production orders; SAP blogs on MRP changes in SAP S/4HANA and on production versions; Guru99, production versions; LeanX, material master fields.
The PP process
Follow one production order from the forecast to the variance
Nine steps of make-to-stock production with a production order. The first three only plan; from the goods issue on, every step posts. Pick a step to see what happens, where you see it, what it posts in the books and, in the Consultant view, what sits under the hood.
Step 1 of 9 · What happens
Demand arrives: forecast and sales orders
Production starts from demand. Planned independent requirements carry the forecast or sales plan, and sales orders arrive from SD. The planning strategy of the material decides how the two meet: whether sales orders consume the forecast or drive production on their own.
Who: Demand planner, sales
Where you see it
Planned independent requirements in MD61 to MD63; sales orders appear as demand in MD04.
MD61MD04
Under the hood
The strategy group in the MRP 3 view (field STRGR) picks the planning strategy, and each strategy pairs requirements types. Strategy 10 uses LSF for the forecast and KSL for sales orders, so orders do not reduce the forecast; strategy 40 uses VSF and KSV, so they consume it.
STRGRLSFKSLVSFKSV
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: Nothing posts. A forecast and a sales order are plans and commitments, not accounting events.
Sources: SAP Help, planning strategy assignments; SAP PRESS, make-to-stock strategies.
Step 2 of 9 · What happens
MRP works out what is missing
MRP compares demand with stock and fixed receipts, keeps the safety stock aside and plans only where something is missing. For each shortage it creates a planned order if the material is made in-house, or a purchase requisition if it is bought, as the procurement type says. It then explodes the BOM of each planned order, so the components get dependent requirements, and plans them too, level by level.
Who: MRP controller, or a nightly job
Where you see it
Run MRP Live in MD01N or classic MRP in MD01 to MD03; check the result in MD04 or the Monitor Material Coverage app.
MD01NMD04
Under the hood
In SAP S/4HANA the materials to plan come from the planning file, table PPH_DBVM. The MRP type (DISMM) and lot size (DISLS) drive the logic. MRP Live does not call classic MRP BAdIs and ignores the creation indicators, creating purchase requisitions for bought materials; MD_MRP_FORCE_CLASSIC sends chosen materials to the classic logic.
PPH_DBVMDISMMDISLSMD_MRP_FORCE_CLASSIC
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: Nothing posts. Planned orders, purchase requisitions and dependent requirements are proposals that the next run may still change.
Sources: SAP Learning, understanding MRP; SAP PRESS, MRP Live and classic MRP; SAP blog, planning file and MRP Live.
Step 3 of 9 · What happens
The planner works the exceptions
MRP does not ask questions; it leaves exception messages. Start dates in the past, firmed receipts that should come earlier or later, receipts no longer needed: each one asks the planner to act. And MRP plans with infinite capacity, so a plan can be complete on materials and impossible on machines.
Who: MRP controller
Where you see it
Exception messages in MD04 for one material or MD07 for many; capacity load with the capacity apps or capacity planning.
MD04MD07
Under the hood
The rescheduling messages 10, 15, 20 and 30 belong to exception group 7 in the standard system. The rescheduling horizon decides when MRP proposes a new date and when it proposes cancelling. For finite capacity, SAP points to PP/DS, embedded in SAP S/4HANA since release 1610.
MD07CM25PP/DS
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: Nothing posts. Exception messages and capacity checks are planning information.
Sources: SAP Help, rescheduling check and exception messages; SAP Community, exception messages 10, 20 and 30; SAP blog, capacity requirements planning.
Step 4 of 9 · What happens
The planned order becomes a production order
When the plan is firm, the planned order is converted. The production order copies the BOM as its component list and the routing as its operations, schedules each operation and calculates planned costs. It starts with status CRTD, created, and takes no costs until it is released. Later MRP runs no longer change it.
Who: Production scheduler
Where you see it
Convert one order in CO40 or many in CO41, or straight from MD04; create an order without a planned order in CO01.
CO40CO41CO01
Under the hood
The production version decides which BOM and routing are copied: the one whose validity and lot-size range fit, the alphanumerically first if several fit. The settlement rule is assigned automatically at creation from the order type’s distribution rule, normally PP1, which settles 100% to the manufactured material.
C223OPJHOPL8
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: No journal entry. The planned costs are plan values in Controlling, to compare later with the actual costs.
Sources: SAP Learning, production order from a planned order and master data selection.
Step 5 of 9 · What happens
The order is released
Release means production may start. SAP checks that the components are available, the order gets status REL and shop papers such as the picking list can be printed. From now on, goods movements and confirmations can post to the order.
Who: Production scheduler or supervisor
Where you see it
Release one order in CO02 or many in CO05N or COHV; the Manage Production Orders app flags missing components before production starts.
CO05NCOHV
Under the hood
Checking control (OPJK) sets which availability check runs for each order type and how missing parts are treated. Missing parts are listed in CO24.
OPJKCO24
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: Nothing posts yet, but the order is now open for costs.
Sources: SAP Help, system status for orders and checking control; SAP Learning, managing shop floor orders.
Step 6 of 9 · What happens
The components go to the line
The components leave stock against the order. They can be issued by hand before or during production, or backflushed: posted automatically when the operation that uses them is confirmed, which is common for cheap, high-volume parts.
Who: Warehouse, or automatic backflush
Where you see it
Goods issue in MIGO with movement type 261; picking list in CO27; backflushed components post from CO11N.
MIGO261CO27
Under the hood
The backflush indicator (RGEKZ) in the material master says always backflush (1) or lets the work center decide (2); it can also sit on the order’s component. A failed backflush does not stop the confirmation: the movement waits in COGI, table AFFW.
RGEKZCOGIAFFW
Customizing, tables and the settings behind this step are in the Consultant view.
FI postingIn the books: Component stock goes down at its valuation price and the same amount is debited to the order as consumption: the first actual cost on the order.
Sources: Guru99, goods movements for production orders; SAP Help, planned withdrawal; LeanX, table MARC; SAP blog, common COGI errors.
Step 7 of 9 · What happens
The work is confirmed
A confirmation records what really happened: good quantity, scrap, machine and labor time, and whether the operation is finished. The order moves to partially confirmed (PCNF), then confirmed (CNF), and the remaining capacity load goes down. Depending on settings, the same confirmation backflushes components and posts the goods receipt.
Who: Shop floor operator or supervisor
Where you see it
Confirm an operation in CO11N or the whole order in one step in CO15; fix failed goods movements in COGI.
CO11NCO15COGI
Under the hood
Confirmation parameters per order type are in OPK4. The control key decides whether an operation is confirmed and whether it posts an automatic goods receipt; SAP’s process order documentation recommends that on one phase only, usually the last.
OPK4OPJ8
Customizing, tables and the settings behind this step are in the Consultant view.
FI postingIn the books: Confirmed times, priced at the activity rates of the work center’s cost center, are debited to the order and credited to the cost center: an activity allocation.
Sources: SAP Help, confirming a production order and goods movements with confirmations; SAP Community, CO15 and CO11N.
Step 8 of 9 · What happens
The finished goods go into stock
The goods receipt puts the finished product into stock. When the whole quantity is in, the order gets status DLV, delivered. By-products and co-products are received too, with their own movement type.
Who: Warehouse, or automatic at the last confirmation
Where you see it
MIGO with movement type 101, or automatic at the last confirmation; by-products with 531.
MIGO101531
Under the hood
A material at standard price is received at that price, whatever the order really cost. That gap is what period-end processing turns into a variance.
CK11NBSX
Customizing, tables and the settings behind this step are in the Consultant view.
FI postingIn the books: Finished goods inventory is debited at the standard price and the order is credited with the same amount.
Sources: Guru99, goods movements for production orders; SAP Learning, settlement of a delivered order.
Step 9 of 9 · What happens
Period end: WIP, variance, settlement
At month-end Controlling goes through every order. Orders still in production have their balance valued as work in process (WIP). Orders delivered or technically completed get a variance instead: actual costs against target costs for the quantity delivered. Settlement then empties the order, and it can be technically completed and closed.
Who: Cost accountant
Where you see it
WIP in KKAO, variances in KKS1 or KKS2, settlement in CO88 or KO88; KKBC_ORD to analyze one order.
KKAOKKS1CO88
Under the hood
WIP is calculated each period until the order is DLV or TECO; then it is cancelled and the variance calculated. Variances split into categories such as input quantity, resource-usage and lot size. The price difference account comes from automatic account determination (OMWB, key PRD).
KKS2KO88OMWB
Customizing, tables and the settings behind this step are in the Consultant view.
FI postingIn the books: Settlement credits the order with its remaining balance and debits a price difference account; with the Material Ledger, the difference stays with the material for actual costing.
Sources: SAP Community, period-end activities, WIP and variance; SAP Help, variance categories and production order settlement; SAP Learning, performing settlement.
The four statuses FI and CO watch
A production order carries many system statuses, but month-end turns on four. They decide whether an order can receive costs, whether its balance is WIP or a variance, and whether it can still be posted to.
- REL · ReleasedCosts can arriveBefore release an order is only created (CRTD) and takes no costs. After release, goods movements and confirmations post to it.
- DLV · DeliveredWIP becomes a varianceUntil the full quantity is received, the order’s balance is valued as work in process. At DLV the WIP is cancelled and the variance calculated.
- TECO · Technically completedDone for logisticsOut of MRP, open reservations and capacity removed, data locked. Postings are still possible, and for costing TECO counts like DLV.
- CLSD · ClosedNothing more can postNeeds a balance of zero and no open requisitions, purchase orders or commitments. It is the controller’s signal that the order is finished.
Sources: SAP Learning, creating a production order from a planned order; SAP Help, technical completion and the closed status; SAP Community, period-end activities, WIP and variance.
Try it: MRP
Run your own MRP
MRP repeats one simple calculation: subtract demand from stock and, wherever the result falls below the safety stock, propose supply. Change the stock, the lot size or the lead time and watch the planned orders, the components they need and the exception messages change. It is the logic behind every line of MD04.
The material: FG-500
Example: opening stock 400 packs, no safety stock, lot size EX, 1 week of in-house production time.
Lot sizes: EX lot-for-lot, FX a fixed 500, HB up to a maximum stock of 800. Weeks W1 to W6; today is the start of W1. Quantities in packs. Examples only.
The result, as a stock/requirements list
| Date | MRP element | Start | Qty | Available | Exception |
|---|---|---|---|---|---|
| Today | Stock | 400 | 400 | ||
| W1 | Forecast (PIR) | −200 | 200 | ||
| W2 | Sales order | −150 | 50 | ||
| W3 | Planned orderStart W2 | W2 | +250 | 300 | |
| W3 | Forecast (PIR) | −300 | 0 | ||
| W4 | Planned orderStart W3 | W3 | +250 | 250 | |
| W4 | Forecast (PIR) | −250 | 0 | ||
| W5 | Planned orderStart W4 | W4 | +100 | 100 | |
| W5 | Sales order | −100 | 0 | ||
| W6 | Planned orderStart W5 | W5 | +350 | 350 | |
| W6 | Forecast (PIR) | −350 | 0 |
What MRP proposed
4 planned orders
Total 950 packs; stock at the end of W6: 0 packs.
No exception messages: every order can start in time.
Dependent requirements for the components
Cans, 12 per pack11,400
Cartons, 1 per pack950
MRP explodes the BOM of each planned order and plans the components next, due when each order starts. Bought components get purchase requisitions.
What MRP did not check
4.8 h
of filling-line time, at 0.5 h per 100 packs. MRP plans with infinite capacity: it assumed the line is free. Capacity planning or PP/DS has to check that.
Simplified: weekly buckets, one level shown, no rounding, no scrap. In a real system the scheduling settings decide whether a start date in the past is kept, as here, or MRP switches to forward scheduling and moves the finish date later. Sources: SAP Learning, understanding MRP (net requirements, lot sizes, scheduling); SAP Help, exception messages; SAP blog, capacity requirements planning (infinite capacity).
Try it: costs
From the production order to the journal entry
This is where PP meets the books, and the part FI and CO consultants ask about most. A production order is debited with what it consumes, credited with what it delivers at the standard price, and settled for whatever is left. Change what happened on the shop floor and watch the postings and the variance move together.
Order 1000457, 1,000 packs
Example: 1,000 good packs, components as planned, line time as planned.
Standard cost from CK11N: 2.10 per pack, of which components 1.50 and line time 0.60 (0.5 h per 100 packs at 120.00 per hour). USD, examples only.
Target against actual, as the cost analysis shows it
| Line | Target | Actual | Variance |
|---|---|---|---|
| ComponentsCans and cartons, goods issue 261 | 1,500.00 | 1,500.00 | 0.00 |
| Line time5.00 h × 120.00, confirmation | 600.00 | 600.00 | 0.00 |
| Goods receipt1,000 packs × 2.10 standard, movement 101 | −2,100.00 | −2,100.00 | 0.00 |
| BalanceWhat settlement clears | 0.00 | 0.00 | 0.00 |
Target costs are the standard cost for the quantity actually delivered. The total target is zero: a perfect order is credited exactly what it consumed.
1 · Goods issue, movement 261
Components leave stock
| Account | Debit | Credit |
|---|---|---|
| Consumption, on order 1000457GBB | 1,500.00 | |
| Raw materials inventoryBSX | 1,500.00 |
Valued at the components’ price: the first actual cost on the order.
2 · Confirmation, CO11N
Line time charged to the order
| Account | Debit | Credit |
|---|---|---|
| Activity allocation, on order 1000457Secondary cost element | 600.00 | |
| Cost center 4210, filling lineActivity credit | 600.00 |
5.00 h × 120.00, the cost center’s planned activity price.
3 · Goods receipt, movement 101
Finished packs into stock
| Account | Debit | Credit |
|---|---|---|
| Finished goods inventoryBSX | 2,100.00 | |
| Production output, credit to the orderGBB | 2,100.00 |
1,000 packs at the 2.10 standard price, whatever the order really cost.
4 · Settlement, KO88
The rest goes to price difference
| Account | Debit | Credit |
|---|---|---|
| Nothing to settleBalance 0.00 |
The order consumed exactly its standard for the quantity delivered.
The balance on the order
Debits: issue + confirmation2,100.00
Credit: goods receipt−2,100.00
Variance to settle0.00
Zero: the order matched its standard, nothing to settle.
Simplified: no overhead, no WIP (the order is delivered and complete) and all prices at standard, so the whole variance is input quantity variance. Had the lost packs been confirmed as scrap, part of it would appear as scrap variance. Which G/L accounts the keys reach depends on your account determination. Sources: SAP Help, variance categories; SAP Learning, settlement of a finally delivered production order and settlement with the price difference account from OMWB.
Quick test
Why is my production order stuck?
Eight calls every PP support team knows by heart. Guess the cause first, then open the card to see it, the fix and who acts.
- Planning
- Master data
- Availability
- Goods movements
- Status
- Costing
MRP ran, but nothing was planned for my materialShow the answer
PlanningMRP plans only where a net requirement remains after stock and fixed receipts. Check the demand, the MRP type (ND means no planning) and, in SAP S/4HANA, the planning file entry in table PPH_DBVM.
Who acts: MRP controller, PP consultant
The order can’t find a BOM or routingShow the answer
Master dataIn SAP S/4HANA the production version is the only valid source of supply. Without a version valid for that date and quantity, there is nothing to copy into the order.
Who acts: PP master data team
The order won’t releaseShow the answer
AvailabilityThe availability check found missing components. Checking control (OPJK) decides for each order type which check runs and how missing parts are treated; CO24 lists them.
Who acts: Production scheduler, purchasing
Confirmed, but the stock didn’t moveShow the answer
Goods movementsThe backflush or automatic goods receipt failed: no stock, no storage location or a closed period. The movements wait in COGI until someone corrects and posts them.
Who acts: Supervisor, warehouse
MD04 shows exception 07Show the answer
PlanningFinish date in the past: the order should already be finished. Reschedule it, or check whether it was produced and never confirmed or received.
Who acts: MRP controller, supervisor
“Current order status does not allow goods receipt”Show the answer
StatusThe order carries a status that blocks the receipt, such as the deletion flag (DLFL) or closed (CLSD). If the movement is genuine, the status is reset in CO02 and the movement posted from COGI.
Who acts: Supervisor, with the controller
The order can’t be closedShow the answer
StatusCLSD needs a balance of zero and no open purchase requisitions, purchase orders or commitments. Usually settlement is missing, or a late posting arrived after it.
Who acts: Cost accountant
A huge variance appeared at settlementShow the answer
CostingCompare target and actual in the order’s cost analysis. Typical causes: more material or time than planned, a component other than the BOM’s, or an order far from the costing lot size, which spreads setup costs differently.
Who acts: Cost accountant, production
Sources: SAP Learning, understanding MRP; SAP Help, MRP type ND, checking control, exception messages, the closed status and variance categories; SAP blogs on production versions and on common COGI errors.
Speak PP
The codes PP people use
PP people talk in codes: “it’s a PD material with EX, strategy 40, the order is still PCNF and MD04 shows a 10”. These are the standard ones you will hear in meetings and see on every screen. Your company may add its own.
Every production order carries system statuses that say what has happened and what is still allowed. FI and CO meet them at month-end, because WIP or variance depends on them.
The MRP type (DISMM) in the MRP 1 view decides how a material is planned: from demand, from a reorder point or from a forecast.
Once MRP finds a shortage, the lot size (DISLS) decides how much to produce or buy.
The strategy group (STRGR) in the MRP 3 view decides how forecast and sales orders work together.
MRP leaves a number next to every element that needs attention. The rescheduling messages 10, 15, 20 and 30 form group 7 in the standard system.
Codes you see on goods movements and in the material master around production.
CRTDCreatedThe order exists but takes no costs until it is released.RELReleasedProduction may start: availability checked, papers printed, goods movements and confirmations allowed.PCNFPartially confirmedSome work has been confirmed; production is under way.CNFConfirmedAll the planned work is confirmed; remaining capacity requirements go.PDLVPartially deliveredPart of the quantity has been received into stock.DLVDeliveredThe whole quantity is in stock. WIP is cancelled and a variance calculated.TECOTechnically completedDone for logistics: out of MRP, reservations and capacity removed. Postings still possible.CLSDClosedNo more postings. Needs a zero balance and no open requisitions, purchase orders or commitments.DLFLDeletion flagMarked for deletion and later archiving.PDMRPPlans from sales orders and planned independent requirements.VBManual reorder pointReplenishes when stock falls below a reorder point you enter.VMAutomatic reorder pointLike VB, with reorder point and safety stock calculated from history.V1Manual reorder point, external requirementsAlso counts sales orders and reservations.V2Automatic reorder point, external requirementsThe automatic version of V1.VVForecast-based planningPlans from forecast consumption; compatibility scope in SAP S/4HANA, usable until 31 December 2025.R1Time-phased planningPlans in a fixed rhythm, such as the days a supplier delivers.NDNo planningMRP ignores the material.EXLot-for-lotExactly the shortage quantity.FXFixed lot sizeThe fixed quantity from the material master, as many times as needed.HBReplenish to maximum stockEnough to bring stock back to a maximum level, such as a tank’s capacity.TBDaily lot sizeAll requirements of one day in one lot.WBWeekly lot sizeAll requirements of one week in one lot.MBMonthly lot sizeAll requirements of one month in one lot.10Net requirements planningMake-to-stock from the forecast; sales orders do not change the plan.11Gross requirements planningProduces the planned quantity regardless of stock, for continuous processes such as cement or steel.20Make-to-orderEach sales order triggers its own production.30Production by lot sizeSales orders drive production, grouped into lots; no forecast needed.40Planning with final assemblySales orders consume the forecast; planning follows whichever is higher.50Planning without final assemblyComponents are planned from the forecast; final assembly waits for the sales order.70Planning at assembly levelThe forecast sits on assemblies, not on the finished product.03New, start date in the pastA proposal from this run should already have started.06Start date in the pastAn existing order should already have started.07Finish date in the pastAn existing order should already be finished.10Bring process forwardA firmed receipt comes too late; move it earlier.15Postpone processA firmed receipt comes too early; move it later.20Cancel processNo requirement needs this receipt within the rescheduling horizon.30Plan process according to scheduleFor receipts that are not firmed; check their timing.50No BOM existsThe material is made in-house but has no BOM.96Stock below safety stockProjected stock falls under the safety stock.261Goods issue for orderComponents consumed by the production order.101Goods receipt for orderFinished product received from the order.531By-product receiptBy-product or co-product received from the order.EIn-house productionProcurement type: MRP creates planned orders.FExternal procurementProcurement type: MRP creates purchase requisitions.XBothProcurement type: the material can be made or bought.1Always backflushBackflush indicator in the material master.2Work center decidesBackflush indicator: the work center’s setting applies.
Sources: SAP Help (system status for orders, process order statuses, technical completion, the closed status, lot-sizing procedures, MRP type ND, exception messages, rescheduling check, planning strategies); SAP Learning, consumption-based planning; SAP PRESS, make-to-stock strategies; SAP Community, production order statuses and exception messages; Guru99, goods movements; LeanX, table MARC.
The CO in CO01, CO11N and COGI has nothing to do with Controlling: CO transactions belong to production orders. Controlling’s own mostly start with K, such as KS01 for cost centers, KKS2 for variances and KO88 for settlement. An FI consultant told to “check CO02” should open the production order. Source: production order transaction list
Reference
The PP transactions people actually use
PP transactions follow a pattern: MD for MRP and planned orders, CO for production orders, COR for process orders, CS for BOMs, CA for routings, CR for work centers, CM for capacity and MF for repetitive manufacturing. Start here shows the ones worth bookmarking; FI/CO bridge collects what cost accountants run at month-end; the last column says what changed in SAP S/4HANA. Type a code or a word to search all of them.
| Code or app | For | What it does | Who opens it | ECC / S/4HANA |
|---|---|---|---|---|
MD04 | User | Stock/requirements list: the live picture of stock, demand and supply for one material, with exception messages. | MRP controller, everyone | ECC + S/4HANA |
MD07 | User | Collective access of stock/requirements lists, for example everything of one MRP controller. | MRP controller | ECC + S/4HANA |
MD05 | User | MRP list: the snapshot of the last planning run. MRP Live writes none. | MRP controller | S/4HANA: compatibility scope |
MD06 | User | Collective access of MRP lists. | MRP controller | S/4HANA: compatibility scope |
MD01N | User | MRP Live: plans many materials on SAP HANA, without MRP lists. | MRP controller, background job | S/4HANA |
MD01 | User | Total planning online for a plant, classic MRP. | MRP controller | ECC + S/4HANA |
MD02 | User | Single-item, multi-level planning: one material and everything below it. | MRP controller | ECC + S/4HANA |
MD03 | User | Single-item, single-level planning. | MRP controller | ECC + S/4HANA |
MDBT | User | Total planning in background, classic MRP. | MRP controller, background job | ECC + S/4HANA |
MD61 | User | Create planned independent requirements, the forecast MRP works from; MD62 changes and MD63 displays them. | Demand planner | ECC + S/4HANA |
MD11 | User | Create a planned order by hand; MD12 changes and MD13 displays it. | MRP controller | ECC + S/4HANA |
MD16 | User | Collective access of planned orders. | MRP controller | ECC + S/4HANA |
MD14 | User | Convert a planned order into a purchase requisition; MD15 converts many. | MRP controller, buyer | ECC + S/4HANA |
MD4C | User | Order report: an order with the levels below it. | MRP controller | ECC + S/4HANA |
MD09 | User | Pegged requirements: which demand an order or proposal covers. | MRP controller | ECC + S/4HANA |
CO40 | User | Convert one planned order into a production order. | Production scheduler | ECC + S/4HANA |
CO41 | User | Collective conversion of planned orders into production orders. | Production scheduler | ECC + S/4HANA |
CO01 | User | Create a production order without a planned order; CO02 changes and CO03 displays it. | Production scheduler | ECC + S/4HANA |
CO05N | User | Release production orders collectively. | Production scheduler | ECC + S/4HANA |
COHV | User | Mass processing of production orders: release, print, complete and more for many orders. | Production scheduler | ECC + S/4HANA |
CO24 | User | Missing parts information system. | Scheduler, buyer | ECC + S/4HANA |
CO27 | User | Picking list for production orders. | Warehouse | ECC + S/4HANA |
COOIS | User | Production order information system: orders, operations, components and more in one report. | Everyone | ECC + S/4HANA |
CO46 | User | Order progress report. | Production scheduler | ECC + S/4HANA |
CO11N | User | Confirm an operation: yield, scrap and times; can backflush components and post the goods receipt. | Shop floor, supervisor | ECC + S/4HANA |
CO15 | User | Confirm the whole order at header level in one step, with the routing’s planned values. | Supervisor | ECC + S/4HANA |
COGI | User | Goods movements with errors from confirmations: correct them and post. | Supervisor, warehouse, cost accountant | ECC + S/4HANA |
MIGO | User | Goods movements: issue to the order (261), receipt from it (101), by-products (531). | Warehouse | ECC + S/4HANA |
CS03 | User | Display a BOM; CS01 creates and CS02 changes it. | Everyone | ECC + S/4HANA |
CS11 | User | Explode a BOM level by level. | Planner, engineer | ECC + S/4HANA |
CS12 | User | Explode a multi-level BOM. | Planner, engineer | ECC + S/4HANA |
CS13 | User | Summarized BOM: each component’s total quantity across levels. | Planner, engineer | ECC + S/4HANA |
CS15 | User | Where-used list: which BOMs use a component. | Planner, buyer | ECC + S/4HANA |
CA03 | User | Display a routing; CA01 creates and CA02 changes it. | Engineer, planner | ECC + S/4HANA |
CR03 | User | Display a work center; CR01 creates and CR02 changes it. | Engineer, planner | ECC + S/4HANA |
C223 | User | Maintain production versions in mass, with a consistency check. | PP key user | ECC + S/4HANA |
CM25 | User | Variable capacity leveling in the graphical planning table. | Capacity planner | S/4HANA: compatibility scope |
MF50 | User | Planning table for repetitive manufacturing. | Line planner | ECC + S/4HANA |
MFBF | User | Repetitive manufacturing backflush: goods receipt, component issue and production times in one step. | Line supervisor | ECC + S/4HANA |
MF60 | User | Pull list: missing components at the production line. | Line supervisor | ECC + S/4HANA |
COR1 | User | Create a process order (PP-PI); COR2 changes and COR3 displays it. | Process scheduler | ECC + S/4HANA |
COR6N | User | Confirm a phase of a process order. | Operator, supervisor | ECC + S/4HANA |
CO53 | User | Control recipe monitor (PP-PI). | Process supervisor | ECC + S/4HANA |
CO54 | User | Process message monitor (PP-PI). | Process supervisor | ECC + S/4HANA |
CO60 | User | Find and maintain PI sheets, the operators’ electronic instructions. | Operator | ECC + S/4HANA |
OPPQ | Consultant | MRP plant parameters, maintained in one place. | PP consultant | ECC + S/4HANA |
OPPR | Consultant | MRP groups: planning settings for a group of materials. | PP consultant | ECC + S/4HANA |
OPJH | Consultant | Order types for production orders. | PP consultant | ECC + S/4HANA |
OPL8 | Consultant | Order-type-dependent parameters per plant. | PP consultant | ECC + S/4HANA |
OPJK | Consultant | Define checking control: which availability checks run for each order type. | PP consultant | ECC + S/4HANA |
OPK4 | Consultant | Confirmation parameters for production orders. | PP consultant | ECC + S/4HANA |
OPJ8 | Consultant | Operation control keys: whether an operation is confirmed or posts an automatic goods receipt. | PP consultant | ECC + S/4HANA |
OPKP | Consultant | Production scheduling profile (shop floor control profile). | PP consultant | ECC + S/4HANA |
OX10 | Consultant | Define plants. | Consultants | ECC + S/4HANA |
MD_MRP_FORCE_CLASSIC | Consultant | Force chosen materials to the classic MRP logic inside an MRP Live run. | PP consultant | S/4HANA |
CS_BOM_PRODVER_MIGRATION02 | Consultant | Report: creates production versions in bulk, with a simulation mode (SAP Note 2463759). | PP consultant | ECC + S/4HANA |
MRP_AREA_STORAGE_LOC_MIGRATION | Consultant | Report: converts storage location MRP into MRP areas for SAP S/4HANA. | PP consultant | Conversion to S/4HANA |
RMDMRPEXTRACT01 | Consultant | Report: extracts MRP results now that MRP Live writes no MRP lists. | PP consultant, developer | S/4HANA |
CEWB | Consultant | Engineering workbench: BOMs and routings together. | PP consultant, engineer | ECC + S/4HANA |
CA85 | Consultant | Replace a work center in many routings at once. | PP consultant | ECC + S/4HANA |
CS20 | Consultant | Mass change of BOMs. | PP consultant | ECC + S/4HANA |
CRC1 | Consultant | Create a resource, the PP-PI counterpart of the work center. | PP-PI consultant | ECC + S/4HANA |
C201 | Consultant | Create a master recipe (PP-PI); C202 changes it. | PP-PI consultant | ECC + S/4HANA |
CK11N | FI/CO bridge | Create a standard cost estimate: the price every goods receipt from production is valued at. | Cost accountant | ECC + S/4HANA |
CK40N | FI/CO bridge | Costing run: cost estimates for many materials, marked and released. | Cost accountant | ECC + S/4HANA |
KKBC_ORD | FI/CO bridge | Analyze an order’s costs: target, actual and variance. | Cost accountant | ECC + S/4HANA |
CO43 | FI/CO bridge | Overhead calculation for many orders; CO42 for one. | Cost accountant | ECC + S/4HANA |
KKAO | FI/CO bridge | WIP calculation for many orders. | Cost accountant | ECC + S/4HANA |
KKS1 | FI/CO bridge | Variance calculation for many orders; KKS2 for one. | Cost accountant | ECC + S/4HANA |
CO88 | FI/CO bridge | Settlement of many orders; KO88 for one. | Cost accountant | ECC + S/4HANA |
KP26 | FI/CO bridge | Plan activity prices: the rates confirmations charge to the order. | Cost accountant | ECC + S/4HANA |
CR06 | FI/CO bridge | Cost center assignments of work centers. | PP and CO consultants | ECC + S/4HANA |
KKF6N | FI/CO bridge | Product cost collector for repetitive manufacturing. | Cost accountant | ECC + S/4HANA |
KKS6 | FI/CO bridge | Variance calculation for product cost collectors. | Cost accountant | ECC + S/4HANA |
KK87 | FI/CO bridge | Settlement of product cost collectors. | Cost accountant | ECC + S/4HANA |
OMWB | FI/CO bridge | Account determination for automatic postings, including the price difference account (PRD) used at settlement. | FI/CO consultant | ECC + S/4HANA |
| Monitor Material Coverage | Fiori app | Shortages across many materials, with a quick MRP run and links to act. | MRP controller | S/4HANA |
| Manage Production Orders | Fiori app | Orders in your area, flagging missing components, holds and out-of-range inspection results. | Production supervisor | S/4HANA |
| Manage Production Operations | Fiori app | Operation progress and the causes of delays; put orders or operations on hold. | Production supervisor | S/4HANA |
| Manage Work Center Capacity | Fiori app | Load and utilization per work center; shows overloads but does not level them. | Capacity planner | S/4HANA |
| Capacity Scheduling Board | Fiori app | Drag-and-drop scheduling; leveling and sequencing need PP/DS. | Capacity planner | S/4HANA |
| Process pMRP Simulations | Fiori app | Predictive MRP: simulate demand against capacity, then release the result as planned independent requirements. | Master planner | S/4HANA |
| Buffer Positioning | Fiori app | DDMRP: choose which materials to buffer while seeing the product structure. | Planner | S/4HANA 1809 |
| Mass Maintenance of Products (DD) | Fiori app | DDMRP: set a DDMRP MRP type on many materials at once. | Planner | S/4HANA 1709 |
PLAF | Table | Planned orders. | Consultants | ECC + S/4HANA |
AUFK | Table | Order master data, for internal orders too. | Consultants | ECC + S/4HANA |
AFKO | Table | Order header data for PP orders. | Consultants | ECC + S/4HANA |
AFPO | Table | Order items. | Consultants | ECC + S/4HANA |
AFVC | Table | Operations of an order; AFVV holds their quantities, dates and values. | Consultants | ECC + S/4HANA |
RESB | Table | Reservations and dependent requirements: the components of orders. | Consultants | ECC + S/4HANA |
AFRU | Table | Order confirmations. | Consultants | ECC + S/4HANA |
AFFW | Table | Goods movements with errors, the ones COGI shows. | Consultants | ECC + S/4HANA |
MKAL | Table | Production versions of a material. | Consultants | ECC + S/4HANA |
STKO / STPO | Table | BOM header and items; MAST links material and BOM. | Consultants | ECC + S/4HANA |
PLKO / PLPO | Table | Routing header and operations. | Consultants | ECC + S/4HANA |
CRHD | Table | Work center header. | Consultants | ECC + S/4HANA |
PBIM / PBED | Table | Planned independent requirements. | Consultants | ECC + S/4HANA |
MDKP / MDTB | Table | MRP list header and items, not updated by MRP Live. | Consultants | S/4HANA: compatibility scope |
PPH_DBVM | Table | Planning file in SAP S/4HANA, without the low-level code. | Consultants | S/4HANA |
Nothing matches. Try another word, or pick All.
Standard codes, cross-checked with SAP Help (MRP transaction list, settlement), the SAPSTACK and TutorialKart PP lists, SAP Datasheet, ERPlingo, TestingBrain and SAP blogs; S/4HANA changes from SAP PRESS, SAP blogs and SAP Learning; Fiori app names from SAP Learning and SAP blogs. Projects can hide transactions or rename apps, so check your own system before you write them into a manual.
ECC to S/4HANA
What changed in PP with SAP S/4HANA
The production order works the way it did in SAP ECC. What changed is mostly planning: the MRP engine, the master data it insists on, the old transactions with an expiry date and the new planning methods around it. If your company is moving from ECC, these are the cards to read.
The MRP engine
ECCClassic MRP in MD01, MD02, MD03 and MDBT.
S/4HANAMRP Live in MD01N, built for SAP HANA.
The classic transactions are still available and supported. MRP Live is faster for large volumes; for a few simple materials classic MRP can still win, and some companies mix the two.
Source: SAP PRESS, MRP Live and classic MRPMRP lists
ECCMD05 and MD06 show the snapshot each run writes to tables MDKP and MDTB.
S/4HANAMRP Live writes no MRP lists; MD04 is the tool.
Custom reports built on MDKP and MDTB stop updating. SAP suggests function module MD_MDPSX_READ_API or report RMDMRPEXTRACT01 instead.
Source: SAP PRESS, MRP Live and classic MRPCustom logic in MRP
ECCClassic MRP BAdIs in ABAP.
S/4HANAMRP Live calls AMDP BAdIs instead.
Logic in classic BAdIs is ignored by MRP Live until it is moved. MD_MRP_FORCE_CLASSIC can send specific materials to the classic logic, at the cost of speed.
Source: SAP PRESS, MRP Live and classic MRPStorage location MRP
ECCStorage locations can be excluded from MRP or planned separately.
S/4HANAPlanning only at plant and MRP area level; MRP areas are active by default.
Report MRP_AREA_STORAGE_LOC_MIGRATION converts storage location MRP into MRP areas during the move, after the pre-checks.
Source: SAP blog, storage location MRP (2016)Production versions
ECCOptional; BOM and routing could be selected in other ways.
S/4HANAMandatory: the only valid source of supply for a manufactured material.
Report CS_BOM_PRODVER_MIGRATION02 (SAP Note 2463759) creates them in bulk, for example only for materials that were actually produced.
Source: SAP blog, production versions for SAP S/4HANA (2020)Sources of supply
ECCSource lists and different rules for purchasing and production.
S/4HANAA smaller, symmetrical set of sources; no source list entry required.
With several valid sources and no quota arrangement, priority goes to production versions, then delivery schedules, contracts and purchasing info records.
Source: SAP blog, ECC vs SAP S/4HANA MRP changes (2018)The planning file
ECCPlanning file tables such as MDVM, with the low-level code.
S/4HANANew table PPH_DBVM, without the low-level code.
The low-level code is read from the material master during the run, so the old synchronization is no longer needed.
Source: SAP blog, planning file and MRP LiveForecast-based planning
ECCMRP type VV.
S/4HANAVV was compatibility scope, usable until 31 December 2025.
SAP recommends MRP type PD or the types P1 to P4 instead.
Source: SAP Learning, consumption-based planningCapacity leveling
ECCGraphical planning table, CM25.
S/4HANACM25 was compatibility scope, with on-premise use rights until 31 December 2025.
Fiori apps such as Manage Work Center Capacity show overloads; leveling, sequencing and rescheduling need PP/DS. MRP lists (MD05) were in the same compatibility scope.
Source: SAPinsider, compatibility scope for SCM itemsDetailed scheduling
ECCPP/DS lived in SAP APO, a separate system.
S/4HANAPP/DS embedded in SAP S/4HANA since release 1610.
PP/DS plans with finite capacity and exact times in hours and minutes; less critical materials are usually left to MRP Live.
Source: SAP blog, PP/DS in SAP S/4HANA 1610 (2017)New planning methods
ECCMRP and reorder point planning.
S/4HANAAdds demand-driven MRP (from 1709) and predictive MRP (pMRP).
DDMRP buffers chosen materials, with the Buffer Positioning app from 1809; pMRP simulates demand against capacity before it reaches MRP.
Source: SAP blog, DDMRP buffer positioning in 1809The planner’s screen
ECCMD04, MD07, CO02 and COOIS in SAP GUI.
S/4HANAFiori apps: Monitor Material Coverage, Manage Production Orders, Manage Production Operations.
The apps flag missing components, holds and delays. MD04 and MD07 are still needed for detailed analysis and for managing exception messages.
Source: SAP Learning, managing shop floor orders
Brazil
PP in Brazil: production is also a tax report
Elsewhere, a production order is an internal document. In Brazil, what it records, the quantity produced and the components consumed, ends up in a digital tax book, subcontracting moves goods under notas fiscais, and the 2027 stage of the tax reform changes the taxes on what a factory sells.
- Bloco K
Production in the SPED file
Block K of the EFD ICMS/IPI is the digital book of production and stock control. Register K230 reports the items produced, by production order, and K235 the components actually consumed: the same facts a production order records. K200 reports the stock.
Source: SEFAZ Paraná, EFD Block K - Industrialização
Subcontracting travels with notas fiscais
Sending components to a subcontractor is industrialização por encomenda. The components leave with a nota fiscal of remessa (CFOP 5901), the subcontractor returns the material used with 5902, which carries no taxes, and bills the service with 5124, the one that is taxed.
Source: Contábeis forum, CFOP 5901, 5902 and 5124 - Tax reform 2027
IPI fades, Imposto Seletivo arrives
From January 2027 IPI goes to zero for most products, with an exception tied to the Manaus Free Trade Zone. The Imposto Seletivo starts the same month: Provisional Measure 1,399/2026, published on 4 November 2026, sets 2027 rates such as 4.2% for malt beer and 2.6% for sugary drinks.
Source: Mercado & Consumo, Imposto Seletivo rates for 2027
Documented, but little known
18 tips for users and consultants
Each tip comes from SAP Help, SAP Learning, an SAP blog or a published source, linked under the tip.
- 01Users
MD04 is live, MD05 was a photo
The stock/requirements list shows every change as it happens; the MRP list shows the result of the last run and ignores what changed since. When the two disagree, trust MD04.
MD04MD05
- 02Users
Work the reschedule messages in order
One published approach reviews bring-forward (10) first, then cancel (20), then postpone (15), so the receipts that are too late get attention before the ones that are too early.
MD07
- 03Users
CO15 confirms the whole order in one stroke
CO11N confirms operation by operation, each with its own yield and scrap. CO15 confirms at header level, using the routing’s planned values for every operation: quick, but the detail is lost.
CO11NCO15
- 04Users
Check the goods movements before you leave
In CO11N the Goods Movements button shows whether the backflush and goods receipt posted or failed. Failed ones wait in COGI until someone fixes them.
CO11NCOGI
- 05Users
See the structure behind one order
MD4C, the order report, shows an order with the levels below it; MD09 shows which requirements an order or proposal is pegged to.
MD4CMD09
- 06Users
Use TECO when an order stops early
Technical completion takes the order out of MRP and removes open reservations, capacity requirements and requisitions, but postings remain possible, such as a forgotten goods issue. It can be revoked.
CO02COHV
- 07Consultants
Force one material to classic MRP
If a material needs logic MRP Live does not support, MD_MRP_FORCE_CLASSIC plans it with the classic logic inside the same MD01N run. Force too many and the speed gain is gone.
MD_MRP_FORCE_CLASSICMD01N
- 08Consultants
Create production versions where they matter
Report CS_BOM_PRODVER_MIGRATION02 creates production versions in bulk and has a simulation mode. The criterion based on production orders limits it to materials actually produced.
CS_BOM_PRODVER_MIGRATION02
- 09Consultants
Replace reports built on MRP lists
MRP Live no longer updates MDKP, MDTB and MDTC. SAP points to function module MD_MDPSX_READ_API or report RMDMRPEXTRACT01 for the same data.
RMDMRPEXTRACT01
- 10Consultants
Run the C223 consistency check
C223 maintains production versions in mass and checks version, BOM and routing against each other; MM02 opens the same screen one material at a time.
C223MM02
- 11Consultants
One automatic goods receipt per order
The control key decides whether an operation or phase posts an automatic goods receipt. SAP’s process order documentation recommends it on one phase only, usually the last.
OPJ8
- 12Consultants
Backflush: material master or work center
The backflush indicator in the material master can say always backflush (1) or leave the decision to the work center (2).
MM02
- 13FI/CO
No variance before DLV or TECO
An order in production has its balance valued as WIP each period. Once it is delivered or technically completed, the WIP is cancelled and the variance calculated. A missing DLV keeps a finished order in WIP.
KKAOKKS1
- 14FI/CO
Empty COGI before you close
A failed backflush or goods receipt means a cost or a credit missing on the order, so WIP and variances are wrong. Typical errors: stock deficits, an empty storage location, a closed posting period.
COGI
- 15FI/CO
Know the variance categories
Input side: price, resource-usage, input quantity, remaining input and scrap. Output side: output price, mixed-price and lot size, which comes from setup costs spread over a different quantity.
KKS2KKBC_ORD
- 16FI/CO
In the public cloud, one account for variances
In SAP S/4HANA Cloud Public Edition, variance journal entries post to a single G/L account; the categories are told apart by line item types.
Source: SAP Learning, settlement of a delivered order - 17FI/CO
Where the variance lands
Settlement to a material posts the difference to the price difference account found through automatic account determination, transaction OMWB with key PRD.
OMWBKO88
- 18FI/CO
Beware the rush to TECO
Setting TECO to clear old orders hides missing confirmations and receipts. MRP, ATP and capacity planning for later orders suffer, and plan-versus-actual reports lose their meaning.
CO02
Myths
Things people get wrong about PP
Myth
MRP checks whether my machines have capacity.FactMRP plans with infinite capacity. It works out quantities and dates and assumes the line is free; capacity evaluation and leveling, or PP/DS, have to check.
Myth
MD04 shows the result of the last MRP run.FactThat is MD05, the MRP list. MD04 is live and shows every change since the last run, which is why the two can disagree.
Myth
TECO closes the order.FactTECO ends it for logistics only. Goods movements and confirmations can still post, and the order still needs settlement. Only CLSD blocks postings.
Myth
Planned orders already hit the books.FactPlanned orders, purchase requisitions and dependent requirements are proposals. The first journal entry comes with the first goods movement on a released order.
Myth
Production versions are optional.FactOptional in ECC, mandatory in SAP S/4HANA, where they are the only valid source of supply for a manufactured material.
Myth
MRP Live is just classic MRP, faster.FactIt writes no MRP lists, ignores classic MRP BAdIs and the creation indicators. For a few simple materials, classic MRP can even be faster.
Myth
A process order is a production order with another name.FactProcess orders use master recipes, resources and phases, control recipes and PI sheets for the operators, and process messages that post the goods movements.
Myth
The production order costs the standard cost.FactThe standard comes from the cost estimate. The order collects actual costs, the goods receipt credits it at standard, and the difference is the variance settled at month-end.
Evolution
From R/2’s materials module to MRP on HANA
Production planning was inside SAP’s materials management from the start, and its field names still carry the German of those years. Gold dots mark the SAP S/4HANA era.
- 1975RMSAP’s materials management program, RM, appears, before R/2.
- 1979SAP R/2SAP R/2 launches. Its RM module covers purchasing, inventory, production planning and quality.
- 1992SAP R/3SAP R/3 launches. In R/3, PP covers discrete, process (PP-PI) and repetitive (REM) manufacturing.
- On HANAMRP LiveMRP Live, transaction MD01N, first runs on SAP Business Suite on HANA.
- 2015SAP S/4HANASAP S/4HANA launches. Its MRP runs as MRP Live, and production versions are mandatory.
- 2016Release 1610PP/DS, the detailed scheduling that used to live in SAP APO, is embedded in SAP S/4HANA.
- 2017Release 1709Demand-driven MRP (DDMRP) arrives.
- 2018Release 1809The Buffer Positioning app is added for DDMRP.
- 2025Compatibility scopeOn 31 December, use rights end for CM25, MRP lists and forecast-based planning (VV).
The MRP fields behind the screens
| MARC | Field |
|---|---|
| DISMM | MRP type |
| DISPO | MRP controller |
| DISLS | Lot size |
| BESKZ | Procurement type |
| EISBE | Safety stock |
| DZEIT | In-house production time |
| STRGR | Planning strategy group |
| RGEKZ | Backflush indicator |
| FEVOR | Production supervisor |
Plant-level material data, table MARC. Source: LeanX, table MARC.
Where an order lives
| Table | Holds |
|---|---|
| AUFK | Order master data |
| AFKO | PP order header |
| AFPO | Order item |
| AFVC | Operations |
| RESB | Components (reservations) |
| AFRU | Confirmations |
Sources: SAP Community, key PP tables by subfunction; LeanX, table AUFK.
Sources: Wikipedia (SAP R/2, SAP R/3, SAP S/4HANA); SAP blogs on the planning file, PP/DS in 1610 and DDMRP in 1809; SAP PRESS, MRP Live; SAPinsider, compatibility scope; SAP Learning, consumption-based planning.
The questions people ask most
What is the difference between a planned order and a production order?
A planned order is a proposal from MRP: it can be changed, rescheduled or deleted, and the next MRP run may do so itself. A production order is the instruction to produce. Once converted, later planning runs no longer change it; it gets components and operations, and it collects real costs.
Production order, process order or repetitive manufacturing: which one?
Production orders suit discrete products made in lots with routings. Process orders, in PP-PI, use master recipes, resources and phases, with control recipes and PI sheets for the operators, and suit process industries. Repetitive manufacturing has no orders: run schedules, a planning table and backflushing, with costs collected per period on a product cost collector.
Why did MRP create a purchase requisition and not a planned order?
The procurement type in the material master decides: E means in-house production, so planned orders; F means external procurement, so purchase requisitions; X allows both.
What is the difference between MD04 and MD05?
MD04, the stock/requirements list, shows the current situation, including every change since the last MRP run. MD05, the MRP list, shows the result of the last run and ignores later changes. MRP Live in SAP S/4HANA writes no MRP lists, so MD04 is the tool there.
Do I have to use MRP Live in SAP S/4HANA?
No. The classic MRP transactions are still available and supported. MRP Live, MD01N, is built for large volumes on SAP HANA; classic MRP can still be faster for a few simple materials, and some companies mix the two. Watch custom logic: MRP Live does not call classic MRP BAdIs.
What is a production version, and why does SAP S/4HANA insist on it?
It ties one BOM alternative to one routing or recipe, with a validity period and a lot-size range. In SAP S/4HANA production versions are mandatory: they are the only valid source of supply for a manufactured material, so without one, MRP and the production order find no BOM and routing.
What is backflushing?
An automatic goods issue: components are posted when the operation that uses them is confirmed, instead of being issued by hand. The backflush indicator sits in the material master, where 1 means always and 2 lets the work center decide, or on the component itself.
What do TECO and CLSD mean?
TECO, technically completed, ends an order for logistics: it leaves MRP, its open reservations and capacity requirements go and its data is locked, but postings are still possible. CLSD, closed, ends it for good: no more postings, and only with a zero balance and no open purchase requisitions, purchase orders or commitments.
Why does my production order have a variance?
Because actual costs differ from target costs, the standard cost of the quantity delivered. SAP splits the difference into categories: on the input side price, resource-usage, input quantity, remaining input and scrap; on the output side output price, mixed-price and lot size.
What is WIP, and when does it go away?
Work in process is the value of an order still in production: its debits not yet balanced by goods receipts. It is calculated each period until the order is delivered (DLV) or technically completed (TECO); then the WIP is cancelled and a variance calculated instead.
Does MRP consider machine capacity?
No. Classic MRP and MRP Live plan with infinite capacity: they look at quantities and dates, not at whether the line is free. Capacity evaluation and leveling come after MRP, or PP/DS plans with finite capacity from the start.
What is COGI, and why should FI care?
COGI lists goods movements that failed during confirmations, such as a backflush with no stock or a posting into a closed period. Until they are fixed, costs or credits are missing on the order and stock is wrong, so WIP, variances and inventory values are wrong too. Empty it before closing.
What is the difference between CO11N and CO15?
CO11N confirms one operation at a time, with its own yield and scrap. CO15 confirms the whole order at header level in one step, using the planned values of the routing for all operations.
Is CM25 still available in SAP S/4HANA?
CM25 and the graphical capacity planning table were in SAP S/4HANA’s compatibility scope, whose on-premise use rights ended on 31 December 2025. The replacements are Fiori apps such as Manage Work Center Capacity and the Capacity Scheduling Board, with PP/DS for real leveling.
Related pages
References
Checked in November 2026. SAP knowledge base articles and SAP Notes need an SAP for Me login. Transaction lists from partner sites can lag behind your release; check names in your own system.
- Understanding MRP in SAP S/4HANAlearning.sap.com
- Analyzing master data selectionlearning.sap.com
- Creating a production order from a planned orderlearning.sap.com
- Managing shop floor orderslearning.sap.com
- Consumption-based planning: key questionslearning.sap.com
- Settlement of a finally delivered production orderlearning.sap.com
- Performing settlementlearning.sap.com
- Advanced planning: PP/DS in SAP S/4HANAlearning.sap.com
- Comparing MRP list and stock/requirements listhelp.sap.com
- Exception messageshelp.sap.com
- Rescheduling checkhelp.sap.com
- Technical completionhelp.sap.com
- The closed (CLSD) statushelp.sap.com
- Process order statuseshelp.sap.com
- System status for ordershelp.sap.com
- Variance categorieshelp.sap.com
- Transaction codes for MRPhelp.sap.com
- Planned withdrawal of material componentshelp.sap.com
- Goods movements and confirmationshelp.sap.com
- Confirming a production orderhelp.sap.com
- Checking the production order settlement (KO88)help.sap.com
- Make-to-stock repetitive manufacturinghelp.sap.com
- Planning strategy assignmentshelp.sap.com
- Checking controlhelp.sap.com
- Lot-sizing procedureshelp.sap.com
- Replenishment up to maximum stock levelhelp.sap.com
- MRP type ND (no planning)help.sap.com
- Differences between MRP Live and classic MRPblog.sap-press.com
- Four strategies for make-to-stock productionblog.sap-press.com
- How to create production versions for SAP S/4HANAblogs.sap.com
- SAP S/4HANA vs ECC MRP: essential changesblogs.sap.com
- Simplification item: storage location MRPblogs.sap.com
- Planning file entries and MRP Liveblogs.sap.com
- PP/DS as part of SAP S/4HANA 1610blogs.sap.com
- DDMRP buffer positioning in SAP S/4HANA 1809blogs.sap.com
- Predictive material and resource planning (pMRP)blogs.sap.com
- Common COGI errors and resolutionsblogs.sap.com
- Do you whitewash your production orders?community.sap.com
- Period-end activities, WIP and variancecommunity.sap.com
- Difference between CO15 and CO11Nanswers.sap.com
- Exception messages 30 and 10answers.sap.com
- Exception messages 20 and 10answers.sap.com
- Why capacity requirements planning mattersblogs.sap.com
- SAP PP REM steps with transaction codesblogs.sap.com
- Production planning for process industryblogs.sap.com
- MD07 and MD04 vs Monitor Material Coverageblogs.sap.com
- Key PP tables by subfunctioncommunity.sap.com
- Managing MRP exception messagesSAPinsider
- Compatibility scope for SCM itemssapinsider.org
- Retirement of CM25: Fiori apps without PP/DSmsg.group
- SAP PP transaction codessapstack.com
- Production order transaction codestutorialkart.com
- IMG activity Define Checking Control (OPJK)sapdatasheet.org
- KKBC_ORD, analyze ordertestingbrain.com
- KKS2, variances for production orderserplingo.com
- SAP table MARCleanx.eu
- SAP table AUFKleanx.eu
- How to create a production version (C223)guru99.com
- Goods movements for production ordersguru99.com
- CS15 single-level where-used listerplingo.com
- SAP PP common tablestutorialspoint.com
- SAP R/2en.wikipedia.org
- SAP R/3en.wikipedia.org
- SAP S/4HANAen.wikipedia.org
- EFD ICMS/IPI: Bloco Ksped.fazenda.pr.gov.br
- CFOP 5901, 5902 e 5124contabeis.com.br
- Alíquotas do Imposto Seletivo para 2027mercadoeconsumo.com.br
- Zeragem do IPI a partir de 2027notagateway.com.br