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

> Source: https://netray.co/tools/sap-qm-notification-inspection-plan-results-table-map
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Find the SAP QM table for a quality notification, inspection plan, sample or result, with key fields and the table it joins to.

## Category

sap

## Erp

SAP ECC / S/4HANA

## Audience

- SAP QM consultant
- Quality engineer
- ABAP developer

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Table

**Key:** table

**Type:** text

#### Process area

**Key:** area

**Type:** text

#### What it stores

**Key:** stores

**Type:** text

#### Key fields and joins

**Key:** keys

**Type:** text

**Rows:**

**Table:** QMEL

**Area:** Notification

**Stored:** Quality notification header (complaint, defect, problem)

**Keys:** QMNUM; parent of QMFE, QMSM, QMMA, QMUR

**Table:** QMFE

**Area:** Notification

**Stored:** Notification items (defect locations and types)

**Keys:** QMNUM, FENUM; joins to QMEL on QMNUM

**Table:** QMUR

**Area:** Notification

**Stored:** Notification causes

**Keys:** QMNUM, FENUM, URNUM; joins to QMFE

**Table:** QMSM

**Area:** Notification

**Stored:** Notification tasks (corrective and preventive)

**Keys:** QMNUM, MANUM; joins to QMEL

**Table:** QMMA

**Area:** Notification

**Stored:** Notification activities (what was done)

**Keys:** QMNUM, MANUM; joins to QMEL

**Table:** QMIH

**Area:** Notification

**Stored:** Notification header data for maintenance and quality (dates, equipment, functional location)

**Keys:** QMNUM; joins to QMEL on QMNUM

**Table:** QPGR

**Area:** Catalogs

**Stored:** Code groups of the quality catalogs

**Keys:** KATALOGART, CODEGRUPPE

**Table:** QPCD

**Area:** Catalogs

**Stored:** Codes within a code group

**Keys:** KATALOGART, CODEGRUPPE, CODE

**Table:** QPCT

**Area:** Catalogs

**Stored:** Code texts by language

**Keys:** KATALOGART, CODEGRUPPE, CODE, SPRACHE

**Table:** QPMK

**Area:** Master data

**Stored:** Master inspection characteristics (header)

**Keys:** MKMNR, VERSION, plant if plant specific

**Table:** QPMT

**Area:** Master data

**Stored:** Master inspection characteristic texts

**Keys:** MKMNR, VERSION, SPRACHE

**Table:** QMAT

**Area:** Setup

**Stored:** Inspection type setup per material and plant (activation of QM in procurement and production)

**Keys:** MATNR, WERKS, ART

**Table:** MAPL

**Area:** Inspection plan

**Stored:** Assignment of task lists (inspection plans) to materials

**Keys:** MATNR, WERKS, PLNTY, PLNNR, PLNAL

**Table:** PLKO

**Area:** Inspection plan

**Stored:** Task list header (inspection plan with type Q)

**Keys:** PLNTY, PLNNR, PLNAL

**Table:** PLPO

**Area:** Inspection plan

**Stored:** Task list operations

**Keys:** PLNTY, PLNNR, PLNKN; joins to PLKO

**Table:** PLMK

**Area:** Inspection plan

**Stored:** Inspection characteristics assigned to plan operations

**Keys:** PLNTY, PLNNR, PLNKN, KZEINSTELL; MKMNR links to QPMK

**Table:** QALS

**Area:** Inspection lot

**Stored:** Inspection lot header

**Keys:** PRUEFLOS; material MATNR, plant WERK, origin HERKUNFT

**Table:** QAVE

**Area:** Usage decision

**Stored:** Usage decision for the inspection lot

**Keys:** PRUEFLOS; joins to QALS

**Table:** QAMV

**Area:** Results

**Stored:** Inspection characteristic specifications for the lot

**Keys:** PRUEFLOS, VORGLFNR, MERKNR; joins to QALS

**Table:** QASR

**Area:** Results

**Stored:** Sample results for inspection characteristics (values per sample unit)

**Keys:** PRUEFLOS, VORGLFNR, MERKNR plus sample number

**Table:** QAMR

**Area:** Results

**Stored:** Characteristic results (summarized per characteristic)

**Keys:** PRUEFLOS, VORGLFNR, MERKNR; joins to QAMV

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use this map

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Which SAP table holds quality notifications?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

sap qm tables, sap quality management tables, sap table qm notification, sap qm table for inspection plan, sap qm table for result recording, sap table qmat, sap table qmfe, sap table qmur, sap table qmsm, sap table qmih, sap table qmma, sap qm sample table

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json