SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

SAP PM Maintenance Order Types and Order Transactions Reference

Anyone configuring or supporting SAP Plant Maintenance ends up searching for the same handful of things: which order types exist, which transaction changes an order, which table holds a field. This reference puts them in one searchable list.

Download:

Code	Kind	Name	What it is and where you use it
PM01	Order type	Maintenance order	Delivered order type for general corrective work. Many projects use it as the template for their own Z order types.
PM02	Order type	Planned maintenance order	Delivered order type usually assigned to orders generated from maintenance plans.
PM03	Order type	Refurbishment order	Delivered order type for refurbishing repairable spares.
30	Order category	Maintenance order category	All PM and CS maintenance orders belong to order category 30. Order types are defined under this category.
Z-types	Order type	Customer order types	Projects typically add types for breakdown, planned, shutdown, calibration or capital work so reporting and settlement differ by type.
OIOA	Config transaction	Maintenance order type settings	Maintain order types and their parameters such as settlement profile, planning and status profile dependencies.
OION	Config transaction	Order number ranges	Maintain number range intervals for maintenance orders.
OKO7	Config transaction	Settlement profile	Defines allowed receivers, default settlement type and the allocation structure for orders.
OKO6	Config transaction	Allocation structure	Assigns cost elements to settlement cost elements so actual costs settle correctly.
IW31	Transaction	Create maintenance order	Create an order manually, with or without a reference notification, equipment or functional location.
IW32	Transaction	Change maintenance order	Change operations, components, costs and status. Release and technical completion are done here.
IW33	Transaction	Display maintenance order	Read-only view of the order, its documents and its status history.
IW38	Transaction	Change order list	List editing with selection by plant, planner group, status or dates. Mass release and mass TECO are done from here.
IW39	Transaction	Display order list	Read-only order list for reporting and export.
IW41	Transaction	Enter time confirmation	Confirm actual work against an order by operation.
IW42	Transaction	Enter individual time confirmation	Confirm a single operation with actual work, final confirmation indicator and remaining work.
IW48	Transaction	Enter collective time confirmation	Confirm time for several operations in one screen.
KO88	Transaction	Settle individual order	Settle actual costs of one order to the receiver in its settlement rule.
KO8G	Transaction	Collective order settlement	Settle many orders in one run, normally at period end.
AUFK	Table	Order master data	Common master record for all order categories: order number, order type, company code, status object number.
AFIH	Table	Maintenance order header	PM specific header fields such as equipment, functional location, notification and planner group.
AFKO	Table	Order header data PP orders	Scheduling dates and basic data shared with production orders.
AFVC	Table	Operation within an order	Operation level data such as work center, control key and short text.
AFVV	Table	Operation quantities, dates, values	Planned work, duration and dates per operation.
AFRU	Table	Order completion confirmations	Confirmation records with actual work and posting date.
RESB	Table	Reservations and dependent requirements	Component reservations created from the order bill of material list.
T003O	Table	Order types	Customizing table that holds the order type definitions.
CRTD	System status	Created	Order exists but is not released. No goods issue or confirmation is allowed yet.
REL	System status	Released	Order released. Goods issues, confirmations and purchase requisitions can post.
PCNF	System status	Partially confirmed	At least one operation has a confirmation but not all are final.
CNF	System status	Confirmed	All operations are finally confirmed.
TECO	System status	Technically completed	Work finished. Settlement is still possible. Commonly the point where costs are reviewed.
CLSD	System status	Closed	Order closed after settlement. No further postings.
DLFL	System status	Deletion flag	Order marked for archiving and deletion.
SETC	System status	Settlement rule created	The order has a valid settlement rule.

Delivered order types and exact status names vary by release and by project customizing. Confirm in OIOA and in your own system before you rely on a row.

Get a PM order backlog query for your system

Share your release and we will send a read-only query pattern for open orders by status, type and planner group. Optional, the reference above is free without it.

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

How to use the reference

Type a code, a transaction or a word into the search box and the table filters as you type. Search for settle to find the settlement transactions and profiles, or for AFIH to see what the PM header table is for. You can export the filtered rows to Excel or PDF to paste into a functional design, a test script or a support handover note. Rows are grouped by kind: order types, configuration transactions, day to day transactions, tables and system statuses. Use the Kind column to narrow the result, for example by searching Table when you are writing a query.

Order types and what they control

In SAP PM an order type is a Customizing object that sits under order category 30. It controls the number range, the settlement profile, the planning and scheduling defaults, the status profile and the authorization checks. SAP delivers PM01, PM02 and PM03 as starting points, but real projects normally define their own types so that breakdown, preventive, shutdown and capital work can be reported and settled differently. Do not overload one type with every business case. If cost reports, KPIs or approval rules differ by work class, a separate order type is the cleanest way to separate them.

Settlement profile decides the allowed receivers (cost center, asset, WBS element)
Number range separates planned and unplanned work for audit and reporting
Status profile adds user statuses such as approved or waiting for parts
Authorization groups can limit who creates or releases each type

Reading the status lifecycle

A typical order moves from CRTD to REL, then PCNF and CNF as confirmations arrive, then TECO, and finally CLSD after settlement. Costs can still post after TECO in some configurations, so many sites also use a user status to freeze the order until a planner approves. The statuses shown here are system statuses. User statuses come from the status profile on the order type and are project specific. When you debug why a goods issue or confirmation will not post, check the status first, then check the business transaction restriction on the status.

Common mistakes

The most common mistakes are copying PM01 for every use case, forgetting to assign a settlement profile so the order cannot settle, and mixing the order type with the maintenance activity type, which is a separate field used for reporting. Another is relying on table names from memory across releases. In S/4HANA the data model is mostly the same for PM, but some reporting views differ and custom code should be tested after upgrade. Always check the field in transaction SE11 in your own system before you build a report on it.

Frequently Asked Questions

What is the difference between PM01 and PM02?

Both are delivered maintenance order types. PM01 is the general maintenance order, PM02 is the planned maintenance order, typically used for orders created from maintenance plans. Your system may use different names or Z types, so check OIOA and the order type descriptions in your own client.

Which transaction creates a maintenance order in SAP?

IW31 creates a maintenance order. IW32 changes it and IW33 displays it. For mass changes use the list transaction IW38, and for creation from a notification you can use the order function inside IW22.

Where is the equipment stored on the order?

The equipment and functional location references on a maintenance order live in the PM header table AFIH, while AUFK holds the common order master fields. Join the two on the order number AUFNR when you build a query.

What is the difference between TECO and CLSD?

TECO means technically completed: the work is done and the order is flagged, but settlement and corrections are normally still possible. CLSD means the order is closed, usually after final settlement, and no more postings are expected.

If you want to query PM orders, backlogs and costs in plain language across your SAP data instead of building ALV variants, Netray can set up a read-only ERPray connection and show the generated query.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools