QM Report Custom development ALV report

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

  • QM10 Change List of Quality Notifications. Lists quality notifications; delay against the required end and task status are not on the same line.
  • QM12 Change List of Tasks. Lists tasks; does not combine them with the priority, customer and delay of the notification.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
QMELNotification HeaderNotification: type, priority, material, vendor, customer, dates and required end (driving table)—ECC + S/4
JESTIndividual Object StatusSystem status of the notification; completed notifications are skippedJEST-OBJNR = QMEL-OBJNR AND JEST-INACT = ' 'ECC + S/4
TJ02TSystem Status TextsSystem status textTJ02T-ISTAT = JEST-STAT AND TJ02T-SPRAS = SY-LANGUECC + S/4
QMSMNotification TasksTasks: code, text, planned finish, completion and ownerQMSM-QMNUM = QMEL-QMNUMECC + S/4
LFA1Vendor Master (General Section)Vendor nameLFA1-LIFNR = QMEL-LIFNUMECC + S/4
KNA1Customer Master (General Section)Customer nameKNA1-KUNNR = QMEL-KUNUMECC + S/4
I_QltyNotificationTaskQuality Notification TaskIn S/4HANA it can replace QMSM with a clean core approachQualityNotification = QMEL-QMNUMS/4HANA only

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_QMARTNotification typeRange / multipleQMEL-QMARTYesQ1
S_WERKPlantRange / multipleQMEL-MAWERKNo1000
S_QMDATNotification dateRange / multipleQMEL-QMDATNo01.01.2026 – 17.11.2026
S_LIFNUMVendorRange / multipleQMEL-LIFNUMNo100512
S_KUNUMCustomerRange / multipleQMEL-KUNUMNo200310
S_PRIOKPriorityRange / multipleQMEL-PRIOKNo1
P_KEYDTKey date (default: today)Single valueSY-DATUMYes17.11.2026
P_ONLYODOverdue onlyCheckbox—NoX

Output columns

#ColumnSource
1NotificationQMEL-QMNUM
2TypeQMEL-QMART
3DescriptionQMEL-QMTXT
4PriorityQMEL-PRIOK
5MaterialQMEL-MATNR
6VendorQMEL-LIFNUM
7CustomerQMEL-KUNUM
8Notification dateQMEL-QMDAT
9Required endQMEL-LTRMN
10Days overdueCalculated Key date − QMEL-LTRMN
11Open tasksCalculated Number of QMSM tasks without ERLDAT and not deleted
12Overdue tasksCalculated Open tasks with QMSM-PETER < key date
13Next overdue taskQMSM-MATXT
14Task planned finishQMSM-PETER
15Task ownerQMSM-PARNR

Sample output

NotificationTypeDescriptionPriorityMaterialVendorCustomerNotification dateRequired endDays overdueOpen tasksOverdue tasksNext overdue taskTask planned finishTask owner
000300001245Q1Moisture stain on packaging1FG-205020031010/14/202610/28/20262032Root cause analysis (8D D4)10/24/2026KALITE03
000300001260Q2Paint viscosity out of tolerance2RM-310510051210/29/202611/12/2026521Request 8D report from vendor11/07/2026TEDARIK01
000300001271Q1Wrong batch number on label2FG-100220014511/05/202611/15/2026211Correct the label template11/13/2026KALITE01
A view built with fictional sample data; not real system data.

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.

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

QM Package Custom

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 …

5 components · v1.0

Related reports

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.

Related report: Overdue Quality Notifications and Open Tasks Report