Discrete Make-to-Stock: Planned Order, Production Order, Goods Issue (261), Confirmation, Goods Receipt (101) and Settlement
The canonical PP cycle: a planned order from MRP becomes a production order, components are issued to it (261), the work is confirmed (CO11N), the finished product is received into stock (101), and settlement clears the order's variance.
Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.
Digital twin
01MRP proposes a planned order
Planned order 45678 proposes 100 EA of FG-2000. It is only a plan — nothing can be produced against it yet.
FG-2000
MD04 — Stock/Requirements List
- Stock
- 40 EA
- Requirements
- 140 EA
- Planned order
- +100 EA
Business scenario
MRP proposed 100 EA of FG-2000 (bracket assembly) to replenish stock. The planner converts the proposal into a production order, the line builds the assemblies from 100 EA of RM-1000, and controlling settles the order at period end.
All companies, numbers and documents are fictional demo data.
Step-by-step flow
- 01
MRP proposes a planned order open in twin
Planned order 45678 proposes 100 EA of FG-2000. It is only a plan — nothing can be produced against it yet.
A planned order belongs to planning. MRP can reschedule or delete it on the next run, so it carries no costs and cannot be executed.
- 02
Convert to a production order open in twin
The planner converts it (CO40). Production order 1000001 copies the BOM and routing and reserves 100 EA of RM-1000.
The production order is the executable object: it reserves components, schedules the work center and collects actual costs.
- 03
Release the order open in twin
The order is released (status REL). Components can now be issued and work can be confirmed.
Goods movements and confirmations are not allowed against an order that has only been created (status CRTD).
- 04
Components are needed at the line open in twin
The line is ready to build. How should the 100 EA of RM-1000 be taken out of stock?
Only then do material costs land on the order, where they can be compared with the planned cost and the value of the finished goods.
- 05
Costs on the wrong object open in twin
Issuing to a cost center expenses the components. The order shows no material cost, so it looks far cheaper than it is.
The order would later credit inventory with the full standard value of the finished goods while carrying almost no cost, producing a large false favourable variance — and the reservation stays open.
- 06
Issue components to the order (261) open in twin
RM-1000 at 1000/0002: 300 → 200 EA. ₹1,00,000 of material cost is charged to the order.
Actual material cost on the order is what variance calculation later compares with plan.
- 07
Confirm the work (CO11N) open in twin
The operator confirms 100 EA yield and 55 machine hours — 5 more than planned. ₹22,000 of activity cost is charged.
Confirmed activities move conversion cost onto the order; the yield quantity drives the expected goods receipt.
- 08
Receive the finished goods (101) open in twin
FG-2000 at 1000/0001: 40 → 140 EA, valued at standard price — ₹1,20,000 is credited to the order.
Stock of the finished good rises, and the order is credited with its standard value — the counterpart of the costs debited so far.
- 09
Settle the order open in twin
Debits ₹1,22,000 − credits ₹1,20,000 = ₹2,000 variance, settled to the material. The order balance is zero.
An order must end with a zero balance. The variance is reported, not hidden in inventory, because standard price keeps the finished good's value fixed.
- 10
Production cycle complete open in twin
Planned order → production order → 261 → confirmation → 101 → settlement. Components down 100, finished goods up 100.
This is the backbone every other PP variant changes: backflush automates the 261, repetitive manufacturing removes the order, process orders swap the routing for a recipe.
SAP documents
Stock impact
| Step | Plant / SLoc | Stock type | MvT | Change |
|---|---|---|---|---|
| Issue components to the order (261) | 1000 / 0002 | Unrestricted use | 261 | −100 EA |
| Receive the finished goods (101) | 1000 / 0001 | Unrestricted use | 101 | +100 EA |
Accounting impact
Components consumed by a production order
TypicalIssue components to the order (261)
- Dr Consumption — order 1000001 (GBB/VBR)₹1,00,000
- Cr Inventory — raw materials (BSX)₹1,00,000
Inventory is credited and a consumption account is debited with the production order as the cost object. The accounts come from automatic account determination (BSX, and GBB with modification VBR).
Internal activity allocation from the work center to the order
ConceptualConfirm the work (CO11N)
- Dr Production order 1000001 — machine hours₹22,000
- Cr Cost center CC-4300 — activity allocation₹22,000
Confirmed time is valued at the work center's activity rate. This is a controlling allocation, not a goods movement: the order is debited and the work center's cost center credited. In S/4HANA it is also recorded in the universal journal as secondary cost.
Goods receipt of finished goods from a production order
TypicalReceive the finished goods (101)
- Dr Inventory — finished goods (BSX)₹1,20,000
- Cr Factory output — order 1000001 (GBB/AUF)₹1,20,000
Finished goods are valued at their standard price. Inventory is debited and the order credited through a factory-output account (transaction key GBB, modification AUF). The accounts are configuration dependent.
Settlement of the production variance
Configuration dependentSettle the order
- Dr Price difference — production variance (PRD)₹2,000
- Cr Production order 1000001 — settlement₹2,000
With standard price control, the variance cannot change the finished good's inventory value, so settlement to the material posts it to a price-difference account (transaction key PRD) and credits the order. Overhead, variance categories, settlement profile and accounts all depend on configuration.
Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.
Movement type
Turns a planning proposal into an executable order, consumes components, records the work and receives the finished product into stock, with every cost collected on the order and settled at period end.
Transactions & Fiori apps
- MD04 — Stock/Requirements List
- CO40 — Convert Planned Order to Production Order
- CO01 — Create Production Order (without a planned order)
- CO02 — Change / Release Production Order
- MIGO — Goods Movement (261, 101)
- CO11N — Confirmation (time ticket)
- KKS2 — Variance Calculation
- KO88 — Order Settlement
- Manage Production OrdersAvailability depends on release and scope
- Confirm Production Operation
- Post Goods Movement
- Monitor Material CoverageAvailability depends on release and scope
Differences by SAP version
Production versions are optional in many configurations; the BOM and routing can be selected without one. Classic MRP (MD01/MD02) creates the planned orders.
Production versions are mandatory for BOM and routing selection. MRP Live (MD01N) is the recommended planning run, and material, activity and settlement postings land in the universal journal (ACDOCA).
Executed through Fiori apps such as Manage Production Orders and Confirm Production Operation. The underlying order, movement types 261/101 and settlement logic are the same.
Configuration
Order type (OPJH) and order-type-dependent parameters (OPL8)
Configuration dependentControl number ranges, settlement profile, costing variants and whether release is automatic.
Availability check at release (OPJK)
Configuration dependentWhether missing components block release, and which scope of check applies.
Confirmation parameters (OPK4)
Configuration dependentTolerances, whether to backflush and whether to post goods receipt automatically on confirmation.
Account determination GBB/VBR, GBB/AUF and PRD
Configuration dependentConsumption for orders, factory output on receipt and price differences at settlement.
Settlement profile and variance keys
Configuration dependentDecide where variances go and which variance categories are calculated.
Prerequisites
- Material master with MRP and work scheduling views, procurement type E (in-house)
- Bill of material and routing (or a production version linking them)
- Work center with a cost center and activity types
- Activity prices planned for the period (KP26)
- Standard cost estimate released for the finished good
- Order type and settlement profile configured for the plant
Master data
- Material master (MRP, work scheduling, costing views)
- Procurement type, lot size, production storage location and standard price.
- Bill of material
- Components and quantities copied into the order and reserved.
- Routing
- Operations, work centers and standard times copied into the order.
- Work center
- Capacity, cost center and activity types used to cost confirmations.
- Production version
- Which BOM and routing combination to use; mandatory in S/4HANA.
Organizational structure
- Company code 1000
- Plant 1000
- Storage locations 0002 (components) and 0001 (finished goods)
- Work center ASSY-01
Tables
| Table | Description |
|---|---|
| PLAF | Planned order |
| AUFK / AFKO / AFPO | Order master, header and item |
| AFVC | Order operations |
| RESB | Component reservations |
| AFRU | Confirmations |
| MATDOC | The 261 and 101 goods movements (MKPF / MSEG in ECC) |
| ACDOCA | Universal journal: material, activity and settlement postings (S/4HANA) |
Integration
- MMComponents leave inventory with 261; the finished good enters with 101. MRP reads stock and requirements from inventory management.
- COThe order is a cost object: it collects material and activity costs, is compared with plan and is settled.
- FIGoods movements post to inventory, consumption and factory-output accounts; settlement posts the variance.
- SDSales demand is one of the requirements that MRP turns into planned orders.
Common errors
“Components cannot be issued to the order”
Likely causes: Order not released; Not enough stock in the production storage location; Reservation already fully withdrawn; Component deleted from the order
Where to look: Order status · Stock overview (MMBE) for the production storage location · Order component overview
“Confirmation posts no activity cost”
Likely causes: No activity price planned for the period; Activity type not linked to the work center's cost center; Standard values missing on the operation
Where to look: KP26 activity prices · Work center costing data · Routing operation standard values
“Order cannot be settled”
Likely causes: No settlement rule; Order not delivered or technically complete; Variance calculation not run; Missing price-difference account
Where to look: Order settlement rule · Order status · KKS2 log · Account determination for PRD
“Large unexpected variance on a production order”
Likely causes: Components issued to the wrong order or to a cost center; Confirmed times far above standard; Standard cost estimate outdated; Goods receipt quantity short of what was consumed
Where to look: Order cost analysis · Material documents for the order · Confirmations · Current standard cost estimate
Troubleshooting
Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.
CHECK 1
Order cannot be created or converted
- Does the material have a valid production version?
- Is there an order type for this plant?
- Can the routing be selected for the order quantity and date?
CHECK 2
Goods movements blocked
- Is the order released?
- Is there stock in the production storage location?
- Is the posting period open?
CHECK 3
Costs look wrong
- Were all components issued against this order?
- Are activity prices maintained?
- Is the standard cost estimate current?
CHECK 4
Settlement fails
- Is there a settlement rule?
- Has variance calculation been run?
- Is the price-difference account (PRD) determined?
Interview questions
What is the difference between a planned order and a production order?
A planned order is MRP's proposal: it can be changed or deleted by the next MRP run, carries no costs and cannot be executed. A production order is the executable document: it copies the BOM and routing, reserves components, schedules capacity, collects actual costs and must be settled. Converting with CO40 or CO41 replaces the planned order with the production order.
Which postings does a production order typically receive over its life?
Debits from component issues (261) and confirmed activities, plus overhead if a costing sheet is used; a credit from the goods receipt of the finished product (101) at standard price. Whatever balance remains at period end is the variance, which settlement moves to a price-difference account (for a standard-price material) or to another receiver defined in the settlement rule.
Why does the goods receipt credit the order at standard price rather than at the actual cost?
Because the finished good is valuated at standard price. Keeping inventory at standard means the difference between what the order actually cost and the standard value stays on the order as a variance, where it can be analysed by category (quantity, price, resource-usage) and then settled.
What does order status REL change, and what does CNF mean?
REL (released) allows goods movements and confirmations against the order; before release, with status CRTD, they are not allowed. CNF means the order has been fully (finally) confirmed; PCNF is partially confirmed. DLV means fully delivered, and TECO marks it technically complete so no further logistics activity is expected.
Why must components be issued to the order and not to a cost center?
Because the order is the cost object for the product. Issuing to a cost center would charge period costs instead, leave the reservation open and make the order look cheaper than it was, distorting variances and product costs.
Quiz
References
- SAP SE — SAP Help Portal: Production Planning and Control (PP) (source)
- SAP SE — SAP Help Portal: Production Orders (source)
- SAP SE — SAP Help Portal: Order Confirmation (source)
- SAP SE — SAP Help Portal: Product Cost by Order (source)
Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.
Version history
| Version | Change |
|---|---|
| 1.0.0 | Initial version. |