SAPFree referencePDF, Excel, Word exportSAP S/4HANADiscrete Manufacturing

SAP Production Order Types, Categories and Statuses Reference

This is a lookup for the codes you meet every day in SAP discrete manufacturing: order categories, order type controls, system statuses, shop floor transactions and the main order tables. Type in the search box to filter and export the list to Excel or PDF.

Download:
Code / objectKindMeaningPractical note
10
Order category
Production order (discrete PP-SFC)
Stored in AUFK-AUTYP. Most discrete manufacturing orders use this category.
40
Order category
Process order (PP-PI)
Used in process industries with master recipes instead of routings.
30
Order category
Maintenance order (PM)
Handled by plant maintenance, not shop floor control.
20
Order category
Network (PS)
Project system activities, not a PP order.
05
Order category
Product cost collector
Used with repetitive manufacturing and cost collection by period.
01
Order category
Internal order (CO)
Controlling order, no BOM or routing.
PP01
Order type
Standard delivered production order type
Most projects copy it into customer types. Check your own system for the types in use.
OPJH
Config transaction
Define order type dependent parameters (PP)
Controls status profile, settlement profile, costing variants and release behavior.
Order type
Order type control
Number range, status profile, settlement profile, cost variants, confirmation parameters
Different order types let you separate normal, rework and subcontract style orders.
CRTD
System status
Created
Order exists but is not released. No confirmations or goods issues yet.
REL
System status
Released
Shop floor can confirm and post goods movements.
PCNF
System status
Partially confirmed
At least one operation has a confirmation but not all.
CNF
System status
Confirmed
All operations are fully confirmed.
PDLV
System status
Partially delivered
Part of the order quantity received into stock.
DLV
System status
Delivered
Order quantity received. Delivery complete is set by the system or user.
GMPS
System status
Goods movement posted
Any goods movement exists on the order.
MACM
System status
Material committed
Availability check confirmed components are covered.
MSPT
System status
Material shortage
Availability check found missing components. Review in CO24.
PRT
System status
Printed
Shop papers have been printed.
SETC
System status
Settlement rule created
Required before settlement of variances.
LKD
System status
Locked
Order is locked against further processing.
TECO
System status
Technically completed
Open reservations and capacity requirements are removed. Costs still settle.
CLSD
System status
Closed
Business completion. Normally follows settlement. Can be reversed with a reset.
DLFL
System status
Deletion flag
Set for archiving. Order no longer shows in normal selections.
DLID
System status
Deletion indicator
Order is marked for deletion pending archiving.
CO01
Transaction
Create production order
Create with material, plant and order type.
CO02
Transaction
Change production order
Release, reschedule, TECO and status changes.
CO03
Transaction
Display production order
Read only view of header, operations and components.
CO40
Transaction
Convert planned orders to production orders
Works for a selection of planned orders. See the planned order conversion checklist.
CO11N
Transaction
Enter time ticket
Confirm an operation with quantities and times.
CO15
Transaction
Enter production order confirmation
Confirm an operation or whole order, with backflush as configured.
CO13
Transaction
Cancel confirmation
Reverses a posted confirmation and related goods movements.
CO24
Transaction
Missing parts info system
Lists shortages per order and component.
CO09
Transaction
Availability overview
Component availability for an order or material.
COOIS
Transaction
Order information system
List and filter orders, operations and components.
COHV
Transaction
Mass processing of production orders
Mass release, schedule, TECO and print in background.
CO88
Transaction
Collective settlement of production orders
Settles variances to the target objects.
AUFK
Table
Order master data
Common to all order categories. AUFNR is the order number.
AFKO
Table
Order header data PP orders
Scheduling dates, task list link and BOM explosion data.
AFPO
Table
Order item
Material, quantity and delivery data. Join to AFKO on AUFNR.
AFVC
Table
Operation within an order
Work center, control key and operation number.
AFVV
Table
Quantities, dates and values for the operation
Setup, machine and labor standard values.
RESB
Table
Reservation and dependent requirements
Order components. Filter by AUFNR and BDART.
AFRU
Table
Order confirmations
One row per confirmation. Reversals are flagged.
JEST
Table
Individual status per object
Join with OBJNR from AUFK to read order statuses.

Standard values shown are from the delivered SAP data model. Order types, status profiles and number ranges are customer specific, so confirm against your own configuration.

Want order status answers without running COOIS?

Optional: a short review of how an assistant over your SAP order data could answer status questions.

Optional. The tool and every export work without this. No spam.

How to use the reference

Search for a status like TECO, a transaction like CO15 or a table like AFKO. The Kind column separates categories, statuses, transactions and tables so you can narrow the list. Use it as a quick check when reading an order in CO03, writing a COOIS variant or building a report that joins AUFK, AFKO, AFPO and AFVC. Export it to hand a new planner or key user a one page cheat sheet.

  • Filter by Kind to see only statuses or only tables
  • Use the practical note to decide the next action on an order
  • Export to Excel to add your own Z order types

Order category versus order type

Order category is a technical classification fixed by SAP: 10 for production orders, 40 for process orders, 30 for maintenance orders. Order type is a four character key you define under each category. It carries the number range, status profile, settlement profile and costing parameters. Many sites run one type for normal orders and others for rework, prototype or subcontracting so costs and statuses can be reported separately.

Reading statuses correctly

System statuses are set by SAP as the order moves through its life: CRTD, REL, PCNF, CNF, DLV, TECO and CLSD. An order can hold several at once, for example REL, PCNF and GMPS. TECO is not the same as CLSD. TECO stops further planning and removes open reservations, while CLSD is the business close that normally follows variance settlement. Mixing these up is a frequent cause of open WIP at period end.

Common mistakes

Deleting an order flag instead of using TECO leaves history unclear. Releasing orders without an availability check hides shortages that CO24 would have shown. Settling before all confirmations are posted pushes variances into the wrong period.

  • Do not close orders with open goods issues
  • Check the settlement rule exists before CO88
  • Use COHV for mass TECO instead of manual change

Frequently Asked Questions

What is the difference between TECO and CLSD in SAP?

TECO means technically complete: no more goods movements or confirmations are planned, open reservations and capacity requirements are removed, but costs can still be settled. CLSD is the business close, usually set after settlement. TECO can be reversed more easily than a close.

Where do I configure production order types?

Order type dependent parameters for PP orders are maintained in the Customizing transaction OPJH, along with related settings in the production planning IMG. Order types are tied to an order category, so a production order type uses category 10.

Which tables hold production order data?

AUFK holds the common order master, AFKO the PP header with dates, AFPO the item and material, AFVC the operations and RESB the components. Join AFKO to AFPO on AUFNR, and use OBJNR from AUFK to read statuses from JEST.

Can an order have more than one system status?

Yes. System statuses are cumulative. A running order can be REL, PCNF, GMPS and MACM at the same time. Selection screens like COOIS let you include or exclude combinations to find orders that need action.

If your planners keep exporting order lists from COOIS, we can build a read only assistant over your S/4HANA data that answers questions about order status and delays, with the query visible.