Overdue Quality Notifications and Open Tasks Report
Short answer: A custom ALV report that lists open quality notifications with the days past the required end date, the number of open and overdue tasks, and the next overdue task with its owner. Quality managers see, sorted by priority, which corrective action is pending on customer and vendor complaints.
- Estimated effort
- S · 3–4 working days
- System
- ECC and S/4HANA
- Tables
- 7
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
QM10 lists notifications and QM12 lists tasks separately. Neither shows the delay of the notification against its required end date, the delay of its tasks against their planned finish and the owner on the same line. Which notification has passed the response time promised to the customer is therefore tracked by hand.
Who uses it? Quality managers, customer and supplier quality engineers, and owners of corrective actions.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| QMELNotification Header | Notification: type, priority, material, vendor, customer, dates and required end (driving table) | — | ECC + S/4 |
| JESTIndividual Object Status | System status of the notification; completed notifications are skipped | JEST-OBJNR = QMEL-OBJNR AND JEST-INACT = ' ' | ECC + S/4 |
| TJ02TSystem Status Texts | System status text | TJ02T-ISTAT = JEST-STAT AND TJ02T-SPRAS = SY-LANGU | ECC + S/4 |
| QMSMNotification Tasks | Tasks: code, text, planned finish, completion and owner | QMSM-QMNUM = QMEL-QMNUM | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor name | LFA1-LIFNR = QMEL-LIFNUM | ECC + S/4 |
| KNA1Customer Master (General Section) | Customer name | KNA1-KUNNR = QMEL-KUNUM | ECC + S/4 |
| I_QltyNotificationTaskQuality Notification Task | In S/4HANA it can replace QMSM with a clean core approach | QualityNotification = QMEL-QMNUM | S/4HANA only |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_QMART | Notification type | Range / multiple | QMEL-QMART | Yes | Q1 |
| S_WERK | Plant | Range / multiple | QMEL-MAWERK | No | 1000 |
| S_QMDAT | Notification date | Range / multiple | QMEL-QMDAT | No | 01.01.2026 – 17.11.2026 |
| S_LIFNUM | Vendor | Range / multiple | QMEL-LIFNUM | No | 100512 |
| S_KUNUM | Customer | Range / multiple | QMEL-KUNUM | No | 200310 |
| S_PRIOK | Priority | Range / multiple | QMEL-PRIOK | No | 1 |
| P_KEYDT | Key date (default: today) | Single value | SY-DATUM | Yes | 17.11.2026 |
| P_ONLYOD | Overdue only | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Notification | QMEL-QMNUM |
| 2 | Type | QMEL-QMART |
| 3 | Description | QMEL-QMTXT |
| 4 | Priority | QMEL-PRIOK |
| 5 | Material | QMEL-MATNR |
| 6 | Vendor | QMEL-LIFNUM |
| 7 | Customer | QMEL-KUNUM |
| 8 | Notification date | QMEL-QMDAT |
| 9 | Required end | QMEL-LTRMN |
| 10 | Days overdue | Calculated Key date − QMEL-LTRMN |
| 11 | Open tasks | Calculated Number of QMSM tasks without ERLDAT and not deleted |
| 12 | Overdue tasks | Calculated Open tasks with QMSM-PETER < key date |
| 13 | Next overdue task | QMSM-MATXT |
| 14 | Task planned finish | QMSM-PETER |
| 15 | Task owner | QMSM-PARNR |
Sample output
| Notification | Type | Description | Priority | Material | Vendor | Customer | Notification date | Required end | Days overdue | Open tasks | Overdue tasks | Next overdue task | Task planned finish | Task owner |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 000300001245 | Q1 | Moisture stain on packaging | 1 | FG-2050 | 200310 | 10/14/2026 | 10/28/2026 | 20 | 3 | 2 | Root cause analysis (8D D4) | 10/24/2026 | KALITE03 | |
| 000300001260 | Q2 | Paint viscosity out of tolerance | 2 | RM-3105 | 100512 | 10/29/2026 | 11/12/2026 | 5 | 2 | 1 | Request 8D report from vendor | 11/07/2026 | TEDARIK01 | |
| 000300001271 | Q1 | Wrong batch number on label | 2 | FG-1002 | 200145 | 11/05/2026 | 11/15/2026 | 2 | 1 | 1 | Correct the label template | 11/13/2026 | KALITE01 |
How does the report work?
- QMEL is read with the notification type, plant, notification date, vendor, customer and priority from the selection screen.
- The system status is read from JEST (QMEL-OBJNR, INACT blank); completed notifications and those flagged for deletion are skipped. Status texts come from TJ02T.
- Days overdue = key date − QMEL-LTRMN (required end). With “Overdue only” selected, only positive values remain.
- Tasks are read from QMSM: tasks without a completion date (ERLDAT) and without a deletion flag are open; those with a planned finish (PETER) before the key date are overdue. The text, planned finish and owner (PARNR) of the earliest overdue task are added to the line.
- Vendor and customer names are added from LFA1 and KNA1; the list is sorted by priority and days overdue.
Performance notes
Narrow QMEL by notification type and date range. Read JEST once with the list of object numbers; read QMSM with FOR ALL ENTRIES on the notification list.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the notification number opens QM03.
- Export to Excel
- Runs as a background job
- Send the result by email Each task owner can receive their own overdue tasks weekly.
Authorization objects
- Q_QMELQuality notification display authorization by notification type
Frequently asked questions
Can the 8D steps be tracked one by one?
Yes. If the 8D steps are defined as task codes (e.g. D1–D8), the report can be extended to show open/completed and delay for each step as columns.
What about notifications without a required end date?
Their delay cannot be calculated; the days since the notification date are shown instead. If a priority and response profile are set for the notification type, the required end is filled automatically.
Does the report work on S/4HANA?
Yes. QMEL, QMSM and JEST keep the same structure in S/4HANA; for clean core, I_QltyNotification and I_QltyNotificationTask can be used.
Packages that include this solution
Quality Management Control Pack
A five-report pack for the weekly quality meeting: inspection lots awaiting a usage decision, decisions made before all results were recorded, blocked …
Related reports
Customer Complaints Traced to Delivery, Batch and Inspection Lot Report
A custom ALV report that shows customer complaint notifications on the same line as the delivery, the batch, the inspection lot of that batch, its …
Vendor Quality Scorecard and Rejection Rate (PPM) Report
A custom ALV report that shows, per vendor and material, the lot rejection rate from goods receipt inspection lots, the rejected quantity in parts per …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.