SAP Reference

QMEL

transaction S/4HANA status: Active

Quality Notification

Identity
Module: QM · Quality ManagementType: transparent
Key fields

MANDT · QMNUM

All 4 fields
What the badges mean
S/4HANA status: Active
Active and unchanged in S/4HANA.
S/4HANA status: Deprecated
Still readable today, but no longer SAP's strategic path — plan around it.
S/4HANA status: Replaced
Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
S/4HANA status: Migrating to IBP
Planning scope is moving from APO toward IBP.
S/4HANA status: Active (StRM) · Replaced (EWM)
Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
S/4HANA status: Replaced · Compat View
Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
S/4HANA status: Active · Proxy View
Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.
master
Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).
Linked type codes

CLNT — the client key; filter it explicitly and carry it through every join.

NUMC — fixed-width numeric text; keep it a string and keep the leading zeros.

DATS, TIMS — character date (YYYYMMDD) and time (HHMMSS), zero-filled when initial.

CURR, CUKY, QUAN, UNIT — amounts and quantities, meaningful only beside the currency key or unit that qualifies them.

LANG — a language key in a text table — one row per language.

In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.
Modeling guide
Quality — What was inspected, what was decided, and what was reported?

What QMEL is for

One row per quality notification (QM01/QM02) — a complaint, an internal problem report, a vendor issue; QMART types them. The notification is a container: the analytical payload hangs beneath it in QMFE (defects), QMUR (causes), QMSM (tasks), QMMA (activities).

Joins that work — and the traps

  • Children on (MANDT, QMNUM) plus their own item counters

    Aggregate children to notification grain before joining upward, or counts multiply.

    QMFEQMURQMSMQMMA

  • PRUEFLOS links lot-origin notifications back to QALS

    The complaint and the inspection lot meet on the lot number.

    QALS

  • The vendor field is LIFNUM here

    Not LIFNR as on QALS; joins written against one table's naming break on the other.

What QMEL does not contain

No defect codes (QMFE, decoded via QPCD/QPCT); no inspection results; no stock quantities — a notification about a bad batch does not know how much stock is affected (the lot does).

What breaks in practice

  • Grain confusion is the whole game: notifications, defects, and causes are three different counts, and "defects by vendor" triples when all three levels are joined flat.
  • Not every notification has a lot: manually raised complaints carry no PRUEFLOS; lot-based joins silently drop them from complaint metrics.

Shape & growth

Grows with complaints, not with production — small next to lots; the fan-out tables multiply by defects-per-notification.

ECC vs S/4HANA

No simplification-list entry restructuring the QMEL family shows up in published material — an absence, not an SAP statement; verify against the simplification list for your release.

Fields

4 fields · 2 key

4 fields.

Table fields: key flag, field name, description, data type (linked to the data quirks guide where the type carries a known trap), length, and check-table references. 4 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3
Primary keyQMNUMQuality Notification NumberCHAR12
QMARTNotification TypeCHAR2
MATNRMaterial NumberCHAR18 / 40MARA

Lengths shown as ECC / S/4HANA where the extended material number applies.

Linked type codes in the Type column jump to the matching section of the SAP data quirks guide.

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading QMEL on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

3 parameters not filled: <catalog>, <schema>, <MANDT>

-- ============================================================
-- Table  : QMEL Quality Notification
-- Purpose: Column-selected read of QMEL — auto-generated from field metadata
-- Grain  : One row per QMNUM
-- Notes  : Auto-generated skeleton. For multi-table transaction query patterns, see the linked t-codes on this page. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  h.MANDT AS "Client",
  h.QMNUM AS "Quality Notification Number",
  h.QMART AS "Notification Type",
  h.MATNR AS "Material Number"
FROM <catalog>.<schema>.qmel h
WHERE
  h.MANDT = '<MANDT>'
ORDER BY h.QMNUM;

Verified August 2026

More query patterns: QM01 QM02 QM03

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

  • QMELQMFEheader item · 1:N
    ON qmel.QMNUM = qmfe.QMNUM
  • QMELQMSMheader item · 1:N
    ON qmel.QMNUM = qmsm.QMNUM
  • QMELQMURheader item · 1:N
    ON qmel.QMNUM = qmur.QMNUM
  • QMELQMMAheader item · 1:N
    ON qmel.QMNUM = qmma.QMNUM

Transaction Codes That Use This Table

R read · W write · R/W read + write

More Quality Management tables