QM Report Custom development ALV report

Quality Notification Defect and Root Cause Pareto Analysis Report

Short answer: A custom ALV report that counts defect codes and root cause codes in the quality notifications of the selected period and ranks them from the most frequent, with share, cumulative percentage and ABC class. Quality teams focus improvement and 8D work on the few defects that make up 80% of the problems.

Estimated effort
S · 2–4 working days
System
ECC and S/4HANA
Tables
5
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

QM11 lists notification items with their defect code and QM10 opens notifications for change; neither gives a count per code, a share or a cumulative percentage, and neither combines the defect code with the root cause on the same line. The Pareto chart is therefore built in Excel every month. The custom report matches defects and causes at notification item level and also shows items without a root cause on a separate line.

Who uses it? Quality managers, quality engineers, supplier quality and customer complaint teams.

Closest standard alternatives

  • QM11 Display List of Quality Notifications. Lists notification items with the defect code; no count per code, no cumulative percentage and no combined view with the root cause.
  • QM10 Change List of Quality Notifications. Lists notifications for change; does not analyse or rank them as a Pareto.

Tables used

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

TableRoleJoinSystem
QMELNotification HeaderNotification header: type, date, material, vendor, customer, complaint quantity (driving table)—ECC + S/4
QMFENotification ItemsDefect items: defect code group, code and number of defectsQMFE-QMNUM = QMEL-QMNUMECC + S/4
QMURNotification CausesRoot cause codes linked to the defect itemQMUR-QMNUM = QMFE-QMNUM AND QMUR-FENUM = QMFE-FENUMECC + S/4
QPCTCode TextsTexts of defect and root cause codesQPCT-KATALOGART = QMFE-FEKAT AND QPCT-CODEGRUPPE = QMFE-FEGRP AND QPCT-CODE = QMFE-FECODECC + S/4
I_QltyNotificationCauseQuality Notification Item CauseIn S/4HANA it can replace QMUR with a clean core approachQualityNotification = QMEL-QMNUMS/4HANA only

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_QMARTNotification typeRange / multipleQMEL-QMARTYesQ1
S_QMDATNotification date rangeRange / multipleQMEL-QMDATYes01.07.2026 – 31.10.2026
S_WERKSPlantRange / multipleQMEL-MAWERKNo1000
S_MATNRMaterialRange / multipleQMEL-MATNRNoFG-1120
S_LIFNRVendorRange / multipleQMEL-LIFNUMNo100245
S_KUNNRCustomerRange / multipleQMEL-KUNUMNo200100
R_DEFPareto key: defect code onlyRadio button—No—
R_DEFCAUPareto key: defect code and root causeRadio button—NoX

Output columns

#ColumnSource
1Defect code groupQMFE-FEGRP
2Defect codeQMFE-FECOD
3Defect textQPCT-KURZTEXT
4Cause code groupQMUR-URGRP
5Cause codeQMUR-URCOD
6Cause textCalculated QPCT-KURZTEXT (catalog type QMUR-URKAT, group QMUR-URGRP, code QMUR-URCOD)
7NotificationsCalculated Number of distinct QMEL-QMNUM
8DefectsCalculated Σ QMFE-ANZFEHLER (1 when empty)
9Share %Calculated Defects ÷ total defects × 100
10Cumulative %Calculated Sum of shares up to this line
11ABC classCalculated Cumulative ≤ 80%: A, ≤ 95%: B, others: C
12Complaint qtyCalculated Σ QMEL-RKMNG
13Most frequent materialCalculated QMEL-MATNR with the most notifications for this code
14Example notificationQMEL-QMNUM

Sample output

Defect code groupDefect codeDefect textCause code groupCause codeCause textNotificationsDefectsShare %Cumulative %ABC classComplaint qtyMost frequent materialExample notification
DEF-AMB010Dented packagingNED-LOJ020Insufficient stacking protection18423030A1,260FG-1001200000451
DEF-DOL020UnderfillNED-MAK040Filling machine calibration93827.1057.10A410FG-1120200000470
DEF-ETK030Wrong labelNED-INS010Operator error122517.9075A640FG-1120200000463
DEF-YAB050Foreign matterNED-HAM030Raw material contamination61510.7085.70B180FG-4010200000488
A view built with fictional sample data; not real system data.

How does the report work?

  1. QMEL is read by notification type, notification date (QMDAT), plant, material, vendor or customer.
  2. The QMFE defect items of each notification (defect catalog, code group and code) and the QMUR root causes linked to them (QMUR-FENUM = QMFE-FENUM) are read.
  3. Code texts are added from QPCT in the logon language by catalog type, code group, code and version.
  4. Totals are built by the selected key (defect code only, or defect code with root cause): number of distinct notifications, Σ QMFE-ANZFEHLER (counted as 1 when empty) and Σ QMEL-RKMNG complaint quantity; the most frequent material and one example notification number are added.
  5. The list is sorted by number of defects in descending order; share and cumulative percentage are calculated. ABC: A up to 80% cumulative, B up to 95%, C for the rest.
  6. Defect items without a root cause are totalled in a “No root cause” line, which is tracked separately for 8D discipline.

Performance notes

Narrow the QMEL selection by notification type and date; read QMFE and QMUR in one JOIN by notification number. Read QPCT texts only for the codes in the result.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants The result can also be shown as an ALV chart with Pareto bars and a cumulative line.
  • Double-click drill-down to the document Double-clicking a line lists the notifications for that code; clicking a notification opens QM03.
  • Export to Excel
  • Runs as a background job
  • Send the result by email The Pareto list can be emailed to the quality team before the monthly quality meeting.

Authorization objects

  • Q_QMELQuality notification display authorization by notification type

Frequently asked questions

Should the number of notifications or the number of defects be used?

The report shows both. Where many defects are recorded on one notification (e.g. count-based incoming inspection), the number of defects is more meaningful; on the customer side, where the number of complaints matters, the number of notifications is. The sort key can be added to the selection screen.

What happens to defects without a root cause?

They are totalled in the "No root cause" line. A high share for this line means notifications are closed in the 8D process before the cause analysis is complete; the report makes this gap visible too.

Does the report work on S/4HANA?

Yes. QMEL, QMFE, QMUR and QPCT keep the same structure in S/4HANA. For a clean core approach, the I_QltyNotificationCause and I_QualityNotificationItem CDS views can be used.

Packages that include this solution

QM Package Custom

Customer Complaint and Root Cause Pack

A five-component pack that follows a customer complaint from intake to improvement: automatic complaint notifications from a portal or call centre …

5 components · v1.0

Related reports

QM Report Custom ALV report

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 …

QMEL · JEST · TJ02T · QMSM

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: Quality Notification Defect and Root Cause Pareto Analysis Report