SAP QM explained: quality management

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 10 October 2026 · facts checked against the SAP Help Portal, October 2026

SAP Quality Management — SAP QM — is the component of SAP ERP and S/4HANA that decides what gets inspected, records the result and holds or releases the stock: inspection plans, inspection lots and their usage decisions, notifications and certificates. It sits inside the logistics chain, not beside it: goods receipt, production order and delivery each carry a checkpoint.

QM has never been sold on its own. It ships inside every edition of SAP S/4HANA, from on premise through private cloud to the public cloud, and only the way users reach it differs: the QA and QE transactions are still there in the first two, while the public cloud offers Fiori apps alone. SAP publishes the Quality Management pages inside the S/4HANA library of its Help Portal.

What is SAP QM?

SAP QM is the inspection and complaint-handling layer of the SAP core — what a plant calls quality control or quality assurance, and what job adverts still call the QM module. It does three jobs. It plans: which materials are inspected, at which event, against which characteristics, with what sample. It executes: a lot is created, results and defects are recorded, and a usage decision frees, blocks or scraps the stock. And it records the aftermath: notifications for complaints and internal problems, certificates that leave with a delivery, and a quality history per supplier and per batch that the rest of the company reads. None of that is optional in pharma, food, automotive or aerospace, which is why QM work concentrates where a regulator or a customer demands documented proof.

What are the QM objects?

Five, and the transactions that create them sit in the table below.

• Inspection planning and control — master inspection characteristics, methods, sampling procedures, catalogs and inspection plans; control charts, the quality level, and the dynamic modification rules that skip inspections once a source proves itself.
• The inspection lot — raised at a goods receipt, inside a production order, by deadline monitoring on a batch, off a calibration order or before a delivery; then results, defects and the usage decision that frees, blocks or scraps it.
• Notifications and certificates — supplier and customer complaints (the customer ones often arriving as service tickets in SAP Service) and internal problems, with tasks, causes and the 8D structure a customer may demand; and the profile behind the certificate of analysis leaving with a delivery.
• Quality in procurement — the QM control key on the material master, quality info records that release or block a supplier, and invoice blocking until the usage decision.
• Test equipment, batches and signed records — calibration falling due as a lot, results written to batch classification, and digital signatures on results recording and the usage decision where a regulated process demands a signed record.

Where the app column is empty, on-premise teams still work in the transaction; in the public cloud every row is a Fiori app.

How does an inspection lot run, from goods receipt to stock release?

In seven steps, and the incoming inspection on a purchased material is the chain every QM consultant is expected to walk without notes.

1. Goods receipt. The stores post the receipt against the purchase order in MIGO with movement type 101. Because the material's QM view is active, the quantity lands in quality inspection stock, not in unrestricted stock.
2. Lot creation. Inspection type 01 — goods receipt from purchase order — is active on the material, so the system creates the inspection lot automatically, reads the inspection plan, and determines the sample from the sampling procedure and the current quality level.
3. Results recording. The lab or the inspector opens the worklist in QE51N and records a value or a valuation per characteristic; the system valuates each against its specification.
4. Defects. A rejected characteristic can record a defect with a code from the catalog, and a defect can raise a quality notification to the supplier while the lot is still open.
5. Usage decision. Someone with the authority — that design decision is argued in every workshop — records the decision in QA11, or from the worklist in QA32: accepted, accepted with concessions, rejected.
6. Stock posting. From the usage decision screen the quantity is posted out of quality inspection: to unrestricted stock with movement type 321, to blocked stock, to scrap, or back to the supplier as a return delivery.
7. Invoice release. If the QM control key blocks the invoice, the supplier's invoice has been held in invoice verification with a quality blocking reason. An acceptance usage decision lifts that reason, and the next run of the blocked-invoice release, MRBR, frees the invoice for payment, unless someone releases it by hand first.

The same chain runs with different triggers: inspection type 03 inside a production order, 04 at the receipt from production, 09 for the recurring inspection of a batch, 10 before a delivery, 14 for calibration, and 89 for a lot raised by hand in QA01. What changes is who records and who decides; what does not change is that stock waits for the decision.

What is the difference between an inspection lot origin and an inspection type?

The origin is fixed by SAP and names the business event that raised the lot. The inspection type is customizing: each type belongs to one origin, is assigned and activated per material in the quality view of the material master, and carries the rules for that inspection, such as whether a plan is needed and how the sample is worked out. One origin can carry several types, so a plant can treat a first delivery from a new supplier differently from a routine receipt. If no type of the matching origin is active on the material, the event passes and no lot is created, which is the usual answer to "why did nothing happen at goods receipt?".

What are the quality notification types in SAP QM?

SAP delivers six, in three pairs. Q1 is a customer complaint, Q2 a complaint against a supplier and Q3 an internal problem notification; someone creates these by hand when a problem is reported, for instance when a customer calls. F1, F2 and F3 are the customer-related, supplier-related and material-related defect notifications, raised out of defect recording during an inspection: a failed characteristic at goods receipt becomes an F2 without leaving results recording.

Every type is processed the same way. The problem is described and linked to its material, batch or delivery; immediate activities record what was already done to contain it; tasks tell a named processor what to do and by when; defects are recorded with their causes; and the notification is completed, which the system refuses while a task is still open. Regulated plants add a digital signature to the status changes. SAP's own course for QM users, on SAP Learning, walks a supplier complaint and a customer complaint step by step.

What does a week in SAP QM look like?

A week in SAP QM follows the project phase, and one argument runs through every phase: which checkpoint is worth the delay it costs, and who may release stock that failed.

Design

Workshops with quality managers, lab staff and the line turn a written procedure into plans and catalogs.

Build

Inspection types per material, sampling, notification types, certificate profiles, and specs for forms and interfaces.

Test

Integration cycles run the chain — receipt, lot, result, usage decision, stock — while you trace why a lot appeared, or did not.

Cutover

Stock arrives already in quality inspection, batches carry statuses, and someone decides where inspections still open finish: in the legacy system, or as lots raised after the load (how projects are phased).

After go-live

The first complaint routed as a notification, the first certificate a customer rejects, and the questions that arrive after the team shrinks to AMS.

Which documents create a lot?

Someone else's, mostly: the goods receipt, the production order and the outbound delivery each belong to a neighbouring area, so QM is usually staffed alongside another area rather than on its own (which combinations work).

The goods receipt

Procurement owns the receipt that raises incoming inspection, and the supplier release that can waive it.

The production order

In-process inspection lives inside Manufacturing's order — QM's closest border.

The outbound delivery

Sales carries the certificate out and the complaint back; Supply Chain & Logistics moves stock not yet free to use.

The triggers QM owns

Calibration lots fall due from a maintenance plan kept in Asset Management, and recurring inspection from deadline monitoring on the batch.

Where do QM people come from?

From the quality function first — QA engineers, inspection supervisors and quality managers who own the procedure — then from the key-user seat (the key-user route), from PP and MM consultants who kept meeting inspection, from validation and compliance people in regulated industries, and from developers behind certificate forms and lab interfaces. What gets someone hired is one inspection chain described end to end: the material, who decides, what happens when the result is bad. Interviewers probe there — what a usage decision posts, why an invoice sits blocked, when a skip rule stops being safe (what interviews test).