# Quality Notification Defect and Root Cause Pareto Analysis Report

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

- Type: Report, Custom development, ALV report
- Module: QM
- Estimated effort: S (2–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/quality-notification-defect-root-cause-pareto-report/


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

### Closest standard alternatives

- QM11: Lists notification items with the defect code; no count per code, no cumulative percentage and no combined view with the root cause.
- QM10: Lists notifications for change; does not analyse or rank them as a Pareto.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| QMEL | Notification header: type, date, material, vendor, customer, complaint quantity (driving table) | Read | - | ECC + S/4 |
| QMFE | Defect items: defect code group, code and number of defects | Read | QMFE-QMNUM = QMEL-QMNUM | ECC + S/4 |
| QMUR | Root cause codes linked to the defect item | Read | QMUR-QMNUM = QMFE-QMNUM AND QMUR-FENUM = QMFE-FENUM | ECC + S/4 |
| QPCT | Texts of defect and root cause codes | Read | QPCT-KATALOGART = QMFE-FEKAT AND QPCT-CODEGRUPPE = QMFE-FEGRP AND QPCT-CODE = QMFE-FECOD | ECC + S/4 |
| I_QltyNotificationCause | In S/4HANA it can replace QMUR 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_QMDAT | Notification date range | Range / multiple | QMEL-QMDAT | Yes |
| S_WERKS | Plant | Range / multiple | QMEL-MAWERK | No |
| S_MATNR | Material | Range / multiple | QMEL-MATNR | No |
| S_LIFNR | Vendor | Range / multiple | QMEL-LIFNUM | No |
| S_KUNNR | Customer | Range / multiple | QMEL-KUNUM | No |
| R_DEF | Pareto key: defect code only | Radio button | - | No |
| R_DEFCAU | Pareto key: defect code and root cause | Radio button | - | No |

## Output columns

| Column | Source |
|---|---|
| Defect code group | QMFE-FEGRP |
| Defect code | QMFE-FECOD |
| Defect text | QPCT-KURZTEXT |
| Cause code group | QMUR-URGRP |
| Cause code | QMUR-URCOD |
| Cause text | Calculated: QPCT-KURZTEXT (catalog type QMUR-URKAT, group QMUR-URGRP, code QMUR-URCOD) |
| Notifications | Calculated: Number of distinct QMEL-QMNUM |
| Defects | Calculated: Σ QMFE-ANZFEHLER (1 when empty) |
| Share % | Calculated: Defects ÷ total defects × 100 |
| Cumulative % | Calculated: Sum of shares up to this line |
| ABC class | Calculated: Cumulative ≤ 80%: A, ≤ 95%: B, others: C |
| Complaint qty | Calculated: Σ QMEL-RKMNG |
| Most frequent material | Calculated: QMEL-MATNR with the most notifications for this code |
| Example notification | QMEL-QMNUM |

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

## Authorization objects

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

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=qm-notification-defect-cause-pareto
