- Home
- Modules
- SAP PM
SAP PM: from the breakdown to the settled order
Plant Maintenance, explained for users and for consultants from other modules.
M2 · 10004711Pump P-101 · BR-SP1-UT-PMP01DamageVibration highBreakdownYesPriority1 · Very highIW32- 0010 Replace bearing
PM01Confirmed - 0020 Laser alignment
PM02PO 4500018832 - Bearing 6205 · 2 PCIssued · 261
- Actual costs
USD 1,030.00
Overview
What PM is, if you have never worked with it
SAP PM, Plant Maintenance, is the part of SAP that keeps machines, buildings, vehicles and networks working. It records what a company has to maintain, who reported a problem, how the repair was planned, which people, spare parts and services it used and what it cost. In SAP S/4HANA, SAP’s courses call the area Asset Management, but the transactions and almost everyone on a project still say PM.
This page is for the people who work around PM without being PM consultants: maintenance planners, supervisors and technicians, and FI, CO, MM or tax consultants who meet maintenance orders at month-end. It follows one breakdown from the first report to the settled order, shows how preventive plans create work by themselves, what each step posts in the books and which transactions are worth knowing.
- SAP ECC 6
- SAP S/4HANA
- SAP S/4HANA Cloud
IW21IW31IP10Use the User | Consultant switch at the top of the page to show or hide the technical layer: Customizing, tables and the settings behind each step.
Keep assets running
PM covers the whole maintenance cycle: report, screen, plan, approve, prepare, schedule, execute, confirm and settle. SAP S/4HANA can run it as nine phases that the system sets by itself, from initiation to completion.
Source: SAP Learning, the phase modelShares its core with service
Technical objects and orders are shared with Customer Service (CS): SAP Help names the components CS-BD/PM-EQM and CS-SE/PM-WOC-MO. Maintenance (M1 to M3) and service (S1 to S3) notification types are listed side by side.
Source: SAP Help, technical objects (CS-BD/PM-EQM)Every order collects costs
A maintenance order gathers the cost of hours, spare parts and services, and settlement passes it on to a cost center, a WBS element or a fixed asset. That is why CO and FI consultants meet PM every month-end.
Source: SAP Learning, period-end closing (BF7)
Who PM talks to
A maintenance order is rarely alone. Each step reads or writes data that belongs to another module, which is why a “maintenance problem” so often ends up on an MM or CO desk.
- MMSpare parts and purchasingReservations, goods issues from stock, purchase requisitions and orders for parts and services.
- COCost centers and pricesActivity prices for hours, settlement to cost centers, period-end closing.
- FI-AAFixed assetsCapitalized work settled to an asset.
- PSProjectsLarge overhauls and investments collected on WBS elements.
- QMQualityThe same notification header table and catalog technique.
- PPProductionLines that stop when equipment breaks, and maintenance windows planned around production.
Technical objects
What the company maintains, and where it sits
Before the first repair, PM needs a model of the plant: the places, the machines installed in them, their spare parts and counters, the standard jobs and the teams that do the work. Each object carries the cost center and other account assignment that later decide where the cost goes. Pick an object to see what it means and why FI and CO care.
Organization
Planning plant
The plant where maintenance work is planned: notifications and orders are created there, and the planners usually sit there. A logistics plant becomes a planning plant in Customizing, and each maintenance plant is assigned to one.
Example: Plant 1000, the central planning office
Why FI and CO care
Maintenance across plants is simple inside one company code, or across company codes in one controlling area. Plants in different controlling areas must deal with each other as customer and vendor, with purchase orders, sales orders and invoices.
TransactionsOIOD
Customizing: maintain the planning plant, then assign it to each maintenance plant. OIOD sets which order types each planning plant may use.
The transactions and the settings behind each object are in the Consultant view.
Organization
Maintenance plant
The plant where the technical objects physically sit. There is no separate setting for it: a plant becomes a maintenance plant as soon as a technical object is created there, provided it is assigned to a planning plant.
Example: Plant 1200, planned and stocked from plant 1000
Why FI and CO care
Each object in the plant carries a cost center, and that cost center is the usual receiver when its maintenance orders are settled.
TransactionsIH08IH06
Without the assignment to a planning plant, the plant can hold no technical objects and run no maintenance planning.
The transactions and the settings behind each object are in the Consultant view.
Structure
Functional location
A place in a hierarchy that represents a technical system or a building: a site, a line, a pump position. Its ID can have up to 40 characters, and a structure indicator with an edit mask decides how the levels are built.
Example: BR-SP1-UT-PMP01: São Paulo plant › utilities › pump position 01
Why FI and CO care
Location and account assignment, such as the cost center, sit on the object (table ILOA) and are copied into the notifications and orders created for it.
TransactionsIL01IL02IH01
Structure indicators and edit masks are defined once and reused for every functional location of the same kind. Master data is in IFLOT, texts in IFLOTX.
The transactions and the settings behind each object are in the Consultant view.
Structure
Equipment
An individual physical object maintained as a unit: a pump, a motor, a truck. It can be installed at a functional location, dismantled and installed somewhere else, and SAP keeps a usage list with every period of use.
Example: Equipment 10000231, centrifugal pump, serial 77-1042
Why FI and CO care
The equipment carries its own location and account assignment, so its orders find the right cost center. The usage list shows where it was installed, and when, if costs ever need to be traced back.
TransactionsIE01IE02IE4NIH08
The equipment category decides, among other things, whether installation is allowed. With hierarchies, only the top equipment can be installed at a functional location. Master data is in EQUI, texts in EQKT and time segments in EQUZ.
The transactions and the settings behind each object are in the Consultant view.
Structure
Maintenance BOM
The spare parts list of a technical object. A material BOM can be shared by identical machines; equipment and functional location BOMs belong to one object.
Example: Bearing 6205, seal kit and impeller for pump 10000231
Why FI and CO care
Parts picked from the BOM become reservations on the order. When they are issued from stock with movement type 261, inventory goes down and the order is debited.
TransactionsIB01IB11IH04
IB01 creates an equipment BOM and IB11 a functional location BOM; IH04 shows the equipment BOM as a structure list.
The transactions and the settings behind each object are in the Consultant view.
Around it
Measuring point and counter
A measuring point records a condition, such as a temperature or a vibration; a counter records use or wear, such as operating hours or kilometres. Every reading is a measurement document.
Example: Counter OPHRS on the pump: 4,812 hours
Why FI and CO care
No posting of its own. Counters drive performance-based maintenance plans, so they decide when the next order, and its cost, arrives.
TransactionsIK01IK11IK22
Readings can also be entered in time confirmations and in Perform Maintenance Jobs. Measurement documents are stored in IMRG.
The transactions and the settings behind each object are in the Consultant view.
Around it
Task list
The standard recipe for a job: operations, durations, work centers, spare parts and services. Maintenance plans and orders copy it, so the same job is not typed twice.
Example: General task list PUMP-6M: inspect, replace bearing, align
Why FI and CO care
The operations and parts of the task list become the planned costs of the order and the cost estimate of the maintenance plan.
TransactionsIA05IA01IA11
General task lists (IA05) can be used for any object; equipment (IA01) and functional location (IA11) task lists belong to one. Header in PLKO, operations in PLPO.
The transactions and the settings behind each object are in the Consultant view.
Around it
Work center
The team or person that does the work, such as mechanics or electricians, with its capacity and the activity type used to value its hours.
Example: MECH-01 Mechanical workshop, activity type LABOR
Why FI and CO care
Hours confirmed on an operation are valued with the price of the work center’s cost center and activity type, planned in KP26. With no price for the period, the confirmation stops with error CK466.
TransactionsIR01IR02CA85
The work center links to a cost center and activity types; CA85 replaces a work center in many task lists at once.
The transactions and the settings behind each object are in the Consultant view.
Sources: SAP Learning, technical objects and BOMs, and measuring points and counters; SAP PRESS, plants from a maintenance perspective; SAP Help, equipment at functional locations; SAPSTACK, PM tables (ILOA, IFLOT, EQUI) and transaction codes; erplingo, IB01; SAP Community, standard PM reports and activity price error CK466.
The PM process
Follow one breakdown from the first report to the closed order
SAP S/4HANA organizes maintenance in nine phases, set by the system from what happens to the request and the order. The classic SAP GUI flow follows the same logic with fewer names. Pick a phase to see what happens, where you see it, what it posts in the books and, in the Consultant view, what sits under the hood.
Phase 1 of 9 · What happens
Something breaks: the request
Pump P-101 starts vibrating. Someone creates a maintenance request for the technical object, with a description, attachments and, where the plant uses it, a priority assessment. In classic processing this is a notification: M2 to report a malfunction, M1 to ask for work, M3 to document work already done.
Who: Requester: an operator, a technician, anyone
Where you see it
Create Maintenance Request and My Maintenance Requests in Fiori; IW21 in SAP GUI, with IW22 to change and IW23 to display.
IW21IW22IW23
Under the hood
The notification type decides the screens. The breakdown indicator and the malfunction start and duration feed MTTR and MTBR. The notification header is stored in QMEL, the same table as quality notifications, with the maintenance data in QMIH.
QMELQMIHQS41
Customizing, tables and the settings behind this phase are in the Consultant view.
No postingIn the books: Nothing yet. A notification is a record, not a cost object.
Sources: SAP Learning, the phase model; SAP Help, notification types and maintenance notification; SAP blog, Breakdown Analysis app; TestingBrain, table QMEL.
Phase 2 of 9 · What happens
Someone decides: screening
Someone responsible looks at the open requests, checks the object, the urgency and who should act, and accepts the request, rejects it or sends it back for more information. Accepted requests go on to planning as notifications.
Who: Maintenance gatekeeper or supervisor
Where you see it
Screen Maintenance Requests in Fiori; in SAP GUI, notification lists in IW28 or IW29 and changes in IW22.
IW28IW29
Under the hood
Prioritization profiles per plant and notification type drive the priority assessment. The screening screen groups requests as Open, Accepted, Rejected, Action Required and Completed.
IW22
Customizing, tables and the settings behind this phase are in the Consultant view.
No postingIn the books: Still nothing. A rejected request never costs anything.
Sources: SAP Learning, the phase model; SAP blog, Asset Management in SAP S/4HANA 2021.
Phase 3 of 9 · What happens
The planner builds the order
The planner creates an order for the notification, or assigns an existing one, and copies its data. Operations say what has to be done and by which work center, components list the spare parts and external operations ask for services. Planned costs appear as resources are planned.
Who: Maintenance planner
Where you see it
Manage Maintenance Notifications and Orders or Create Maintenance Order in Fiori; IW31 in SAP GUI, with IW32 to change.
IW31IW32
Under the hood
The order type sets the number range, settlement profile, costing data and whether the phase model applies. Control key PM01 makes an operation internal; PM02 and PM03 make it external, with a purchase requisition. Planned costs come from the operations and components, not from typing.
OIOAAFIHAUFK
Customizing, tables and the settings behind this phase are in the Consultant view.
Plan onlyIn the books: Planned costs, kept for comparison later. Nothing reaches the general ledger.
Sources: SAP Learning, the phase model, costing and standard service (PM03); SAP Community, external procurement (PM02).
Phase 4 of 9 · What happens
Approval and release
If the order type requires it, the order goes for approval, for example above a cost limit, and approvers decide in My Inbox. When the order is approved, its baseline cost is set to the planned cost, so overruns can be measured later. Then the order is released.
Who: Approvers in a flexible workflow
Where you see it
Manage Workflows for Maintenance Orders and My Inbox in Fiori. In SAP GUI, releasing the order in IW32 is the step that lets work and procurement start.
IW32IW38
Under the hood
Each step condition that is true creates an approval step. Releasing sets system status REL: material and capacity checks run, and reservations and purchase requisitions are created if the order type did not create them earlier.
RELOIOA
Customizing, tables and the settings behind this phase are in the Consultant view.
No postingIn the books: Release makes reservations and purchase requisitions effective. Still no actual cost.
Sources: SAP Learning, the phase model; SAP Help, system status for orders and materials planning for orders.
Phase 5 of 9 · What happens
Preparation: parts, services, buckets
Work is grouped into planning buckets, such as a weekly maintenance window or a planned shutdown, and the backlog shows what is ready: status, priority, due date, materials and resources. Purchasing turns the purchase requisitions into purchase orders.
Who: Planner and purchasing
Where you see it
Manage Maintenance Planning Buckets and Manage Maintenance Backlog in Fiori; IW37N for orders and operations in SAP GUI; ME21N for the purchase order.
IW37NME21N
Under the hood
Purchase requisitions and purchase orders carry the order as account assignment, and open purchase orders show on the order as commitments before any goods receipt. KOB2 lists them.
KOB2ME21N
Customizing, tables and the settings behind this phase are in the Consultant view.
CommitmentIn the books: Open purchase orders show as commitments on the order: money promised, not yet spent.
Sources: SAP Learning, the phase model and costing.
Phase 6 of 9 · What happens
Scheduling: dates and people
Orders and operations are dispatched to dates and work centers. Without resource scheduling, whole orders are dispatched; with it, each operation is placed on the board and capacity is balanced across work centers.
Who: Planner or supervisor
Where you see it
Maintenance Scheduling Board, Manage Schedules and Manage Work Center Utilization in Fiori; IW37N in SAP GUI.
IW37N
Under the hood
Operations are tagged PRE, MAIN or POST as execution stages. Resource scheduling needs its own license (RSH).
IW37N
Customizing, tables and the settings behind this phase are in the Consultant view.
No postingIn the books: No posting. Capacity is reserved, money is not.
Sources: SAP Learning, the phase model; SAP PRESS, Fiori apps for maintenance planning.
Phase 7 of 9 · What happens
Execution: the repair
The work is done. Technicians take the spare parts, record hours and findings and enter counter readings. Vendors deliver their services, recorded with a goods receipt or a service entry sheet.
Who: Technicians
Where you see it
Perform Maintenance Jobs in Fiori or on mobile; IW41 for time confirmation and MIGO for the goods issue in SAP GUI.
IW41IW42MIGO
Under the hood
Goods issue to the order uses movement type 261. Time confirmations allocate the work center’s activity at its KP26 price. Goods receipts and accepted service entry sheets post the external cost to the order.
261KP26IW47
Customizing, tables and the settings behind this phase are in the Consultant view.
Actual costIn the books: Actual costs arrive: spare parts from stock, hours at the activity price and external services. The order now has a balance.
Sources: SAP Learning, executing a maintenance task and period-end closing (BF7); SAP Community, movement type 261.
Phase 8 of 9 · What happens
Post execution: technically complete
Final work is confirmed, failure data such as damage, cause and breakdown time is completed, and the supervisor sets the order to technically complete (TECO). The notification can be completed with it if it has no outstanding tasks.
Who: Technician, then supervisor
Where you see it
Perform Maintenance Jobs and Find Maintenance Order in Fiori; IW32 or IW42 in SAP GUI.
IW32IW42
Under the hood
TECO closes open reservations and capacities and flags purchase requisitions without a purchase order for deletion. If the order has no settlement rule yet, SAP creates one automatically.
TECOIW32
Customizing, tables and the settings behind this phase are in the Consultant view.
No postingIn the books: Technical completion posts nothing. Invoices and late confirmations can still reach the order.
Sources: SAP Learning, executing maintenance orders and settlement; SAP Help, system status for orders.
Phase 9 of 9 · What happens
Completion: settle and close
Actual costs are compared with the plan, invoices are checked and the order is settled: its costs move to the receiver in the settlement rule. With the balance at zero and no purchase order open, the order is completed for business (CLSD) and no more costs can be posted.
Who: Planner or controller
Where you see it
Find Maintenance Order and the Maintenance Order Costs app in Fiori; KO88 to settle one order and KO8G for many, then complete for business in IW32.
KO88KO8GIW32
Under the hood
The settlement profile of the order type says which receivers are allowed: cost center, WBS element, fixed asset. With parallel ledgers, settlement runs for each ledger. Phase-based orders must be fully settled before they close.
KO88KO8G
Customizing, tables and the settings behind this phase are in the Consultant view.
SettlementIn the books: Settlement credits the order and debits the receiver. Balance zero, order closed.
Sources: SAP Learning, period-end closing (BF7) and settlement; SAP Help, business completion and settling the maintenance order.
The three order statuses everyone mixes up
Most questions about a maintenance order come down to one of these. They decide what can still happen to the order, and whether costs can still reach it.
- REL · ReleasedWork can startMaterial and capacity checks run, reservations and purchase requisitions become effective, and goods movements and confirmations can be posted.
- TECO · Technically completedThe work is doneOpen reservations and capacities are closed and open purchase requisitions are flagged for deletion. Invoices and late confirmations can still post costs.
- CLSD · Completed for businessNothing more can postOnly possible when the order is settled, its balance is zero and no purchase order is open. After it, the order accepts no more costs.
Sources: SAP Help, system status for orders, and business completion of an order.
Try it · Preventive maintenance
How a maintenance plan creates work by itself
Preventive maintenance runs on plans. A plan has a cycle, such as every 90 days or every 500 operating hours, and the call horizon says how far into that cycle SAP creates the order. Nothing happens unless the plan is scheduled: started once in IP10, then watched by the deadline monitoring job. Change the plan below and watch the calls move.
The plan
Example: a 90-day cycle with an 80% call horizon, each job finished on the planned date.
Single cycle plan, time-based, started on 1 Jan 2027. Simplified: tolerances, factory calendar and cycle modification factor are left out.
The next four calls
With a 90-day cycle and an 80% call horizon, SAP creates each order 72 days into the cycle, 18 days before it is due.
- Order exists, waiting
- Planned date
- Actual finish
- Call 1Order created 14 Mar 2027Due 1 Apr 2027 · 18 days to prepareFinished 1 Apr 2027
- Call 2Order created 12 Jun 2027Due 30 Jun 2027 · 18 days to prepareFinished 30 Jun 2027
- Call 3Order created 10 Sep 2027Due 28 Sep 2027 · 18 days to prepareFinished 28 Sep 2027
- Call 4Order created 9 Dec 2027Due 27 Dec 2027 · 18 days to prepareFinished 27 Dec 2027
Timeline from 1 Jan 2027 to the last date shown.
IP41Single cycle plan
One cycle, by time or by a counter: every 90 days, or every 500 operating hours. The simplest plan, and the one in the simulator.
IP42Strategy plan
Several packages from a strategy (IP11), such as clean every 3 months and replace every 6. When packages fall together, only the highest hierarchy runs.
IP43Multiple counter plan
Time and counters together, linked with OR, which triggers at the first deadline, or AND, which waits for the last one.
IP10 · IP30 · IP30HNo scheduling, no orders
A new plan is started once in IP10. After that, deadline monitoring, usually a daily job (IP30, program RISTRA20, or IP30H on SAP HANA), recalculates dates and creates the orders.
Sources: SAP Help, call horizon; SAP Learning, scheduling a single cycle plan, SAP GUI functions for single-cycle plans, scheduling maintenance plans and describing a maintenance strategy; SAP blog, types of maintenance plans.
Try it · Costs
From the maintenance order to the journal entry
This is the part FI and CO consultants ask about most. A maintenance order collects three kinds of cost: hours from internal work centers, spare parts from stock and services from vendors. At period-end, settlement passes the total on to a receiver. Change the order and the receiver, and follow the money.
Order 4000123
Example: 12 hours, spare parts 250.00, external service 800.00, settled to the cost center.
Activity price 65.00 per hour, in USD. Examples only.
Actual costs on the order
| Cost | Comes from | Amount |
|---|---|---|
| Internal activity | 12 h × 65.00, work center MECH-01 | 780.00 |
| Spare parts | Goods issue from stock, movement type 261 | 250.00 |
| External service | Goods receipt on the purchase order | 800.00 |
| Actual costs | Before settlement | 1,830.00 |
| Settlement | To Cost center 4110 Utilities | −1,830.00 |
| Order balance | Ready for CLSD | 0.00 |
What each step posts
| Step | Debit | Credit | Amount |
|---|---|---|---|
| Time confirmation | Order 4000123 (internal activity) | Cost center of MECH-01 | 780.00 |
| Goods issue 261 | Order 4000123 (consumption, GBB-VBR) | Inventory (BSX) | 250.00 |
| Goods receipt | Order 4000123 (service expense) | GR/IR clearing (WRX) | 800.00 |
| Settlement | Cost center 4110 Utilities | Order 4000123 | 1,830.00 |
Debits on the order 1,830.00, settlement credit 1,830.00: balance 0.00.
Where the cost ends up
USD 1,830.00
Maintenance expense of cost center 4110
The cost stays in the income statement this period and is reported by cost center. This is the usual receiver for repairs and routine maintenance, taken from the technical object.
Capitalized on asset 10000045
The cost leaves the income statement and becomes part of the asset’s acquisition value, coming back as depreciation over its life. Your accounting policy decides when maintenance work may be capitalized.
Collected on overhaul project P-1001
The project gathers the cost of many orders and is settled later, often to an asset under construction, so large overhauls can be budgeted and tracked as one.
The settlement profile of the order type decides which receivers are allowed; the settlement rule on the order decides which one is used.
Examples only: your G/L accounts come from your settings. Hours are an internal activity allocation with a secondary cost element; goods issues follow MM account determination (OBYC), where VBR is the grouping for internal goods issues; settlement uses the cost elements in the allocation structure of the settlement profile. Sources: SAP Learning, costing, settlement and period-end closing (BF7); SAP Help, account grouping VBR; SAP Community, movement type 261 for PM orders and maintenance orders with external procurement (PM02).
Quick test
Why is my maintenance order stuck?
Eight calls every PM support team knows by heart. Guess the cause first, then open the card to see it, the fix and who acts.
- Completion
- Costs
- Planning
- Materials
- Master data
Complete (business) fails: the balance is not zeroShow the answer
CompletionThe order still has costs that were not settled. Run settlement for the period (KO88, or KO8G in the monthly job) and try again: business completion needs a zero balance.
Who acts: Planner or controller
Complete (business) fails because of a purchase orderShow the answer
CompletionA purchase order assigned to the order is still open, so there is a commitment. Finish it with purchasing, with the last goods receipt and invoice or by closing the item, then complete again.
Who acts: Purchasing, then planner
The notification cannot be completedShow the answer
CompletionIt still has outstanding tasks (status OSTS). Complete or release the tasks first. The order itself can still be completed, because those tasks may belong to other work.
Who acts: Supervisor
Confirming hours stops with “price cannot be determined” (CK466)Show the answer
CostsThere is no activity price for the work center’s cost center and activity type in the period or fiscal year of the confirmation. Plan the price in KP26, also for next year if the order runs into it.
Who acts: Controlling
The maintenance plan never created the orderShow the answer
PlanningUsually the plan was never started in IP10, the deadline monitoring job (IP30 or IP30H) is not running, the call date is not reached yet or the plan is inactive (INAK). With the completion requirement on, the next call also waits for the previous order to be completed.
Who acts: Planner, then basis for the job
No reservation or purchase requisition for the partsShow the answer
MaterialsUnless the order type creates them at once, reservations and purchase requisitions are generated only when the order is released. Release the order, or ask for the Res/PReq setting of the order type.
Who acts: Planner
After TECO, the purchase requisition disappearedShow the answer
MaterialsTechnical completion flags purchase requisitions without a purchase order for deletion and closes open reservations. If the work must continue, cancel the technical completion first.
Who acts: Supervisor
The costs went to the old cost centerShow the answer
Master dataThe order took the location and account assignment of the object on its creation date. If the equipment’s cost center changed meanwhile, use Update Reference Object Data on the order before settling.
Who acts: Planner, then controller
Sources: SAP Help, business completion, system status for orders and materials planning for orders; SAP Learning, executing maintenance orders, scheduling a single cycle plan and SAP GUI functions for single-cycle plans; SAP Community, activity price error CK466.
Speak PM
The codes PM people use
PM people talk in codes: “the M2 has an order, it’s REL, the PM02 operation waits for the PO, we TECO on Friday”. These are the standard ones you will hear in meetings and see on every screen. Your company may add its own, often starting with Z or Y.
Each notification type has its own screens, set in Customizing, and companies add their own types for their processes.
Only CLSD stops costs. After TECO, invoices and late confirmations can still post; only CLSD, reached with a zero balance, blocks every posting.
Two lives: the notification and the order have their own statuses. Completing one does not complete the other, unless you complete them together.
PM01 is three things: a control key, the standard maintenance order type and the confirmation profile in SAP’s IW42 example. The context tells you which one is meant.
Call horizon in one line: 0% creates the order at the start of the cycle, 80% after 80% of it, 100% on the planned date.
M1Maintenance requestAsks for maintenance work to be done.M2Malfunction reportReports a failure that has happened; carries the breakdown data.M3Activity reportDocuments maintenance work already done.S1Problem notificationService: a customer reports a problem.S2Service requestService: a customer asks for service.S3Activity reportService: documents service work done.Q1Customer complaintQuality: a complaint from a customer.Q2Complaint against vendorQuality: a defect from a supplier.Q3Internal problemQuality: a problem found inside the company.CRTDCreatedBeing planned; no goods receipts yet.RELReleasedWork, goods movements and confirmations allowed.PCNFPartially confirmedSome work confirmed, more to come.CNFFinally confirmedThe work is confirmed as finished.TECOTechnically completedWork done; reservations closed, costs still possible.CLSDCompleted for businessSettled, balance zero, no more postings.DLFLDeletion flagMarked for deletion and archiving.OSNOOutstanding notificationCreated, not yet in process.NOPRNotification in processSomeone is working on it.ORASOrder assignedAn order exists for it.OSTSOutstanding tasksTasks still open; blocks completion.NOCONotification completedClosed; goes to history.DLFLDeletion flagMarked for deletion and archiving.PM01Internal processingDone by your own work centers, valued at the activity price.PM02External processingPurchase requisition, purchase order and goods receipt to the order.PM03External serviceService specifications, confirmed with a service entry sheet.IP41Single cycle planOne cycle, time or counter.IP42Strategy planPackages from a strategy, such as 3M and 6M.IP43Multiple counter planSeveral cycles linked with OR or AND.IP10Schedule a planStart, restart, manual call.IP30Deadline monitoringDaily job that creates the due orders.IP30HDeadline monitoring on HANAFinds the due plans by itself.INAKInactive planNo calls until it is active again.
One table for maintenance and quality notifications. Both are rows of table QMEL, the notification header, with the maintenance data in QMIH, items in QMFE, causes in QMUR, tasks in QMSM and activities in QMMA. An extract of QMEL mixes them unless you filter by notification type. Source: TestingBrain · SAP Help
Reference
The PM transactions people actually use
PM transactions follow a pattern: IW for notifications and orders, IE for equipment, IL for functional locations, IP for maintenance plans, IK for measuring points, IA for task lists, IB for BOMs and IH for structures and lists. Start here shows the ones worth bookmarking; FI/CO bridge collects what controlling and finance people touch; 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 |
|---|---|---|---|---|
IW21 | User | Create a maintenance notification: malfunction, request or activity report, for a functional location or equipment. | Anyone who reports problems | ECC + S/4HANA |
IW22 | User | Change a notification: tasks, causes, damage codes, breakdown times, completion. | Supervisors, planners | ECC + S/4HANA |
IW23 | User | Display a notification. | Everyone | ECC + S/4HANA |
IW28 | User | Change notifications in a list, selected by object, date, status or priority. | Planners | ECC + S/4HANA |
IW29 | User | Display notifications in a list. | Everyone | ECC + S/4HANA |
IW64 | User | Change the list of notification activities; IW65 displays it. IW66 and IW67 do the same for tasks, IW68 and IW69 for items. | Planners, reliability engineers | ECC + S/4HANA |
IW31 | User | Create a maintenance order: operations, work centers, spare parts and services. | Planners | ECC + S/4HANA |
IW32 | User | Change an order: release, settlement rule, technical completion, complete for business. | Planners | ECC + S/4HANA |
IW33 | User | Display an order, with its costs and document flow. | Everyone | ECC + S/4HANA |
IW38 | User | Change orders in a list. | Planners, supervisors | ECC + S/4HANA |
IW39 | User | Display orders in a list. | Everyone | ECC + S/4HANA |
IW40 | User | Display orders in a multi-level list, with the objects linked to each order. | Planners, controllers | ECC + S/4HANA |
IW37N | User | Change orders and operations in one combined list. | Planners, schedulers | ECC + S/4HANA |
IW49N | User | Display orders and operations in one combined list. | Everyone | ECC + S/4HANA |
IW41 | User | Time confirmation for an operation: hours, final confirmation, measurement readings. | Technicians, supervisors | ECC + S/4HANA |
IW42 | User | Overall completion confirmation: time, materials, damage, activities and readings in one screen. | Supervisors | ECC + S/4HANA |
IW47 | User | Display a list of time confirmations. | Supervisors, controllers | ECC + S/4HANA |
IW13 | User | Where-used list of a material in orders. | Storeroom, planners | ECC + S/4HANA |
IW3K | User | Change the list of order components; IW3L displays it. | Storeroom, planners | ECC + S/4HANA |
COGI | User | Postprocess goods movements that failed, such as a goods issue that could not be posted. | Storeroom, support | ECC + S/4HANA |
IE01 | User | Create equipment; IE02 changes and IE03 displays it. | Master data team | ECC + S/4HANA |
IH08 | User | Display equipment in a list; IE05 changes the list. | Everyone | ECC + S/4HANA |
IE4N | User | Install or dismantle equipment together with the goods movement. | Master data, warehouse | ECC + S/4HANA |
IL01 | User | Create a functional location; IL02 changes and IL03 displays it. | Master data team | ECC + S/4HANA |
IH01 | User | Structure display of a functional location, with the equipment installed below it. | Everyone | ECC + S/4HANA |
IH06 | User | Display functional locations in a list; IL05 changes the list. | Everyone | ECC + S/4HANA |
IB01 | User | Create an equipment BOM; IB11 creates a functional location BOM, IH04 shows the equipment BOM structure. | Master data team | ECC + S/4HANA |
IK01 | User | Create a measuring point or a counter; IK02 changes and IK03 displays it. | Master data team | ECC + S/4HANA |
IK11 | User | Create a measurement document: one reading for a measuring point or counter. | Operators, technicians | ECC + S/4HANA |
IK22 | User | Enter measurement documents in a collective list. | Operators | ECC + S/4HANA |
IA05 | User | Create a general task list; IA01 creates one for an equipment, IA11 for a functional location. | Planners | ECC + S/4HANA |
IP41 | User | Create a single cycle plan, time or performance based. | Planners | ECC + S/4HANA |
IP42 | User | Create a strategy plan from a maintenance strategy. | Planners | ECC + S/4HANA |
IP43 | User | Create a multiple counter plan. | Planners | ECC + S/4HANA |
IP10 | User | Schedule a maintenance plan: start, restart, manual call. | Planners | ECC + S/4HANA |
IP24 | User | Scheduling overview as a list; IP19 shows it graphically. | Planners | ECC + S/4HANA |
IP16 | User | Display maintenance plans in a list; IP15 changes them, IP17 and IP18 do the same for maintenance items. | Planners | ECC + S/4HANA |
MCI7 | User | Breakdown analysis: number of breakdowns and downtime by object. | Reliability engineers | Classic report (PMIS) |
MCJB | User | MTTR and MTBR for equipment; MCJC does it for functional locations. | Reliability engineers | Classic report (PMIS) |
IP30 | Consultant | Deadline monitoring for many plans, usually a daily job with program RISTRA20. | Consultants, basis | ECC + S/4HANA |
IP30H | Consultant | Deadline monitoring on SAP HANA: preselects the due plans itself; log in SLG1. | Consultants | S/4HANA, LOG_EAM_MPSI |
IP11 | Consultant | Maintenance strategies: packages, cycles, hierarchy; IP12 displays them. | Consultants, planners | ECC + S/4HANA |
IR01 | Consultant | Create a work center with capacity, cost center and activity types; IR02 changes it. | Consultants, master data | ECC + S/4HANA |
CA85 | Consultant | Replace a work center in many task lists at once. | Consultants | ECC + S/4HANA |
OIOA | Consultant | Maintenance order types: number range, settlement profile, costing and other controls. | Consultants | ECC + S/4HANA |
OIOD | Consultant | Order types allowed per planning plant. | Consultants | ECC + S/4HANA |
QS41 | Consultant | Maintain the code catalogs used in notifications, such as damage, causes and activities. | Consultants | ECC + S/4HANA |
BS02 | Consultant | Status profiles for user statuses on notifications and orders. | Consultants | ECC + S/4HANA |
KO88 | FI/CO bridge | Settle one order: its costs move to the receivers in the settlement rule. | Controllers, planners | ECC + S/4HANA |
KO8G | FI/CO bridge | Settle orders collectively, usually in the period-end job. | Controllers | ECC + S/4HANA |
KOB1 | FI/CO bridge | Actual cost line items of an order. | Controllers | ECC + S/4HANA |
KOB2 | FI/CO bridge | Commitment line items: open purchase requisitions and purchase orders for the order. | Controllers | ECC + S/4HANA |
KP26 | FI/CO bridge | Plan activity prices by cost center and activity type; confirmed hours are valued with them. | Controllers | ECC + S/4HANA |
KSB1 | FI/CO bridge | Cost center actual line items, where settled maintenance costs land. | Controllers | ECC + S/4HANA |
MCI8 | FI/CO bridge | PMIS cost analysis by object. | Controllers, managers | Classic report (PMIS) |
ME21N | FI/CO bridge | Purchase order for an external operation or a non-stock part, with the order as account assignment. | Purchasing | ECC + S/4HANA |
MIGO | FI/CO bridge | Goods issue of spare parts to the order, movement type 261. | Storeroom | ECC + S/4HANA |
| Create Maintenance Request | Fiori app | Report a problem from desktop or phone; starts the initiation phase. | Everyone | S/4HANA |
| Screen Maintenance Requests | Fiori app | Accept, reject or send back requests, with a priority assessment. | Gatekeepers | S/4HANA |
| Manage Maintenance Notifications and Orders | Fiori app | Plan phase-based notifications and orders. | Planners | S/4HANA |
| Find Maintenance Order and Operation | Fiori app | Select orders and operations with flexible filters and act on them. | Supervisors, planners | S/4HANA |
| Find Technical Object | Fiori app | Search equipment and functional locations; see their notifications, orders, measuring points and documents; mass edit. | Everyone | S/4HANA |
| Perform Maintenance Jobs | Fiori app | The technician’s app: own jobs, time, goods issues, malfunction data and readings, for phase-based and classic orders. | Technicians | S/4HANA |
| Manage Maintenance Planning Buckets | Fiori app | Group work into weekly windows or shutdowns. | Planners | S/4HANA |
| Manage Maintenance Backlog | Fiori app | The backlog with readiness by status, priority, due date, materials and resources. | Planners | S/4HANA |
| Maintenance Scheduling Board | Fiori app | Gantt chart of orders and operations by work center: dispatch and resolve conflicts. | Schedulers | S/4HANA, Resource Scheduling |
| Manage Workflows for Maintenance Orders | Fiori app | Approval workflows with step conditions and approvers. | Key users, consultants | S/4HANA |
| Breakdown Analysis (F2812) | Fiori app | Breakdowns, MTTR and MTBR per equipment. | Reliability engineers | S/4HANA |
| Maintenance Order Costs | Fiori app | The costs of a maintenance order, with a detailed cost analysis of actual against planned costs. | Controllers, planners | S/4HANA |
QMEL | Table | Notification header, shared with quality notifications. | Consultants, analysts | ECC + S/4HANA |
QMIH | Table | Maintenance data of a notification. | Consultants | ECC + S/4HANA |
QMFE | Table | Notification items; QMUR causes, QMSM tasks, QMMA activities. | Consultants | ECC + S/4HANA |
AFIH | Table | Maintenance order header. | Consultants, analysts | ECC + S/4HANA |
AUFK | Table | Order master data, shared with all CO orders. | Consultants, controllers | ECC + S/4HANA |
AFKO | Table | Order header data, shared with production orders. | Consultants | ECC + S/4HANA |
AFVC | Table | Operations of the order. | Consultants | ECC + S/4HANA |
RESB | Table | Reservations: the spare parts of the order. | Consultants | ECC + S/4HANA |
EQUI | Table | Equipment master data; EQKT texts, EQUZ time segments. | Consultants | ECC + S/4HANA |
IFLOT | Table | Functional location master data; IFLOTX texts. | Consultants | ECC + S/4HANA |
ILOA | Table | Location and account assignment of a technical object. | Consultants, controllers | ECC + S/4HANA |
MPLA | Table | Maintenance plans; MPOS items, MHIS calls, MMPT cycles. | Consultants | ECC + S/4HANA |
IMRG | Table | Measurement documents. | Consultants | ECC + S/4HANA |
PLKO | Table | Task list header; PLPO operations. | Consultants | ECC + S/4HANA |
JEST | Table | Statuses of orders, notifications and other objects. | Consultants | ECC + S/4HANA |
IHPA | Table | Partners of notifications, orders and technical objects. | Consultants | ECC + S/4HANA |
Nothing matches. Try another word, or pick All.
Standard codes, cross-checked with the SAPSTACK and TestingBrain PM lists, erplingo, the SAP Community list of standard PM reports, SAP Help and SAP Learning; Fiori app names follow SAP Learning, SAP blogs and SAP PRESS. 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 PM with SAP S/4HANA
Notifications, orders and plans are the same objects as in SAP ECC, and the IW transactions still work. What changed is around them: an optional phase model, Fiori apps for each role, faster plan scheduling, new mobile and reliability tools, and AI. If your company is moving from ECC, these are the cards to read.
The process
ECCNotification and order, with system and user statuses.
S/4HANAAn optional phase model: nine phases set by the system, activated per order type.
Activating it for an order type has no effect on orders already created.
Source: SAP blog, Asset Management in S/4HANA 2021Best-practice scope items
ECCCorrective and preventive maintenance as classic processes.
S/4HANAReactive (4HH) and Proactive (4HI) maintenance with phases; in the public cloud, BH1 and BJ2 were deprecated in release 2302.
Improvement (4VT) and Operational and overhead maintenance (4WM) complete the set.
Source: SAP Learning, implementing SAP S/4HANA (scope items)User interface
ECCSAP GUI: IW21, IW31, IW41.
S/4HANAFiori apps for each role: request, screen, plan, schedule, perform.
Perform Maintenance Jobs works with both phase-based and classic orders from SAP S/4HANA 2022.
Source: SAP Learning, executing a maintenance taskScheduling plans
ECCIP30 with selection variants, as a daily job with program RISTRA20.
S/4HANAIP30H finds the due plans by itself on SAP HANA.
Needs business function LOG_EAM_MPSI; its log is in SLG1 under object IP30H.
Source: SAP Learning, SAP GUI functions for single-cycle plansCall horizon
ECCA percentage of the cycle.
S/4HANAAlso in calendar days (DAY) or factory calendar days (FKT).
Delivered with business function LOG_EAM_CI_6.
Source: SAP Learning, scheduling a single cycle planScheduling work
ECCCapacity planning and order lists in SAP GUI.
S/4HANAMaintenance Scheduling Board and Manage Schedules, with flexible schedule periods.
Resource Scheduling needs its own license (RSH).
Source: SAP blog, Asset Management in S/4HANA 2021Planning and backlog
ECCOrder lists and personal variants.
S/4HANAPlanning buckets for shutdowns and weekly windows, and a backlog with readiness indicators.
A final due date, the latest date for the work, is set from the priority.
Source: SAP blog, Asset Management in S/4HANA 2021Mobile
ECCSAP Work Manager and partner apps.
S/4HANASAP Service and Asset Manager, on iOS and Android, offline.
On-premise systems need a mobile add-on to connect through SAP BTP.
Source: SAP Learning, mobile maintenanceReliability figures
ECCPMIS: MCI7 breakdown analysis, MCJB and MCJC for MTTR and MTBR.
S/4HANABreakdown Analysis app (F2812).
Only notifications with the breakdown indicator count.
Source: SAP blog, Breakdown Analysis app F2812Asset strategy and health
ECCSeparate products: ASPM and Predictive Asset Insights.
S/4HANASAP Asset Performance Management (APM), integrated with SAP EAM.
The earlier products stay supported while they have subscribers.
Source: SAP blog, introducing SAP APM (2022)Words on the screen
ECCRevision; activity type on the order.
S/4HANAMaintenance event; maintenance activity type.
Renamed in the 2021 release, so old manuals and new screens use different words.
Source: SAP blog, Asset Management in S/4HANA 2021AI
ECCNot available.
S/4HANAOrder suggestions from similar past notifications, and Joule.
SAP also offers a Maintenance Planner agent for backlogs, licensed separately.
Source: SAP Learning, AI in SAP EAM
Brazil
PM in Brazil: inspections by law and taxes on spare parts
In Brazil, part of maintenance is not optional: a labor ministry norm sets mandatory safety inspections for boilers and pressure vessels. And the spare parts behind every order carry a tax question that the consumption tax reform is about to change.
- NR-13
Inspections with legal deadlines
NR-13 covers boilers above 60 kPa, pressure vessels with P·V above 8 and other equipment, with initial, periodic and extraordinary safety inspections at maximum intervals by category. For boilers of categories A and B without an own inspection service (SPIE), the limit is 12 months. These deadlines fit naturally as time-based maintenance plans, and the safety record can be kept in a computerized system.
Source: NR-13, text as amended in 2022 - ICMS
No credit on use and consumption until 2033
Maintenance materials bought for use and consumption (uso e consumo) do not give ICMS credit yet: LC 171/2019 moved the start date in LC 87/96 to 1 January 2033. Until then, the tax is part of the cost of the part and, through the order, of the maintenance cost that settlement passes on.
Source: Systax, LC 171/2019 - IBS and CBS
Broad credit with the reform
Under LC 214/2025, IBS and CBS give credit on purchases in general, maintenance included, unless the goods or services are for personal use or consumption. Tax codes and the master data used in maintenance purchases are worth reviewing as the new taxes phase in.
Source: Jettax, broad credit in the reform
Documented, but little known
15 tips for users and consultants
Each tip comes from SAP Learning, SAP Help, an SAP blog or a published source, linked under the tip.
- 01Users
An empty IW38 is usually the selection
If orders you know exist do not appear, check the status boxes, the period and any hidden selection values. Typing only the order numbers is the quickest test: if they show, the selection was the problem.
IW38IW39
- 02Users
One screen for the whole confirmation
IW42 records time, spare parts, damage, activities and measurement readings for an order in one screen, instead of IW41 plus separate transactions.
IW42
- 03Users
Readings while you confirm
Counter readings and measurements can be entered in the time confirmation, in IW41 or in Perform Maintenance Jobs, so technicians do not need a separate IK11.
IW41IK11
- 04Users
Complete order and notification together
It only works when the notification has no outstanding tasks. If tasks remain, complete the order now and the notification later.
IW32
- 05Users
Everything about one machine in one app
Find Technical Object shows an equipment’s notifications, orders, measuring points, readings and attachments, and lets you mass-edit fields such as warranty dates.
Source: SAP Learning, Fiori apps for functional locations - 06Consultants
The phase model is set per order type
Activating it for an order type has no effect on orders already created, so old and new orders run side by side until the old ones are closed.
OIOA
- 07Consultants
Call horizon in days
Besides a percentage of the cycle, the call horizon can be given in calendar days (DAY) or factory calendar days (FKT), with business function LOG_EAM_CI_6.
IP41IP11
- 08Consultants
IP30H finds the due plans itself
The SAP HANA version of deadline monitoring preselects the plans that are due, so it needs no selection variant; its log is in SLG1 under object IP30H.
IP30HSLG1
- 09Consultants
In a strategy, the higher package wins
When packages of the same strategy fall on the same date, only those with the highest hierarchy run. SAP’s example: replacing spark plugs every six months suppresses cleaning them every three.
IP11IP42
- 10Consultants
Phase control codes block phases, not work
They stop an order or operation from moving to a sub-phase, but goods receipts, service entry sheets, external confirmations and time reporting still go through.
Source: SAP Learning, the phase model - 11FI/CO
TECO posts nothing
Technical completion only locks the order for maintenance changes and creates a missing settlement rule. Settlement can run at any time afterwards, and an order can be debited again and settled again.
KO88
- 12FI/CO
Costs follow the creation date
The order takes location and account assignment from the object when it is created. If the equipment’s cost center changes, use Update Reference Object Data before settling.
IW32
- 13FI/CO
Every ledger is settled
With parallel accounting, settlement runs for each ledger, and the balance is zero only when all of them are settled. Phase-based orders cannot be closed before that.
KO8G
- 14FI/CO
Plan next year’s prices before January
Confirmations in a new fiscal year need KP26 activity prices for that year. Without them, the first confirmation of the year stops with error CK466.
KP26
- 15FI/CO
Costs per operation
Operation account assignment (business function LOG_EAM_OLC) lets each operation carry its own cost object, with the header showing the totals. An order uses header or operation costing, never both.
Source: SAP Learning, costing
Myths
Things people get wrong about PM
Myth
A notification and an order are the same thing.FactThe notification records a problem, a request or work done. The order plans the work and collects its costs. Many notifications never get an order, and one order can serve several notifications.
Myth
TECO closes the order for costs.FactAfter technical completion, invoices and late confirmations can still post. Only completion for business (CLSD), with a zero balance, blocks every posting.
Myth
A maintenance plan creates orders on its own.FactOnly if it is scheduled: started once in IP10 and then watched by deadline monitoring (IP30 or IP30H). Without the job, dates are not recalculated and no order appears.
Myth
A 100% call horizon creates the order early.FactIt is the opposite: 100% creates the order on the planned date itself, and 0% at the very start of the cycle.
Myth
Equipment and functional location mean the same.FactThe functional location is a place in the plant structure; the equipment is the physical object installed there, which can move, with a usage list for every period of use.
Myth
PM is only for factories.FactFunctional locations can represent any technical system or building, and PM also keeps fleet data for vehicles (table FLEET).
Myth
Maintenance costs always stay on the maintenance cost center.FactSettlement can send them to a cost center, a WBS element or a fixed asset. Capitalized work leaves the income statement altogether.
Myth
PM and Customer Service are separate systems.FactThey share technical objects and orders: SAP documents them as common components (CS-BD/PM-EQM, CS-SE/PM-WOC-MO), and service notification types S1 to S3 sit next to M1 to M3.
Evolution
From R/2’s RM-INST to AI agents
Maintenance has been in SAP since R/2, and the German roots still show in the screens. Gold dots mark the S/4HANA era.
- 1979SAP R/2SAP launches R/2. Maintenance is part of its materials management block, as a module called RM-INST.
- 1992SAP R/3R/3 brings SAP to client-server computing, with Plant Maintenance among its logistics modules, sharing technical objects and orders with Customer Service.
- ECC 6SAP ERP 6.0For most consultants this is classic PM: IW21 and IW31, plans scheduled with IP10 and IP30, reliability figures from PMIS.
- 2015SAP S/4HANANotifications, orders and plans stay. In SAP S/4HANA, SAP’s courses call the area Asset Management.
- 2021SAP S/4HANA 2021The nine-phase process for reactive and proactive maintenance arrives, with planning buckets and dispatching on the Maintenance Scheduling Board.
- 2022APM and S/4HANA 2022SAP Asset Performance Management becomes an official product for asset strategy and health; Perform Maintenance Jobs serves phase-based and classic orders.
- 2023Cloud release 2302In SAP S/4HANA Cloud, public edition, the classic corrective and preventive scope items are deprecated in favor of the phase-based ones.
- TodayAIAI suggests orders from similar past notifications, Joule answers questions and SAP offers a Maintenance Planner agent for backlogs.
Why so many I’s
Most PM transactions start with I: IW, IE, IL, IP, IK, IA, IB, IH. In German, maintenance is Instandhaltung, and SAP’s German screens still show it: IW38 reads “IH-Aufträge ändern”, change maintenance orders. In R/2, the maintenance module was called RM-INST.
Can costs still post?
| Status | What the order allows |
|---|---|
| CRTD | Planning; reservations and purchase requisitions, but no goods receipts yet |
| REL | Work, goods movements, confirmations and settlement |
| TECO | Maintenance changes locked; invoices, late confirmations and settlement still post |
| CLSD | Nothing: balance zero, no more postings |
Sources: SAP Help, system status for orders; SAP Learning, settlement.
The questions people ask most
What does PM stand for, and is it still called that?
Plant Maintenance. SAP’s courses for SAP S/4HANA call the area Asset Management and its wider portfolio Enterprise Asset Management (EAM), but the transactions, the tables and most people on a project still say PM.
What is the difference between a notification and an order?
The notification records something: a malfunction, a request or work already done, with damage, causes and breakdown times. The order plans and executes the work and collects its costs. A notification can live without an order, such as an activity report, and one order can serve several notifications.
Equipment or functional location: which one do I use?
Usually both. The functional location is the place in the plant structure, such as a pump position; the equipment is the physical pump installed there. When the pump is swapped, the place keeps its history and the pump keeps its own, with a usage list of where it was installed.
How does a maintenance plan create orders?
A plan has a cycle, a call horizon and a task list. Once it is started in IP10, deadline monitoring (IP30 or IP30H), usually a daily job, checks which calls are due and creates the call objects: maintenance orders, notifications or service entry sheets. Without scheduling, no order is ever created.
What is the call horizon?
A percentage of the cycle that decides when the order is created. With a 90-day cycle, 0% creates it right away, 80% after 72 days and 100% on the planned date. Newer releases also accept it in days.
What is the difference between TECO and CLSD?
TECO, technically completed, means the work is done: reservations and capacities are closed and open purchase requisitions are flagged for deletion, but costs can still post. CLSD, completed for business, needs a zero balance and no open purchase orders, and after it nothing can post.
Where do maintenance costs end up?
Wherever the settlement rule says: usually the cost center of the technical object, sometimes a WBS element or a fixed asset when the work is capitalized. The settlement profile of the order type defines which receivers are allowed.
What does a maintenance order post in FI?
Nothing when it is created or released. Actual costs come from time confirmations, an internal activity allocation from the work center’s cost center; from goods issues of spare parts, movement type 261; and from goods receipts or service entry sheets for external work. Settlement then moves the total to the receiver.
What is the phase model, and do I have to use it?
A process of nine phases, from initiation to completion, that the system sets by itself. It is activated per order type and is not mandatory: classic order types keep working, and orders created before the activation stay as they were.
How do I get MTTR and MTBR in SAP?
From notifications with the breakdown indicator set and the malfunction start and duration filled in. The classic reports are MCJB for equipment and MCJC for functional locations, with MCI7 for breakdown analysis; in SAP S/4HANA, the Breakdown Analysis app (F2812) shows them per equipment.
What are measuring points and counters?
A measuring point records a condition, such as a temperature; a counter records use or wear, such as operating hours or kilometres. Each reading is a measurement document, and counters drive performance-based maintenance plans.
What is the difference between a planning plant and a maintenance plant?
The maintenance plant is where the technical objects are; the planning plant is where the work is planned. In a simple setup both are the same plant; with central planning, one planning plant serves several maintenance plants.
Why does IW38 show nothing?
Almost always the selection: the status boxes, the period or hidden selection values. Try with only the order number; if the order appears, adjust the selection and save it as a variant.
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.
- Introducing the phase modellearning.sap.com
- Costing for maintenance orderslearning.sap.com
- Settlement of maintenance orderslearning.sap.com
- Period-end closing of maintenance orders (BF7)learning.sap.com
- Confirmation and completionlearning.sap.com
- Executing maintenance orderslearning.sap.com
- Scheduling a single cycle planlearning.sap.com
- SAP GUI-based functions for single-cycle planslearning.sap.com
- Scheduling maintenance planslearning.sap.com
- Describing a maintenance strategylearning.sap.com
- Working with measuring points and counterslearning.sap.com
- Structuring and displaying technical objects and BOMslearning.sap.com
- Using Fiori apps for functional locationslearning.sap.com
- Executing a maintenance tasklearning.sap.com
- Creating and planning a maintenance tasklearning.sap.com
- Using standard service (PM03)learning.sap.com
- Implementing SAP S/4HANA Asset Managementlearning.sap.com
- Using mobile maintenancelearning.sap.com
- Exploring AI in SAP EAMlearning.sap.com
- Call horizonhelp.sap.com
- Notification typeshelp.sap.com
- Maintenance notificationhelp.sap.com
- Technical objects (CS-BD/PM-EQM)help.sap.com
- Orders (CS-SE/PM-WOC-MO)help.sap.com
- System status for ordershelp.sap.com
- Business completion of an orderhelp.sap.com
- Settling the maintenance orderhelp.sap.com
- Equipment at functional locationshelp.sap.com
- Materials planning for ordershelp.sap.com
- Overall completion confirmationhelp.sap.com
- Account grouping for movement types (VBR)help.sap.com
- Order type PM01help.sap.com
- Archiving of maintenance notifications (PM_QMEL)help.sap.com
- Highlights for Asset Management in SAP S/4HANA 2021blogs.sap.com
- Introducing SAP Asset Performance Managementblogs.sap.com
- Fiori app for Breakdown Analysis (F2812)blogs.sap.com
- Types of maintenance planscommunity.sap.com
- Maintenance orders with external procurement (PM02)community.sap.com
- Movement type 261 for PM ordersarchive.sap.com
- Price cannot be determined for internal activity (CK466)answers.sap.com
- Work orders not appearing in IW38 and IW39answers.sap.com
- Standard SAP Plant Maintenance reportscommunity.sap.com
- Plants from a maintenance perspectiveblog.sap-press.com
- Fiori apps for maintenance planningblog.sap-press.com
- SAP PM transaction codessapstack.com
- SAP PM tablessapstack.com
- SAP PM transaction codes listtestingbrain.com
- QMEL, notification header for quality and maintenancetestingbrain.com
- IW38 in German: IH-Aufträge ändernerplingo.com
- IB01, create equipment BOMerplingo.com
- SAP R/2en.wikipedia.org
- SAP Maintenance Planner agentsap.com
- Migrating from SAP Work Manager to Service and Asset Managersapinsider.org
- NR-13: boilers, pressure vessels, piping and tanksguiatrabalhista.com.br
- LC 171/2019 and ICMS credit on use and consumptionsystax.com.br
- What changes with broad credit in the tax reformjettax.com.br