# Overdue Quality Notifications and Open Tasks Report

> 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.

- Type: Report, Custom development, ALV report
- Module: QM
- Estimated effort: S (3–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/overdue-quality-notifications-and-open-tasks-report/


## 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.

### Closest standard alternatives

- QM10: Lists quality notifications; delay against the required end and task status are not on the same line.
- QM12: Lists tasks; does not combine them with the priority, customer and delay of the notification.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| QMEL | Notification: type, priority, material, vendor, customer, dates and required end (driving table) | Read | - | ECC + S/4 |
| JEST | System status of the notification; completed notifications are skipped | Read | JEST-OBJNR = QMEL-OBJNR AND JEST-INACT = ' ' | ECC + S/4 |
| TJ02T | System status text | Read | TJ02T-ISTAT = JEST-STAT AND TJ02T-SPRAS = SY-LANGU | ECC + S/4 |
| QMSM | Tasks: code, text, planned finish, completion and owner | Read | QMSM-QMNUM = QMEL-QMNUM | ECC + S/4 |
| LFA1 | Vendor name | Read | LFA1-LIFNR = QMEL-LIFNUM | ECC + S/4 |
| KNA1 | Customer name | Read | KNA1-KUNNR = QMEL-KUNUM | ECC + S/4 |
| I_QltyNotificationTask | In S/4HANA it can replace QMSM with a clean core approach | Read | QualityNotification = QMEL-QMNUM | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_QMART | Notification type | Range / multiple | QMEL-QMART | Yes |
| S_WERK | Plant | Range / multiple | QMEL-MAWERK | No |
| S_QMDAT | Notification date | Range / multiple | QMEL-QMDAT | No |
| S_LIFNUM | Vendor | Range / multiple | QMEL-LIFNUM | No |
| S_KUNUM | Customer | Range / multiple | QMEL-KUNUM | No |
| S_PRIOK | Priority | Range / multiple | QMEL-PRIOK | No |
| P_KEYDT | Key date (default: today) | Single value | SY-DATUM | Yes |
| P_ONLYOD | Overdue only | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Notification | QMEL-QMNUM |
| Type | QMEL-QMART |
| Description | QMEL-QMTXT |
| Priority | QMEL-PRIOK |
| Material | QMEL-MATNR |
| Vendor | QMEL-LIFNUM |
| Customer | QMEL-KUNUM |
| Notification date | QMEL-QMDAT |
| Required end | QMEL-LTRMN |
| Days overdue | Calculated: Key date − QMEL-LTRMN |
| Open tasks | Calculated: Number of QMSM tasks without ERLDAT and not deleted |
| Overdue tasks | Calculated: Open tasks with QMSM-PETER < key date |
| Next overdue task | QMSM-MATXT |
| Task planned finish | QMSM-PETER |
| Task owner | QMSM-PARNR |

## How does the report work?

1. QMEL is read with the notification type, plant, notification date, vendor, customer and priority from the selection screen.
2. 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.
3. Days overdue = key date − QMEL-LTRMN (required end). With "Overdue only" selected, only positive values remain.
4. 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.
5. Vendor and customer names are added from LFA1 and KNA1; the list is sorted by priority and days overdue.

## Authorization objects

- Q_QMEL: Quality 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=qm-overdue-quality-notifications
