SAP Quality Notification Types Reference
Quality notifications in SAP QM record problems and drive follow up tasks. The notification type decides the screen layout, the catalogs and the partner roles. This reference lists the standard types and how they relate to the PM types.
| Notification type | Name | When to use | Module | Practical note |
|---|---|---|---|---|
Q1 | Customer complaint | A customer reports a defect or service problem on goods you delivered | QM | Typically linked to a sales order or delivery. Used for returns, credit and corrective action. |
Q2 | Complaint against vendor | You report a defect on goods or services received from a supplier | QM | Often linked to a PO and inspection lot. Feeds vendor evaluation. |
Q3 | Internal problem report | A defect found inside your own plant, process or product | QM | Common starting point for internal corrective actions and 8D style work. |
M1 | Maintenance request | A request to maintenance for a repair or inspection | PM | Created from the plant maintenance side, can start a maintenance order. |
M2 | Malfunction report | Reports a breakdown or malfunction on equipment | PM | Often used for downtime tracking in plant maintenance. |
M3 | Activity report | Documents an activity that was performed without prior planning | PM | Used to record work done after the fact. |
Notification types are customizing items and your system may have added custom types such as Z-types. Check SPRO under Quality Management, Quality Notifications, Notification Creation.
Optional notification process review
We can walk through your complaint and corrective action flow and show where SAP data can feed it.
Optional. The tool and every export work without this. No spam.
How to use this reference
Search by type letter or process. Use it when designing a complaint process, deciding which type to start a corrective action from, or explaining the difference between QM and PM notifications to a new colleague. Export the table to Excel and add your own custom types next to the standard ones so there is a single list for the team.
How notification types drive the process
A notification type fixes the number range, the screen layout, the catalog profile, the status profile and the partner determination. For quality, Q1 starts from a customer, Q2 from a vendor and Q3 from inside the plant. Each notification can carry items, causes, tasks and activities. Tasks can be assigned to users and tracked until completion, which is the core of a closed loop corrective action.
- Catalog profile controls defect, cause and task codes
- Partner functions identify customer, vendor or responsible user
- Status profile controls lifecycle such as open, in process, completed
- Reference objects link the notification to material, batch or lot
Common mistakes
Teams often create one generic type for everything, which breaks reporting, or copy catalog profiles without cleaning defect codes. Some processes also forget to link the notification to the inspection lot or vendor, so vendor evaluation cannot use it. Agree on a small set of types and a single catalog design before go live.
- Using Q3 for complaints that should be Q1 or Q2
- Custom types without matching status profiles
- Defect codes that overlap with usage decision codes
- No follow up task assigned to a responsible person
Frequently Asked Questions
Which transaction creates a quality notification?
QM01 creates a quality notification, QM02 changes it and QM03 displays it. In S/4HANA there are also Fiori apps for managing quality issues. Check your release.
Which type should I use for a supplier defect?
Use Q2, complaint against vendor, when the defect comes from a supplier. Link it to the PO or inspection lot so the notification can support vendor evaluation and claims.
Are Q1, Q2 and Q3 always available?
They are delivered in standard customizing, but projects can change or deactivate them. Confirm in your own system and check whether custom types were created.
Can a notification start a corrective action?
Yes. Tasks in the notification can represent corrective and preventive actions, and they can be assigned and tracked. Many companies also use a separate 8D or CAPA tool and link it to the notification.
Netray can add a read only AI layer to your SAP QM so quality teams ask about open notifications and recurring defects in plain language.
Related Tools
SAP QM Usage Decision Codes Worksheet
Plan usage decision code groups and codes, with valuation, stock posting and quality score, before you configure them in SAP QM.
SAPSAP QM Inspection Types Reference
Look up the standard SAP QM inspection types, what business event triggers each one and what you must set up in the material master and inspection plan.
SAPSAP QM in Procurement Setup Checklist
Check each step needed to run goods receipt inspection for purchased materials, from QM control key to vendor release.
SAPSAP QM Inspection Lot Origins Reference
See which business events create inspection lots in SAP QM and what to check when a lot is missing.
More SAP tools
See all- SAP QM Sampling Procedure Design Template
- SAP Master Inspection Characteristic Upload Worksheet
- SAP QM Dynamic Modification Rule Calculator
- SAP PM Breakdown Notification Request Form Template
- SAP PM Measuring Point and Counter Readings Worksheet
- SAP PM Maintenance BOM and Spare Parts Cost Worksheet
- SAP PM Work Clearance and Work Permit Template
- SAP PM Spare Parts Kitting and Reservation Worksheet
- SAP PM Catalog and Code Group Design Worksheet