Lesson 1 of 5
Maintenance in SAP S/4HANA: what the business actually does
11 min
Listen to this lesson
Every plant has machines that break, wear out and need inspection. Asset Management in SAP S/4HANA is the application area that records those machines, the work done on them, the people, parts and services the work consumed, and what it all cost. Long-time SAP users still call it Plant Maintenance or PM, and you will see that name in Customizing, in transaction descriptions and in many older documents. Current SAP learning material talks about SAP S/4HANA Asset Management and its Maintenance Management processes. They are the same thing; this track uses both names. Underneath, the objects keep their PM identity: the application component is still PM, orders are maintenance orders such as PM01, and the tables are the familiar ones (notifications in QMEL/QMIH, orders in AUFK/AFIH, equipment in EQUI, functional locations in IFLOT). You will also hear EAM (enterprise asset management): SAP uses it for the wider portfolio, which adds cloud solutions such as SAP Asset Performance Management for asset health and reliability on top of maintenance in SAP S/4HANA.
At Contoso Motor Co., the Detroit plant (1710) winds rotors and assembles alternators. If the rotor winding machine on line 1 stops, alternators stop. Rosa, the Detroit maintenance planner and the Asset Management key user on the S/4HANA program, puts it simply: "Production makes the alternators. We make sure production can." This course follows Rosa's team through the system as Contoso converts from SAP ECC 6.0 EHP 8 to SAP S/4HANA Private Edition.
The kinds of maintenance
| Type | What triggers the work | Contoso example |
|---|---|---|
| Corrective | Something is wrong: a malfunction, damage or a request for a change | The winding machine trips its motor breaker; an operator reports it and a planned repair follows |
| Emergency | A breakdown that must be fixed now, with planning reduced to a minimum | The line 1 compressed air supply fails during a shift; the technician repairs first and documents during or after |
| Preventive, time-based | A fixed interval has passed | The air compressor is serviced every three months |
| Preventive, performance-based | A counter reaches a value, such as operating hours | The winding machine spindle is overhauled every 2,000 operating hours |
| Condition-based | A measured condition leaves its allowed range | Bearing temperature above the limit triggers an inspection |
| Predictive | A model predicts a failure from sensor data | Not in scope for Contoso's conversion; a later initiative |
Maintenance types and how each one starts.
SAP's own learning material describes the standard corrective process (SAP Best Practices scope item BH1) as six steps: create the notification, plan the order, check and release it, execute, confirm, and complete. Scheduling the work is optional. The simplified emergency process (scope item BH2) collapses most of those steps into one app, Report and Repair Malfunction, so a technician can report, plan, do and document a breakdown in one place.
- NotificationSomeone reports a problem or requests work on a machine
- PlanningAn order is created with operations, work centers and spare parts
- Check and releaseMaterials and permits are checked; the order is released for work
- ExecutionTechnicians do the work; parts are issued from stock
- ConfirmationHours and findings are recorded against the order and notification
- CompletionTechnical completion, then settlement of costs and business completion
Two ways to organize the work
SAP S/4HANA also offers a phase model for maintenance, with scope items for reactive (4HH), proactive (4HI), improvement (4VT) and operational and overhead maintenance (4WM). The phase model walks a request through initiation, screening, planning, approval, preparation, scheduling, execution, post-execution and completion, and its Fiori apps show each order's phase. Contoso decided to keep the classic notification-and-order process in the conversion, because that is what its ECC users know, and to evaluate the phase model after go-live. If your program adopts the phase model, the objects in this track are the same; the screens and the approval steps differ.
What would you do?
Grace asks Rosa which maintenance process to put first in the conversion test plan. Detroit runs about 60 corrective orders and 40 preventive orders a month, and breakdowns of the winding machine stop alternator output. What should Rosa answer?
| Name you will hear | What it means | Where you see it |
|---|---|---|
| Plant Maintenance (PM) | The ECC name, still the application component | Customizing, transaction descriptions, older documents |
| Asset Management / Maintenance Management | SAP S/4HANA's name for the area and its processes | SAP Help Portal, SAP Learning, Fiori roles |
| Enterprise asset management (EAM) | The broader portfolio, including cloud solutions | SAP product pages, roadmaps |
| SAP Asset Performance Management | Cloud solution for asset health, criticality and reliability strategies | Post-go-live roadmaps, not Contoso's conversion scope |
One area, several names: who uses which, and why it matters when you search for documentation.
- Asset Management in SAP S/4HANA is the former Plant Maintenance (PM); both names are in use.
- Corrective work starts from a problem; preventive work starts from a time interval or a counter; condition-based work starts from a measured value.
- The standard corrective process runs notification, order, release, execution, confirmation and completion; the emergency process does most of it in one app.
- Test the processes your plant runs, in order of business impact.
Check your understanding · not graded
Lesson check
1. What is a common older name for SAP S/4HANA Asset Management?
2. A compressor is serviced every three months regardless of its condition. Which type of maintenance is that?
3. What is special about the simplified emergency maintenance process (BH2)?
4. Which event starts performance-based preventive maintenance?