SAPFree referencePDF, Excel, Word exportSAP S/4HANADiscrete Manufacturing

SAP QM Database Tables Reference (QALS, QAVE, QMEL and More)

This reference lists the SAP QM tables you meet most often when writing reports, CDS views, extractors or data migration programs. Search by table name or by what the table stores and export the result to Excel for your design document.

Download:

Table	What it stores	Main fields	QM area
QALS	Inspection lot record (header data of the lot)	PRUEFLOS, WERK, MATNR, ART, HERKUNFT, LOSMENGE	Inspection lot
QAVE	Inspection processing: usage decision data	PRUEFLOS, VCODE, VCODEGRP, VDATUM	Usage decision
QAMV	Characteristic specifications of the inspection lot	PRUEFLOS, VORNR, MERKNR, VERWMERKM	Results
QAMR	Characteristic results during inspection processing	PRUEFLOS, VORNR, MERKNR	Results
QAPP	Inspection points of the lot	PRUEFLOS, VORNR	Inspection lot
QMAT	Inspection type setup per material and plant	ART, MATNR, WERKS	Master data
QINF	QM info record for procurement (material, vendor, plant)	MATNR, LIEFERANT, WERK	QM in procurement
MARC	Plant data for material, including QM fields QMATV, SSQSS and QMATA	MATNR, WERKS	Master data
QMEL	Quality notification header	QMNUM, QMART, MATNR, MAWERK, QMDAT	Notification
QMFE	Quality notification items (defects)	QMNUM, FENUM, FEGRP, FECOD	Notification
QMUR	Quality notification causes	QMNUM, FENUM, URNUM	Notification
QMSM	Quality notification tasks	QMNUM, MANUM	Notification
QMMA	Quality notification activities	QMNUM, MANUM	Notification
QPMK	Master inspection characteristics (general data)	MKMNR, ZAEHLER	Master data
QPMT	Master inspection characteristic texts	MKMNR, SPRACHE	Master data
QPGR	Code groups of the QM catalogs	KATALOGART, CODEGRUPPE	Catalogs
QPGT	Code group texts	KATALOGART, CODEGRUPPE, SPRACHE	Catalogs
QPCD	Codes within code groups	KATALOGART, CODEGRUPPE, CODE	Catalogs
QPCT	Code texts	KATALOGART, CODEGRUPPE, CODE, SPRACHE	Catalogs
MAPL	Assignment of task lists to materials	PLNTY, PLNNR, PLNAL, MATNR, WERKS	Inspection plan
PLKO	Task list header (inspection plan header)	PLNTY, PLNNR, PLNAL	Inspection plan
PLPO	Task list operations	PLNTY, PLNNR, PLNKN	Inspection plan
PLMK	Inspection characteristics of the task list	PLNTY, PLNNR, PLNKN, MERKNR	Inspection plan
JEST	Individual object status (links to QALS and QMEL through OBJNR)	OBJNR, STAT, INACT	Status

Field lists are the main fields only, not the full table definition. Confirm exact fields and keys for your release in SE11 or SE16N before you build a report or a migration object. Table names are the same in ECC and S/4HANA unless noted in your release notes.

Want these tables queried in plain language?

An optional review of how read-only natural-language access to your SAP QM data could work on-premises.

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

How to use the table list

Type part of a table name or a business word such as usage decision or notification in the search box. Each row shows what the table holds and the fields you normally join on. Export the filtered rows to Excel or PDF and attach them to a functional specification so developers and testers start from the same list. Always verify the field list in SE11 for your release, because custom append structures and newer releases add fields that this reference does not show.

How the QM tables fit together

The inspection lot in QALS is the anchor. The lot number PRUEFLOS links to the characteristic specifications in QAMV, the results in QAMR, inspection points in QAPP and the usage decision in QAVE. Material setup comes from QMAT and MARC, and the inspection plan behind the lot comes from MAPL, PLKO, PLPO and PLMK. Notifications live in QMEL with items, causes, tasks and activities in separate tables joined by QMNUM. Status is not stored in the QM tables themselves but in JEST through the object number OBJNR.

QALS to QAVE: one usage decision per lot, join on PRUEFLOS
QALS to QAMV and QAMR: join on PRUEFLOS and VORNR
QMEL to QMFE: join on QMNUM, add MANDT in native SQL
QALS and QMEL to JEST: join on OBJNR for status

Worked example: lots with a rejected decision

A quality engineer wants all lots for plant 1000 that ended with a rejection code last month. The query starts at QALS filtered on WERK and the creation date, joins QAVE on PRUEFLOS and filters on the usage decision code group and code that your catalog uses for rejection. Because code groups are customer defined, the filter values come from your own QPGR and QPCD entries, not from a standard list. Joining JEST on OBJNR lets you exclude lots that carry a deletion flag.

Common mistakes

Most defects in QM reports come from the same few habits. Avoid them and your numbers will match what users see in transactions such as QA32 and QM03.

Reading results from QAMR without joining the specification in QAMV
Forgetting MANDT when using native SQL on HANA
Treating a status as a column instead of reading JEST
Hard coding code groups instead of reading them from QPGR and QPCD
Ignoring archived data, which is no longer in the active tables

Frequently Asked Questions

Which table stores the usage decision in SAP QM?

The usage decision data is stored in table QAVE, keyed by the inspection lot number PRUEFLOS. It holds the code group, the code and the decision date. The lot header itself is in QALS, so most reports join QALS to QAVE on PRUEFLOS.

Where are SAP QM inspection results stored?

Characteristic results are stored in QAMR, with the matching specification in QAMV. Both are keyed by inspection lot, operation and characteristic number. Single value results are stored in a related table, so check SE11 for your release if you need individual readings.

How do I find the status of a quality notification in tables?

Statuses are not columns in QMEL. QMEL carries an object number OBJNR, and the active statuses for that object are rows in JEST. Join on OBJNR and read the STAT column, then translate the status codes using the status text tables.

Are the QM table names different in S/4HANA?

The core QM tables such as QALS, QAVE and QMEL keep their names in S/4HANA, and material master tables follow the simplifications of your release. Confirm field lengths such as the material number in SE11, because S/4HANA allows longer material numbers.

If you need these tables exposed as a governed, read-only data model that quality people can query in plain language, we can build that on top of your SAP system, on-premises if required.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools