SAP PM explained: asset management in SAP

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 10 October 2026 · facts checked against the SAP Help Portal, October 2026

SAP PM (Plant Maintenance) is the part of SAP that records a company's physical assets and runs the maintenance work done on them. The assets are machines, vehicles, pipelines and buildings; in S/4HANA the same area is called Asset Management, widely shortened to EAM.

On premise and in private cloud a planner still has the IW transactions beside the Fiori apps; in the public cloud edition the apps are the only way in. Around the core, SAP sells cloud extensions on BTP, chiefly SAP Asset Performance Management for condition and risk and SAP Service and Asset Manager for technicians on mobile devices. SAP documents maintenance itself in the S/4HANA application help, reachable from the Help Portal.

What is SAP PM?

SAP PM is the maintenance component of SAP ERP and S/4HANA, spoken of as PM or EAM: functional locations and equipment, maintenance notifications and orders, preventive plans, and the cost every repair carries. The codes below are its application components, with cost across all of them. Work Clearance Management (PM-WCM), the permits and lockout/tagout layer used in utilities, chemicals and oil and gas, is one of those sub-components rather than another name for PM.

Technical objects (PM-EQM)

Functional locations say where maintenance happens, equipment says what is maintained; under them hang maintenance BOMs, measuring points, counters and warranties. The structure indicator fixes the edit mask and hierarchy levels of every functional location, so changing it after go-live renumbers everything hung on it. Functional locations are created in IL01, equipment in IE01, and a piece of equipment can be installed at a location, removed and reinstalled elsewhere with its history travelling with it — the reason a pump is equipment and the position it sits in is a functional location.

Maintenance processing (PM-WOC)

A fault is reported, an order is planned with operations, spares and external services, technicians confirm time, the order closes and its cost settles.

Preventive maintenance (PM-PRM)

Task lists, strategies and their packages, time- and counter-based plans, and the scheduling run that calls the next order before failure.

Work Clearance Management (PM-WCM)

Permits, isolation and safety approval before anyone touches a live asset — standard in utilities and process industries.

The cost side

Every order settles — to a cost centre, an internal order, or a WBS element when a shutdown runs as a project — which keeps Controlling close.

A breakdown, from the first report to settlement

The corrective cycle is the spine of the area, and every consultant is expected to walk it without notes.

1. Notification. An operator reports that a conveyor has stopped: a malfunction report against the functional location or the equipment, with a damage code, the object part affected, and a breakdown flag if the asset is down. Created in IW21, and in S/4HANA just as often from a Fiori request app on a phone.
2. Order. The planner turns the notification into a maintenance order (IW31 to create, IW32 to change): operations with a work centre and planned hours, components reserved from stock, external services requested through a purchase requisition. The order is created with status CRTD and nothing can be withdrawn or confirmed against it yet.
3. Release and execution. Releasing the order (REL) prints or sends the job, lets the stores issue parts against the reservation — goods issue in MIGO with movement type 261 — and opens it for confirmation. Permits from Work Clearance Management, where used, gate this step.
4. Confirmation. Technicians confirm hours per operation (IW41, or a mobile app), together with the cause and the activity codes that make the job analysable later. Status moves to PCNF, then CNF.
5. Technical completion. TECO says the work is done: open reservations and requisitions are closed, the notification is completed, and the order waits only for its cost.
6. Settlement and close. Month-end settlement (KO88 for one order, KO8G for the collective run) moves the actual cost to the receiver in the settlement rule, and the order is closed (CLSD). Settlement is where Asset Management consultants meet Controlling, usually over an order that cannot settle because its rule is missing.

A dash means the classic transaction is still how most teams do it, not that nothing else exists; SAP's own walkthrough of the process is in the free SAP Learning course Exploring Business Processes in SAP S/4HANA Asset Management.

How does a preventive plan decide when the next order appears?

Through its cycle and its scheduling parameters: a maintenance plan calls orders on its own, and most go-live surprises in the area come from not understanding when. A single-cycle plan (IP41) repeats one interval — every three months, or every 500 operating hours read from a counter. A strategy plan (IP42) hangs several packages off one strategy, so the monthly check, the quarterly service and the annual overhaul come from a single plan and the longer package absorbs the shorter ones when they fall due together. A multiple-counter plan (IP43) calls on whichever of several conditions arrives first, such as distance or time for a vehicle.

Scheduling (IP10) turns the plan into call objects. The call horizon decides how early inside the cycle the order is created — early enough for parts and permits, late enough that the planner is not buried in orders for work months away. The scheduling period decides how far ahead calls are generated at all, and the shift factors decide whether a job completed late pushes the next due date or leaves the cycle alone, which is a regulatory question for inspected equipment rather than a preference. Deadline monitoring (IP30) runs the same logic across every plan as a background job; when it stops running, preventive maintenance silently stops too.

What is the maintenance history for?

Deciding what to fix differently next time — which it can only do if it was coded. Every notification carries catalogue codes — object part, damage, cause, activity — and those codes are the only reason the history can answer a question. With the breakdown flag and the malfunction start and end times recorded honestly, the system can report mean time between failures and mean time to repair per equipment or per class of asset, and a reliability engineer can find the pump model that fails three times as often as its neighbours. With free text instead of codes, the same ten years of history are unreadable. Designing a catalogue small enough that technicians use it and specific enough to analyse is one of the few design decisions in the area whose cost only appears years later.

The same history feeds the move from calendar-based to condition-based maintenance: measuring points and counters record what the asset actually experienced, and a plan can react to a reading rather than to a date. SAP's Asset Management overview describes where the product is heading; the prerequisite for any of it is an object structure and a catalogue that were kept clean.

How do technicians work on SAP PM work orders on a mobile device?

SAP's mobile app for maintenance work orders is SAP Service and Asset Manager, a native app for iOS and Android phones and tablets that runs on SAP Business Technology Platform Mobile Services; SAP's current overview lists Windows as well. It is built on the code line of the earlier SAP Asset Manager, so moving from one to the other is a technical upgrade. SAP's course on implementing the app, written for release 2205, lists three personas: maintenance technician, field service technician and inventory clerk. Its newer overview lesson names four: maintenance technician, logistics clerk, field service technician and a safety technician, who isolates equipment before the work starts. A maintenance technician can create and edit work orders and notifications on the device, see an order's operations, components and object list, confirm time, and take measuring-point readings. Data and business logic are held on the device, so work carries on without a network and reaches the back end at the next synchronisation. The back end can be SAP S/4HANA or SAP ERP 6.0; SAP publishes the minimum release of each.

Where a plant has no mobile project, technicians confirm in the Fiori app Perform Maintenance Jobs or in IW41. On a project, the mobile stream decides which plants and order types are sent to devices, what a technician may change, and who resolves a confirmation that fails to post. As of October 2026.

What is SAP APM (Asset Performance Management)?

SAP APM (SAP Asset Performance Management) is SAP's cloud application for deciding which assets matter most and how each should be maintained: risk and criticality assessment, reliability-centred maintenance and FMEA studies, and condition monitoring from sensor data and measuring documents. It does not replace PM. APM works out the strategy, and its recommendations go to S/4HANA as maintenance plans and task lists, where the order is still planned, confirmed and settled.

SAP introduced it in 2022 as the convergence of two earlier cloud products, SAP Asset Strategy and Performance Management (the "ASPM" still seen in adverts and searches) and SAP Predictive Asset Insights; customers on either should check their current status with SAP. SAP Business Network Asset Collaboration, called SAP Asset Intelligence Network until late 2022, is a separate product: a network on which operators, manufacturers and service providers share equipment records and documentation. The current scope is in the SAP APM documentation.

Does the work happen in the plant or in the project room?

Both, and in that order: the hierarchy is agreed by walking the plant with maintenance planners, then configured against the names they already use.

• Design weeks — workshops on the technical-object structure, notification and order types, and the damage, cause and activity catalogue that makes history analysable.
• Build and data weeks — configuration, task lists and strategies, then equipment records built from drawings, nameplates and a legacy extract: the stretch that overruns whatever greenfield, brownfield or rollout shape the programme runs.
• Test, cutover and hypercare — a notification becomes an order beside the planners, its confirmation posts hours to the right cost object, then the first scheduling runs and the backlog arrive with AMS.

Why does a maintenance order never stay inside PM?

Because it consumes parts, labour and money that other modules own. Spares and external services are ordered against the order's account assignment, so Procurement sits beside Asset Management on most teams. Project Systems appears when a turnaround is budgeted as a project; Quality Management meets it at calibration, where inspecting test equipment rides on a maintenance plan. Utilities, oil and gas, mining and rail each maintain differently, so industry depth counts here (which combinations work).

Who ends up owning Asset Management

• From maintenance itself — planners, supervisors and reliability engineers who became key users (the key-user route).
• From the shop floor — Manufacturing consultants share the plant, the work centres and the vocabulary.
• From Service — close objects, minus the entitlement check and the price that make a job billable.
• From the technical side — developers on order forms, mobile apps and hierarchy migration, who often know the data model best.

What gets read is a plant you structured: a hierarchy the planners accepted, a preventive programme taken live, an equipment load reconciled against nameplates. Questions follow that line — equipment or functional location, how a plan's call horizon behaves, where a confirmation's cost lands (what interviews test).

What is changing in maintenance work

The process core stayed; the name did not — on S/4HANA the area is Asset Management. Fiori apps ship for planner and technician tasks and mobile confirmation is a standard scope item, so how the day is tooled is a project decision, not a given. The drift toward condition-based calling rewards a clean object structure (the career effect).