How to create a quality notification in SAP QM (QM01) and set up an 8D report
how to create quality notification in sap qm
Also searched as
- sap qm 8d report customizing
- QM01 quality notification
- sap quality notification types Q1 Q2 Q3
Short answer
Run QM01, pick the notification type (Q1 customer complaint, Q2 complaint against a vendor, Q3 internal problem), fill the header and item, then add causes, tasks and activities to track the problem to closure. An 8D report is not a separate object: it is a print form over the notification, configured in customizing.
Applies to: SAP ECC 6.0 and S/4HANA on-premise
Create and process a quality notification
- 1Run QM01 and enter the notification type: Q1 for a customer complaint, Q2 for a complaint against a vendor, Q3 for an internal problem (the standard delivered types).
- 2Enter the reference data: material, batch, plant, and for Q1 the customer and delivery, for Q2 the vendor and purchase order. Reference objects pull master data into the header.
- 3Describe the problem in the short text and long text, set the priority, required start and end dates, and the coordinator (person responsible).
- 4On the item tab enter the defect: defect type, code group and code from the catalog, and the quantity affected. An item can hold several causes.
- 5Add causes on the item, then tasks on the notification (what must be done, who, by when) and activities for what was done. Tasks are what you release and complete for closure.
- 6Save the notification. The system shows the number and the user status OSNO (outstanding). Move through statuses with the Notification menu functions as the work proceeds.
- 7Complete the notification when all tasks are done. Use IQM1 (Quality Notification List) to monitor open ones, and QM02 or QM03 to change or display one.
Q1, Q2 and Q3: choosing the right type
Q1 records a customer complaint and is normally created from a sales or delivery reference. Q2 records a problem you have with a vendor and is linked to the purchase order and the vendor, which is what supplier quality and returns teams use. Q3 covers internal problems such as in-process defects and scrap analysis.
Types are defined in customizing under Quality Management > Quality Notifications > Notification Creation > Notification Types. Each type has a screen layout, a number range, a status profile and a catalog profile. If your plant needs a custom type, copy a standard one and keep the Z or Y namespace.
Tasks, activities and the closure workflow
A task is a planned action, such as containment, corrective action or verification. A task has a processor, a due date and its own status; tasks are released and completed individually. Activities record what has been done. Splitting these correctly gives you a clean audit trail and a usable overdue report.
Some plants link the notification to a quality management workflow so that the coordinator receives a work item when a Q2 is created. Workflow is optional; the basic notification works without it.
8D report: how it fits and what you customize
The 8D method is a problem-solving structure, not a different notification type. In SAP QM an 8D report is a printed document built from the notification data: team and coordinator, problem description, containment tasks, causes, corrective actions, preventive actions and closure. SAP provides report and form objects that you assign to the notification type, and many companies modify the delivered form.
To set it up, go to the notification type settings in Quality Management > Quality Notifications and check the print program or action profile for the form, then enable the catalogs (defect, cause, task) the report prints from. Because form names differ across releases and between Smart Forms and Adobe forms, ask your Basis or forms developer which form your system uses before copying it.
To feed the eight disciplines, use tasks for D3 (containment) and D5 and D6 (corrective actions), causes for D4, and long text for D1 and D2 plus the problem description. Treat the report as the output, and train users to complete the notification in the same order.
Catalogs: the part that makes reporting work
Defect types, causes and tasks are chosen from catalogs maintained with QS41. Free-text only notifications cannot be analysed. Spend your effort on a short, consistent code list before go-live; pareto and quality score reports in the information system depend on it.
Try it here, free
SAP QM Quality Notification Types Reference
See what the standard SAP quality notification types Q1, Q2 and Q3 are for, and how related PM types differ.
Common pitfalls
- !Using Q3 for a vendor problem because it is the default, which loses the vendor link for supplier scorecards.
- !Skipping catalog codes, which makes later pareto analysis impossible.
- !Creating tasks without a processor or date, so nothing appears as overdue.
- !Printing the standard 8D form without checking which fields are mapped for your notification type.
- !Closing the notification while tasks are still open in the status profile.
How an ERP-grounded AI assistant handles this
A grounded assistant can read quality notifications and answer practical questions such as which Q2 notifications for a vendor are overdue, which defect codes recur, and what the open containment tasks are. It can also draft the 8D narrative from the notification fields for a person to review. Everything runs on your own system and models, with write actions left to users.
Frequently asked questions
What is the transaction to create a quality notification?
QM01 creates one, QM02 changes it and QM03 displays it. IQM1 lists quality notifications and IQM2 lets you change them from a list. Catalogs for defects and causes are maintained with QS41.
What is the difference between Q1, Q2 and Q3?
Q1 is a customer complaint, Q2 a complaint against a vendor and Q3 an internal problem. They are the standard delivered notification types, and you can add your own copies in customizing.
Is there a separate 8D transaction in SAP QM?
No, there is no separate 8D object. The 8D report is a form printed from the notification, built from its tasks, causes, activities and text. You configure it through the notification type and the output form assignment.
How do I monitor open quality notifications?
Use IQM1 to list notifications, filtering by type, status, plant, coordinator and dates. Tasks with overdue dates can be reviewed from the task list view for the same selection.
Related
How to Sync an NCR From Your QMS to ERP Quarantine and MRB Disposition
The reliable pattern is two events: when the NCR opens, the ERP moves or flags the affected lot or serial into a non-nettable quarantine status; when the Material Review Board closes it, the disposition (use as is, rework, repair, scrap, return to vendor) triggers exactly one matching ERP transaction. The NCR number is the key that ties both sides together.
How-toHow to Link a CAPA to ERP Lots and Serial Numbers for Containment and Effectiveness
A CAPA is only as good as its containment scope, and the scope comes from ERP genealogy: forward trace from the suspect raw material lot or process to every job, serial and shipment that consumed it, and backward trace from the failed serial to its components. Store the CAPA number against those ERP records, then use ERP rejection and return data to verify effectiveness.
How-toSAP QM inspection results report: which tcode shows what
Use QA32 for the list of inspection lots, QE51N or QE03 for recorded results, the QM information system (for example QM12) and QGC2 for evaluations of characteristics over time, and QA11 or QAVE for usage decisions. If none fits, read the tables QALS, QAMV, QAMR and QAVE directly.
How-toHow to release (and cancel) an inspection lot in SAP QM
Open the lot in QA02, check the system status, and use the Release function so the status moves from CRTD (created) to REL (released); only then can results be recorded in QE01 and a usage decision made in QA11. To cancel a lot, use the cancel function in QA02, which only works while no usage decision exists and no stock posting blocks it.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
AI for ERPAI for SAP Quality Management: Notifications, 8D, and CAPA Without the Manual Drafting
AI grounded on SAP QM data that triages notifications, drafts 8D and CAPA reports, and summarizes inspection trends, deployed on-prem for full traceability.
AI for ERPAI for NCR, CAPA, and 8D Drafting in AS9100 and ISO 9001 Quality Systems
AI drafts NCR, CAPA, and 8D reports from ERP quality data for engineer review, cutting drafting time under AS9100 and ISO 9001 without changing sign-off.
Stuck on SAP ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP QM Quality Notification Types ReferenceSee what the standard SAP quality notification types Q1, Q2 and Q3 are for, and how related PM types differ.
- SAP QM Quality Notification 8D Report TemplateAn 8D problem-solving report laid out to match the data in a SAP QM quality notification, so the document and the SAP record stay aligned.
- SAP QM Inspection Types ReferenceLook 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.
ERP fixes and how-tos
- How to Create a Selected Set in SAP QM (QS51)Create a selected set in SAP QM with QS51: pick codes from catalog code groups and use them for qualitative characteristics, usage decisions and defect recording.
- How to Create a Status Profile in SAP QM (BS02)Create a user status profile in SAP QM with BS02 and assign it to quality notifications, tasks and inspection lots, with status numbers and business transaction control.
- How to create an inspection plan in SAP QM (QP01)Create an inspection plan in SAP QM with QP01: header, operations, master inspection characteristics, sampling procedure and material assignment, plus a plan report.
AI on your ERP
- AI for SAP Quality Management: Notifications, 8D, and CAPA Without the Manual DraftingAI grounded on SAP QM data that triages notifications, drafts 8D and CAPA reports, and summarizes inspection trends, deployed on-prem for full traceability.
- AI for SAP S/4HANA in Automotive: Scheduling Agreements, Quality Notifications and Line-Side PressureAI on SAP S/4HANA for automotive suppliers: scheduling agreements, JIT/JIS, PPAP and 8D, answered from live data on your own infrastructure, read-only.