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
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 header: type, date, material, vendor, customer, complaint quantity (driving table) | — | ECC + S/4 |
| QMFENotification Items | Defect items: defect code group, code and number of defects | QMFE-QMNUM = QMEL-QMNUM | ECC + S/4 |
| QMURNotification Causes | Root cause codes linked to the defect item | QMUR-QMNUM = QMFE-QMNUM AND QMUR-FENUM = QMFE-FENUM | ECC + S/4 |
| QPCTCode Texts | Texts of defect and root cause codes | QPCT-KATALOGART = QMFE-FEKAT AND QPCT-CODEGRUPPE = QMFE-FEGRP AND QPCT-CODE = QMFE-FECOD | ECC + S/4 |
| I_QltyNotificationCauseQuality Notification Item Cause | In S/4HANA it can replace QMUR 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_QMDAT | Notification date range | Range / multiple | QMEL-QMDAT | Yes | 01.07.2026 – 31.10.2026 |
| S_WERKS | Plant | Range / multiple | QMEL-MAWERK | No | 1000 |
| S_MATNR | Material | Range / multiple | QMEL-MATNR | No | FG-1120 |
| S_LIFNR | Vendor | Range / multiple | QMEL-LIFNUM | No | 100245 |
| S_KUNNR | Customer | Range / multiple | QMEL-KUNUM | No | 200100 |
| R_DEF | Pareto key: defect code only | Radio button | — | No | — |
| R_DEFCAU | Pareto key: defect code and root cause | Radio button | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Defect code group | QMFE-FEGRP |
| 2 | Defect code | QMFE-FECOD |
| 3 | Defect text | QPCT-KURZTEXT |
| 4 | Cause code group | QMUR-URGRP |
| 5 | Cause code | QMUR-URCOD |
| 6 | Cause text | Calculated QPCT-KURZTEXT (catalog type QMUR-URKAT, group QMUR-URGRP, code QMUR-URCOD) |
| 7 | Notifications | Calculated Number of distinct QMEL-QMNUM |
| 8 | Defects | Calculated Σ QMFE-ANZFEHLER (1 when empty) |
| 9 | Share % | Calculated Defects ÷ total defects × 100 |
| 10 | Cumulative % | Calculated Sum of shares up to this line |
| 11 | ABC class | Calculated Cumulative ≤ 80%: A, ≤ 95%: B, others: C |
| 12 | Complaint qty | Calculated Σ QMEL-RKMNG |
| 13 | Most frequent material | Calculated QMEL-MATNR with the most notifications for this code |
| 14 | Example notification | QMEL-QMNUM |
Sample output
| Defect code group | Defect code | Defect text | Cause code group | Cause code | Cause text | Notifications | Defects | Share % | Cumulative % | ABC class | Complaint qty | Most frequent material | Example notification |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DEF-AMB | 010 | Dented packaging | NED-LOJ | 020 | Insufficient stacking protection | 18 | 42 | 30 | 30 | A | 1,260 | FG-1001 | 200000451 |
| DEF-DOL | 020 | Underfill | NED-MAK | 040 | Filling machine calibration | 9 | 38 | 27.10 | 57.10 | A | 410 | FG-1120 | 200000470 |
| DEF-ETK | 030 | Wrong label | NED-INS | 010 | Operator error | 12 | 25 | 17.90 | 75 | A | 640 | FG-1120 | 200000463 |
| DEF-YAB | 050 | Foreign matter | NED-HAM | 030 | Raw material contamination | 6 | 15 | 10.70 | 85.70 | B | 180 | FG-4010 | 200000488 |
How does the report work?
- QMEL is read by notification type, notification date (QMDAT), plant, material, vendor or customer.
- 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.
- Code texts are added from QPCT in the logon language by catalog type, code group, code and version.
- 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.
- 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.
- 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
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 …
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 …
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 …
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.