SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

SAP QM Tables: Notification, Inspection Plan and Result Recording Map

SAP QM spreads quality data over a few families of tables: notification, catalogs and master data, inspection plan, and inspection lot with its results. This map groups them by process so you can find the right table and the field to join on.

Download:
TableProcess areaWhat it storesKey fields and joins
QMEL
Notification
QMNUM; parent of QMFE, QMSM, QMMA, QMUR
QMFE
Notification
QMNUM, FENUM; joins to QMEL on QMNUM
QMUR
Notification
QMNUM, FENUM, URNUM; joins to QMFE
QMSM
Notification
QMNUM, MANUM; joins to QMEL
QMMA
Notification
QMNUM, MANUM; joins to QMEL
QMIH
Notification
QMNUM; joins to QMEL on QMNUM
QPGR
Catalogs
KATALOGART, CODEGRUPPE
QPCD
Catalogs
KATALOGART, CODEGRUPPE, CODE
QPCT
Catalogs
KATALOGART, CODEGRUPPE, CODE, SPRACHE
QPMK
Master data
MKMNR, VERSION, plant if plant specific
QPMT
Master data
MKMNR, VERSION, SPRACHE
QMAT
Setup
MATNR, WERKS, ART
MAPL
Inspection plan
MATNR, WERKS, PLNTY, PLNNR, PLNAL
PLKO
Inspection plan
PLNTY, PLNNR, PLNAL
PLPO
Inspection plan
PLNTY, PLNNR, PLNKN; joins to PLKO
PLMK
Inspection plan
PLNTY, PLNNR, PLNKN, KZEINSTELL; MKMNR links to QPMK
QALS
Inspection lot
PRUEFLOS; material MATNR, plant WERK, origin HERKUNFT
QAVE
Usage decision
PRUEFLOS; joins to QALS
QAMV
Results
PRUEFLOS, VORGLFNR, MERKNR; joins to QALS
QASR
Results
PRUEFLOS, VORGLFNR, MERKNR plus sample number
QAMR
Results
PRUEFLOS, VORGLFNR, MERKNR; joins to QAMV

Key field lists show the fields most useful for joins, not every part of the primary key. Confirm in SE11 for your release. Sampling procedure tables vary by release, so look for tables starting QDP in SE11 rather than relying on a single name. The sample size itself is calculated from the sampling procedure at lot creation.

Want a quality dashboard from these tables?

We can outline a read-only view of notifications and inspection results for your plant. Optional follow-up only.

Optional. The tool and every export work without this. No spam.

How to use this map

Filter by process area first. A defect report starts in QMEL and walks to QMFE (items), QMUR (causes), QMSM (tasks) and QMMA (activities). A results report starts at QALS and walks to QAMV for characteristics and QASR for sample values. Export the filtered rows to share with whoever builds the extract.

  • Notification chain: QMEL to QMFE to QMUR, with QMSM and QMMA from QMEL.
  • Plan chain: MAPL to PLKO to PLPO to PLMK, then QPMK for the master characteristic.
  • Results chain: QALS to QAMV to QAMR and QASR, decision in QAVE.

Notification tables

QMEL is the header of a quality notification, and each notification type controls which child tables are used. Items sit in QMFE, causes in QMUR below the item, and corrective actions in QMSM and QMMA. Codes in those tables come from the quality catalogs, so join to QPCT for readable text. QMIH is mainly used where a notification carries equipment or maintenance data.

Inspection plan and result tables

An inspection plan is a task list of type Q. MAPL ties it to a material and plant, PLKO and PLPO hold header and operations, and PLMK holds the characteristics with their limits. When a lot is created the plan is copied: characteristic specifications go to QAMV and the recorded measurements go to QASR and QAMR. That copy means later plan changes do not alter old lots.

Common mistakes

People often query QALS and assume one row per characteristic, but the lot header has one row and the characteristics are in QAMV. Another mistake is reading the plan tables to report on past lots, which shows today's limits instead of the limits used at inspection. For QMAT, remember it controls whether an inspection type is active, it does not hold results.

Frequently Asked Questions

Which SAP table holds quality notifications?

QMEL holds the notification header. Items are in QMFE, causes in QMUR, tasks in QMSM and activities in QMMA. All of them join on the notification number QMNUM, and codes translate through the catalog tables such as QPCT.

Where are inspection results stored in SAP QM?

Characteristic specifications for a lot are in QAMV, summarized results in QAMR and individual sample values in QASR. The lot header is QALS and the usage decision is QAVE. All join on the inspection lot number PRUEFLOS plus the operation and characteristic numbers.

What is table QMAT used for?

QMAT stores the inspection type setup per material and plant, for example inspection type 01 for goods receipt. It decides whether SAP creates an inspection lot for that movement. It is configuration of the material, not inspection data.

Which tables hold an inspection plan?

MAPL links the plan to material and plant, PLKO is the header, PLPO holds operations and PLMK the inspection characteristics with limits. Master inspection characteristics are in QPMK. Plans use task list type Q, which separates them from routings.

If your quality team exports inspection and notification data into spreadsheets every week, we can set up a private, read-only assistant over your SAP QM data so questions get answered with the query shown.

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP