# SAP PM Maintenance Order Types and Order Transactions Reference > Source: https://netray.co/tools/sap-pm-maintenance-order-types-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Searchable lookup of SAP plant maintenance order types, order transactions, order tables and system statuses. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP PM consultant - Maintenance planner - SAP functional analyst ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Code **Key:** code **Type:** text #### Kind **Key:** kind **Type:** text #### Name **Key:** name **Type:** text #### What it is and where you use it **Key:** notes **Type:** text **Rows:** #### Maintenance order **Code:** PM01 **Kind:** Order type **Notes:** Delivered order type for general corrective work. Many projects use it as the template for their own Z order types. #### Planned maintenance order **Code:** PM02 **Kind:** Order type **Notes:** Delivered order type usually assigned to orders generated from maintenance plans. #### Refurbishment order **Code:** PM03 **Kind:** Order type **Notes:** Delivered order type for refurbishing repairable spares. #### Maintenance order category **Code:** 30 **Kind:** Order category **Notes:** All PM and CS maintenance orders belong to order category 30. Order types are defined under this category. #### Customer order types **Code:** Z-types **Kind:** Order type **Notes:** Projects typically add types for breakdown, planned, shutdown, calibration or capital work so reporting and settlement differ by type. #### Maintenance order type settings **Code:** OIOA **Kind:** Config transaction **Notes:** Maintain order types and their parameters such as settlement profile, planning and status profile dependencies. #### Order number ranges **Code:** OION **Kind:** Config transaction **Notes:** Maintain number range intervals for maintenance orders. #### Settlement profile **Code:** OKO7 **Kind:** Config transaction **Notes:** Defines allowed receivers, default settlement type and the allocation structure for orders. #### Allocation structure **Code:** OKO6 **Kind:** Config transaction **Notes:** Assigns cost elements to settlement cost elements so actual costs settle correctly. #### Create maintenance order **Code:** IW31 **Kind:** Transaction **Notes:** Create an order manually, with or without a reference notification, equipment or functional location. #### Change maintenance order **Code:** IW32 **Kind:** Transaction **Notes:** Change operations, components, costs and status. Release and technical completion are done here. #### Display maintenance order **Code:** IW33 **Kind:** Transaction **Notes:** Read-only view of the order, its documents and its status history. #### Change order list **Code:** IW38 **Kind:** Transaction **Notes:** List editing with selection by plant, planner group, status or dates. Mass release and mass TECO are done from here. #### Display order list **Code:** IW39 **Kind:** Transaction **Notes:** Read-only order list for reporting and export. #### Enter time confirmation **Code:** IW41 **Kind:** Transaction **Notes:** Confirm actual work against an order by operation. #### Enter individual time confirmation **Code:** IW42 **Kind:** Transaction **Notes:** Confirm a single operation with actual work, final confirmation indicator and remaining work. #### Enter collective time confirmation **Code:** IW48 **Kind:** Transaction **Notes:** Confirm time for several operations in one screen. #### Settle individual order **Code:** KO88 **Kind:** Transaction **Notes:** Settle actual costs of one order to the receiver in its settlement rule. #### Collective order settlement **Code:** KO8G **Kind:** Transaction **Notes:** Settle many orders in one run, normally at period end. #### Order master data **Code:** AUFK **Kind:** Table **Notes:** Common master record for all order categories: order number, order type, company code, status object number. #### Maintenance order header **Code:** AFIH **Kind:** Table **Notes:** PM specific header fields such as equipment, functional location, notification and planner group. #### Order header data PP orders **Code:** AFKO **Kind:** Table **Notes:** Scheduling dates and basic data shared with production orders. #### Operation within an order **Code:** AFVC **Kind:** Table **Notes:** Operation level data such as work center, control key and short text. #### Operation quantities, dates, values **Code:** AFVV **Kind:** Table **Notes:** Planned work, duration and dates per operation. #### Order completion confirmations **Code:** AFRU **Kind:** Table **Notes:** Confirmation records with actual work and posting date. #### Reservations and dependent requirements **Code:** RESB **Kind:** Table **Notes:** Component reservations created from the order bill of material list. #### Order types **Code:** T003O **Kind:** Table **Notes:** Customizing table that holds the order type definitions. #### Created **Code:** CRTD **Kind:** System status **Notes:** Order exists but is not released. No goods issue or confirmation is allowed yet. #### Released **Code:** REL **Kind:** System status **Notes:** Order released. Goods issues, confirmations and purchase requisitions can post. #### Partially confirmed **Code:** PCNF **Kind:** System status **Notes:** At least one operation has a confirmation but not all are final. #### Confirmed **Code:** CNF **Kind:** System status **Notes:** All operations are finally confirmed. #### Technically completed **Code:** TECO **Kind:** System status **Notes:** Work finished. Settlement is still possible. Commonly the point where costs are reviewed. #### Closed **Code:** CLSD **Kind:** System status **Notes:** Order closed after settlement. No further postings. #### Deletion flag **Code:** DLFL **Kind:** System status **Notes:** Order marked for archiving and deletion. #### Settlement rule created **Code:** SETC **Kind:** System status **Notes:** The order has a valid settlement rule. **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the reference **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is the difference between PM01 and PM02? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap maintenance order types, sap pm order types, PM01 PM02 PM03 order type, sap iw31 iw32 transaction, sap maintenance order status, sap pm tables AUFK AFIH, sap order category 30, oioa order type configuration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json