SAP PM Breakdown Notification Request Form Template
A good notification is the cheapest piece of maintenance data you will ever collect, and a bad one costs the planner a walk to the line. This form lists the fields a planner needs before keying a malfunction report in IW21.
Fill in
SAP PM Breakdown Notification Request Form Template
Maintenance Notification Request
Plant: 1000 Notification type: M2 Malfunction report Reported by: S. Alvarez, Press Line 2 operator Date and time: 2026-10-20 06:40
Technical object
Functional location: 1000-PRS-L02-HYD Equipment: 10004512 Hydraulic power unit HPU-02 Main work centre: MECH-01
Breakdown details
Priority: 2 High Breakdown indicator: Yes, equipment stopped Malfunction start: 2026-10-20 06:15 Required end date: 2026-10-20 Damage / problem: Leak - hydraulic oil at pump flange
Short text
HPU-02 oil leak, press stopped
Description and symptoms
Oil pooling under pump since start of shift. Pressure dropped from 180 bar to 120 bar. Machine stopped by operator. No injury. Spill contained with absorbent.
Safety and containment check
| Check | Yes / No | Comment |
|---|---|---|
| Equipment isolated (LOTO applied) | ||
| Injury or near miss | ||
| Spill or release contained | ||
| Production or quality impact |
Approvals
Field names follow the standard notification screen (IW21 create, IW22 change). Your system may use different notification types or catalog profiles, so adjust the dropdown values. Print it as a fallback form for when the SAP Fiori or mobile app is offline.
Automate notification intake
Optional: we review how your plant receives breakdown reports and outline a draft-for-approval workflow into SAP PM.
Optional. The tool and every export work without this. No spam.
How to use the form
Fill it in at the machine or hand it to the operator as the fallback when mobile entry is unavailable. Pick the notification type first: M1 for a request, M2 for a malfunction that has happened, M3 for an activity report. Then identify the technical object. A functional location tells the planner where, the equipment number tells them which asset, and together they drive the maintenance plant, planner group and work centre defaults in SAP.
- Always give both functional location and equipment when you know them
- Keep short text under 40 characters, it is the field that shows in lists
- Put symptoms and measured values in the long text, not the short text
- Record the malfunction start separately from the time you reported it
Why these fields matter for reliability data
Breakdown indicator, malfunction start and malfunction end are what SAP uses to calculate breakdown duration in standard PM reports. If operators leave them blank, MTTR and downtime reports are wrong for years. The damage and cause fields come from catalogs, which is how a plant moves from free text to a Pareto of failure modes. The priority field is not an urgency opinion: it maps to the priority type that sets required start and end dates on the order.
Common mistakes
The most frequent problem is a vague short text such as 'machine down' with no equipment reference. The second is a priority 1 on everything, which makes the scale meaningless. Third, planners edit the notification after the repair and overwrite the original malfunction times. Keep the original report as filed, add the findings in the order confirmation, and use the cause code to capture what you learned.
- Do not close a notification before the order is technically completed
- Do not reuse one notification for repeat failures, raise a new one
- Check the equipment is not a duplicate of an older record
Frequently Asked Questions
Which SAP PM transaction creates a notification?
IW21 creates a notification, IW22 changes it and IW23 displays it. In S/4HANA you can also use Fiori apps such as Create Maintenance Notification. The fields on this form map to both the GUI screen and the Fiori app.
What is the difference between M1, M2 and M3?
In standard SAP, M1 is a maintenance request for work needed, M2 is a malfunction report for something that has failed, and M3 is an activity report documenting work already done. Many plants define their own types, so check your configuration.
Do I need the breakdown indicator?
Set it whenever the equipment stopped or the failure caused a loss of function. SAP uses it with malfunction start and end to report breakdown duration, so it feeds your availability and MTTR numbers.
Can this replace entering data in SAP?
No. It is a capture form and a fallback. The planner still creates the notification in SAP. Its value is that every required field has already been collected, so the entry takes a minute.
If notifications arrive by email, WhatsApp or paper, Netray can build a read-and-draft agent that prepares the SAP notification for planner approval, with a human confirming every write.
Related Tools
SAP PM Measuring Point and Counter Readings Worksheet
Log counter readings for running hours or cycles, compute daily usage and the days left until a performance-based service is due.
SAPSAP PM Shutdown and Turnaround Work Package Template
A structured work package document for one job in a planned shutdown, linking the SAP order, notification, permits, parts and crew in one place.
SAPSAP PM Work Clearance and Work Permit Template
A permit-to-work form tied to a SAP maintenance order, covering isolation, hazards, authorizations and close-out signatures.
SAPSAP PM Catalog and Code Group Design Worksheet
Plan code groups and codes for damage, cause, object part and activity, so failure data becomes something you can analyze.
More SAP tools
See all- SAP QM Inspection Types Reference
- SAP QM Usage Decision Codes Worksheet
- SAP QM Sampling Procedure Design Template
- SAP QM Quality Notification Types Reference
- SAP Master Inspection Characteristic Upload Worksheet
- SAP QM in Procurement Setup Checklist
- SAP QM Inspection Lot Origins Reference
- SAP QM Dynamic Modification Rule Calculator
- SAP PM Maintenance BOM and Spare Parts Cost Worksheet