QMEL table — Quality Notification Header Data
QMEL stores the header-level master and process data of quality notifications, including notification number, notification type, dates, status object, material or technical reference, organizational data, and responsible context. Notification defects, causes, tasks, activities, partners, and status history are stored in companion tables such as QMFE, QMUR, QMSM, QMMA, IHPA, JEST, and JCDS.
Verified practitioner reference for QMEL — Quality Notification Header Data, covering its real SAP role, keys and joins, diagnostic proof, S/4HANA context, common pitfalls, ownership, and related objects.
Published 20 Sept 2026· 525 words
Purpose
QMEL is the central header table for SAP Quality Management notifications. One notification can represent a customer complaint, supplier complaint, internal problem, or another configured quality-notification type. QMEL identifies the notification and its header context, while detailed defect items, causes, tasks, activities, partners, and status changes are normalized into separate application tables.
Key fields
The notification number and status object are the main technical anchors, but material, plant, dates, and notification type define the business context.
- QMNUM — quality notification number.
- QMART — notification type.
- OBJNR — status object number used with JEST/JCDS.
- Material, plant, batch, vendor, customer, or technical-object references — populated according to notification scenario.
- Creation, malfunction, reference, and completion dates/times — support chronology.
- Organizational and responsibility fields — depend on notification type and configuration.
How it joins the data model
QMFE stores defect or item records for the notification, QMUR causes, QMSM tasks, QMMA activities, and IHPA partner assignments where used. JEST gives current statuses and JCDS status history through QMEL-OBJNR. VIQMEL is a standard notification view used by list transactions and combines notification data for operational reporting.
How to read it safely
Start from QMNUM and notification type, then decide whether the question concerns the header, a defect item, a cause, task, activity, partner, or status. Do not expect child-table detail to be denormalized into QMEL. Use OBJNR for status evidence and preserve item numbers when joining item-level tables.
How to prove it in the data
For a notification that appears incomplete or has the wrong processing state, confirm the QMEL header for QMNUM, then follow the relevant child records and status object. Compare QM03/QM02 or the notification worklist with QMFE/QMUR/QMSM/QMMA and JEST/JCDS. This separates a missing child record from a header or status problem.
ECC vs S/4HANA
QMEL remains part of the Quality Management notification model in S/4HANA. Fiori quality-notification apps and CDS views can provide newer user and analytical surfaces, but the classic notification object and its normalized header/item/cause/task/activity data model continue to be relevant. Use released APIs or CDS views for new extensions where provided.
Common pitfalls
- Looking for defect-item or cause details directly in QMEL.
- Reading status text without resolving OBJNR through JEST/JCDS and status text tables.
- Joining child tables by QMNUM but ignoring item or sequence numbers.
- Assuming a notification is complete because a header completion date is filled without checking active status.
- Confusing Quality notifications with PM/CS notification views without checking notification type and application context.
Whose problem this is
Primary ownership is QM notification processing. Supplier Quality, Customer Quality, Manufacturing, PM, or other teams join according to notification type. Workflow and integration teams join when tasks, approvals, or external complaint interfaces are involved.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tables/qmelERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.