Automatic Vendor Quality Notification Creation for Rejected Characteristics
Short answer: A custom background job that automatically opens a quality notification against the vendor for goods receipt lots with a rejected characteristic. The notification is created with the material, batch, purchase order and measured values; every rejected characteristic becomes a separate defect item.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
QM01 opens a notification manually. If defects are recorded during results recording, a notification can be created through the inspection type setting, but that expects the user to enter the defect separately; when results come from a laboratory interface or a mass upload, no notification is opened at all. An automatic job is needed so that every rejected result turns into a notification against the vendor and shows up on the vendor scorecard.
Who uses it? Supplier quality engineers, incoming inspection laboratories, quality managers and purchasing teams.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| QALSInspection Lot Record | Goods receipt inspection lot, vendor, batch and purchase order | Read | ECC + S/4 |
| QAMRCharacteristic Results During Inspection Processing | Rejected characteristic results | Read | ECC + S/4 |
| QAMVCharacteristic Specifications for Inspection Processing | Characteristic description, target and limits | Read | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor name | Read | ECC + S/4 |
| QMELNotification Header | Existing notification check and the quality notification created | Read / write | ECC + S/4 |
| QMFENotification Items | Defect item for every rejected characteristic | Write | ECC + S/4 |
BAPIs and functions used
- BAPI_QUALNOT_CREATECreate QM Notification. Creates the quality notification with header and defect items
- BAPI_QUALNOT_SAVESave QM Notification. Saves the notification created
- BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Makes the save permanent
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_WERK | Plant | Range / multiple | QALS-WERK | Yes | 1000 |
| S_ART | Inspection type | Range / multiple | QALS-ART | No | 01 |
| S_DATE | Result date range | Range / multiple | QAMR-PRUEFDATUV | Yes | Son 3 gün |
| S_LIFNR | Vendor | Range / multiple | QALS-LIFNR | No | 100245 |
| P_QMART | Notification type | Single value | QMEL-QMART | Yes | Q2 |
| P_FEGRP | Default defect code group | Single value | QMFE-FEGRP | No | GIRIS |
| P_FECOD | Default defect code | Single value | QMFE-FECOD | No | 0010 |
| P_TEST | Test mode (list without creating notifications) | Checkbox | — | No | X |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Inspection lot | QALS-PRUEFLOS |
| 2 | Vendor | QALS-LIFNR |
| 3 | Vendor name | LFA1-NAME1 |
| 4 | Material | QALS-MATNR |
| 5 | Rejected characteristic | QAMV-VERWMERKM |
| 6 | Measured mean | QAMR-MITTELWERT |
| 7 | Notification | QMEL-QMNUM |
| 8 | Status | Calculated Created, test, skipped (notification exists) or error |
| 9 | Message | Calculated First error or success message from the BAPI return table |
Sample result list
| Inspection lot | Vendor | Vendor name | Material | Rejected characteristic | Measured mean | Notification | Status | Message |
|---|---|---|---|---|---|---|---|---|
| 010000018840 | 100245 | Bursa Metal Sanayi | RM-2051 | KALINLIK | 3.18 | 200001452 | Created | Notification 200001452 saved, 1 defect item |
| 010000018902 | 100388 | Konya Kalıp ve Plastik | RM-3602 | CAP-DIS | 40.36 | 200001453 | Created | Notification 200001453 saved, 2 defect items |
| 010000018911 | 100412 | Trakya Ambalaj | RM-1205 | NEM | 11.80 | 200001440 | Skipped | A notification already exists for the lot |
| 010000018915 | 100310 | Kuzey Ahşap Ürünleri | RM-4410 | KALINLIK | 17.20 | Error | Defect code GIRIS/0010 not in catalog |
How does the program work?
- Goods receipt lots (QALS) in the selected plant and inspection types whose result date is in the parameter range and that have at least one rejected characteristic (QAMR-MBEWERTG = R) are read.
- Lots that already have a notification (QMEL-PRUEFLOS) are skipped, so a second notification is never opened for the same lot when the job runs again.
- The notification header is prepared: notification type (parameter, e.g. Q2), material, vendor, plant, batch, inspection lot, purchase order and item; the short text is built from the description of the first rejected characteristic.
- A defect item is added for every rejected characteristic: the defect code group and code come from the parameter or from a characteristic-to-code mapping table; target, limits and measured mean are written to the long text.
- The notification is created with BAPI_QUALNOT_CREATE and saved with BAPI_QUALNOT_SAVE and BAPI_TRANSACTION_COMMIT. In test mode only the notifications to be opened are listed. Results and messages are written to the job log.
Performance notes
Schedule the job hourly or daily and limit the result date range to the last few days. A commit is done per notification; a lot that fails is retried in the next run.
Features
- Runs as a background job
- Test mode (check without posting)
- Line-by-line result and error log
- Send the result by email The list of notifications created can be sent to the supplier quality engineer.
- ALV list (sort, filter, subtotals)
Authorization objects
- Q_QMELQuality notification creation authorization by notification type
- Q_INSPTYPEInspection lot authorization by inspection type
Frequently asked questions
How many notifications are opened when several characteristics of a lot are rejected?
One notification is opened per lot and every rejected characteristic becomes a separate defect item on it. Separate notifications per characteristic are also possible if preferred.
Is the notification sent to the vendor automatically?
The program opens the notification; sending it to the vendor is done with the standard notification output or email setup. A step that emails a summary to the vendor when the notification is saved can be added if needed.
Can it be used on S/4HANA?
Yes. BAPI_QUALNOT_CREATE and BAPI_QUALNOT_SAVE are supported on S/4HANA as well; the QM tables read are the same.
Packages that include this solution
Supplier Quality Management Pack
A four-component pack that follows supplier quality from approval to evaluation: quality info record release and certificate validity, lots skipped by …
Related reports
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 program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.