# SAP PM Notification Types Reference (M1, M2, M3) > Source: https://netray.co/tools/sap-pm-notification-types-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Look up SAP plant maintenance notification types, transactions, tables, catalog types and system statuses. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP PM consultant - Maintenance planner - SAP support 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 request **Code:** M1 **Kind:** Notification type **Notes:** Delivered type for requesting work on a technical object without a failure. Often raised by operators or planners. #### Malfunction report **Code:** M2 **Kind:** Notification type **Notes:** Delivered type for failures. Carries breakdown indicator and malfunction start and end for downtime analysis. #### Activity report **Code:** M3 **Kind:** Notification type **Notes:** Delivered type for recording work done without a prior request, such as inspections or short tasks. #### Customer notification types **Code:** Z-types **Kind:** Notification type **Notes:** Projects often add types for safety, quality or near miss so workflows and reporting stay separate. #### Create notification **Code:** IW21 **Kind:** Transaction **Notes:** Create a notification against equipment, functional location or assembly. #### Change notification **Code:** IW22 **Kind:** Transaction **Notes:** Edit text, items, causes, tasks and activities. Create an order from the notification here. #### Display notification **Code:** IW23 **Kind:** Transaction **Notes:** Read-only view of the notification and its history. #### Change notification list **Code:** IW28 **Kind:** Transaction **Notes:** List editing with selection by status, priority, planner group or dates. #### Display notification list **Code:** IW29 **Kind:** Transaction **Notes:** Read-only list for reporting and export. #### Quality notification header **Code:** QMEL **Kind:** Table **Notes:** Header of every notification, including PM types. Holds notification number, type, dates and priority. #### Quality notification items **Code:** QMFE **Kind:** Table **Notes:** Item level data such as damage code and object part. #### Quality notification causes **Code:** QMUR **Kind:** Table **Notes:** Cause records linked to items. #### Quality notification tasks **Code:** QMSM **Kind:** Table **Notes:** Task records on the notification. #### Quality notification activities **Code:** QMMA **Kind:** Table **Notes:** Activity records on the notification. #### Outstanding notification **Code:** OSNO **Kind:** System status **Notes:** Notification created and not yet taken into process. #### Notification in process **Code:** NOPR **Kind:** System status **Notes:** Work on the notification has started. #### Order assigned **Code:** NOPR+ORAS **Kind:** System status **Notes:** ORAS shows that an order is assigned to the notification. #### Notification completed **Code:** NOCO **Kind:** System status **Notes:** Notification completed. Completion usually requires the required end date and time fields. #### Deletion flag **Code:** DLFL **Kind:** System status **Notes:** Notification marked for archiving and deletion. #### Object parts **Code:** Catalog B **Kind:** Catalog type **Notes:** Catalog used to code which part of the object was affected. #### Damage **Code:** Catalog C **Kind:** Catalog type **Notes:** Catalog used to code the damage found. #### Causes **Code:** Catalog 5 **Kind:** Catalog type **Notes:** Catalog used to code the cause of the damage. #### Activities **Code:** Catalog A **Kind:** Catalog type **Notes:** Catalog used to code what was done. #### Catalog profile **Code:** Catalog profile **Kind:** Master data **Notes:** Assigned to equipment or functional location. Decides which code groups appear on notifications. #### Notification priority **Code:** Priority **Kind:** Field **Notes:** Comes from a priority type assigned to the notification type. Drives required start and end dates. #### Breakdown indicator **Code:** Breakdown **Kind:** Field **Notes:** Flags that the object was down. Used for downtime and availability reporting. #### Malfunction start and end **Code:** Malf start/end **Kind:** Field **Notes:** Dates and times used to calculate breakdown duration and MTTR reporting. #### Required start and end **Code:** Req start/end **Kind:** Field **Notes:** Planned window for the work, often derived from priority. #### Planner group **Code:** Planner group **Kind:** Field **Notes:** Group responsible for planning and often used to filter lists and workflows. **Notes:** Delivered types, status text and catalog codes vary by release and by project customizing. Check Customizing for Notification Types and catalog profiles in your own system. ## Content **Intro:** In SAP Plant Maintenance, every piece of work starts as a notification. This reference lists the delivered notification types, the transactions you use to process them, the tables behind them and the statuses you will see, so you can answer a support question or design a report faster. **Sections:** #### How to use the reference **Body:** Type a code or word to filter. Search M2 to see the malfunction report row, search QM to list the notification tables, or search Catalog to see the coding catalogs. Use the Kind column to narrow to transactions or statuses. Export the visible rows to Excel to attach to a design document or a test plan. If you are writing a query, filter by Table and use the rows as a quick reminder of which table holds the header, items, causes, tasks and activities. #### M1, M2 and M3 explained **Body:** The three delivered types map to three business events. A maintenance request, M1, asks for work when nothing is broken. A malfunction report, M2, records a failure and carries the breakdown indicator and malfunction start and end, which feed downtime and MTTR reporting. An activity report, M3, records work already done. Many plants keep these three and add types for specific workflows such as safety observations. The type controls the screen layout, the priority type, the number range, the status profile and which fields are mandatory, so plan a type per workflow instead of one type with many optional fields. #### Catalogs and why they matter **Body:** Failure analytics in SAP depends on consistent coding. A catalog profile is assigned to equipment or a functional location and decides which code groups the user can pick for object part, damage, cause and activity. If the profile is missing, users type free text and your reports have nothing to group on. Design the code groups around the failures you actually see and keep them short enough for operators to use on a handheld device. Review the top codes quarterly and retire the ones nobody uses. **Bullets:** - Assign catalog profiles at equipment class or functional location level - Limit each code group to a manageable list - Use object part plus damage plus cause for failure pattern reporting - Train planners to correct bad coding before order settlement #### Common mistakes **Body:** Typical problems are leaving breakdown and malfunction dates optional so downtime reports are empty, creating notifications without a technical object so history cannot be analysed, and using one type for everything. Another is closing notifications before the order is complete, which breaks the link between request and work. Make completion dates mandatory where you rely on them, and review status settings when you build a workflow. **Cta:** If your failure coding is inconsistent, Netray can help analyse notification text and propose clean catalog codes over your own data, on premises if required. **Faq:** #### What are the standard notification types in SAP PM? **Answer:** The delivered types are M1 maintenance request, M2 malfunction report and M3 activity report. Most projects keep these and add their own types for safety, quality or project specific workflows. Check your own Customizing for the final list. #### Which table stores PM notifications? **Answer:** The notification header is stored in QMEL. Items are in QMFE, causes in QMUR, tasks in QMSM and activities in QMMA. They are shared with quality notifications, so filter by notification type when you report on PM. #### How do I create an order from a notification? **Answer:** Open the notification in IW22 and use the function to create an order, or create the order in IW31 and enter the notification number. The status ORAS then shows that an order is assigned, and the notification keeps the link. #### What is the breakdown indicator for? **Answer:** It marks that the technical object was out of service. Together with malfunction start and end it feeds breakdown duration, availability and MTTR reports. If it is not mandatory on your malfunction type, downtime reports will often be incomplete. ## Search terms sap notification types, sap pm notification M1 M2 M3, iw21 create notification, sap malfunction report, sap maintenance request, sap qmel table, sap notification status OSNO NOPR NOCO, sap pm catalog profile --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json