Mass Master Inspection Characteristic Upload from Excel Program
Short answer: A custom program that creates quantitative and qualitative master inspection characteristics in bulk from Excel or CSV rows, with text, unit of measure, decimal places, target value, tolerance limits and code group, or opens a new version of them. It checks everything in test mode first, then lists the result of each row.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 4
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
QS21 creates master inspection characteristics one at a time and QS23 opens new versions one at a time; there is no file upload. Because the control indicators are entered in pop-ups, recording-based uploads are fragile. When a new plant or product family needs hundreds of characteristics, teams enter them manually for days. The custom program loads the characteristic list from the file through the standard BAPI.
Who uses it? QM consultants, quality planning engineers and project teams rolling out a new plant or product range.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| QPMKMaster Inspection Characteristic | Master inspection characteristic header: version, validity, control indicators, target and tolerance | Read / write | ECC + S/4 |
| QPMTMaster Inspection Characteristic Texts | Characteristic short text (per language) | Write | ECC + S/4 |
| T006Units of Measurement | Unit of measure check | Read | ECC + S/4 |
| QPGRInspection Catalog Code Groups | Code group check for qualitative characteristics | Read | ECC + S/4 |
BAPIs and functions used
- BAPI_QPMK_SAVEREPLICAReplicate Master Inspection Characteristics (ALE). Creates the master inspection characteristic or its new version for each row
- BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Saves successful rows permanently
- BAPI_TRANSACTION_ROLLBACKRoll Back BAPI Transaction. Rolls back the change in test mode
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_FILE | Upload file (XLSX or CSV) | Single value | — | Yes | C:\temp\karakteristikler.xlsx |
| P_WERKS | Plant | Single value | QPMK-ZAEHLER | Yes | 1000 |
| P_RELEA | Create with status released | Checkbox | — | No | X |
| P_TEST | Test mode (check without saving) | Checkbox | — | No | X |
Input file columns
The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.
| # | Column | Target field | Required |
|---|---|---|---|
| 1 | Master characteristic | QPMK-MKMNR | Yes |
| 2 | Valid from | QPMK-GUELTIGAB | Yes |
| 3 | Short text | QPMT-KURZTEXT | Yes |
| 4 | Language | QPMT-SPRACHE | No |
| 5 | Type (N quantitative, L qualitative) | By rule Written to the quantitative/qualitative control indicator in QPMK-STEUERKZ | Yes |
| 6 | Decimal places | QPMK-STELLEN | No |
| 7 | Unit of measure | QPMK-MASSEINHSW | No |
| 8 | Target value | QPMK-SOLLWERT | No |
| 9 | Lower limit | QPMK-TOLERANZUN | No |
| 10 | Upper limit | QPMK-TOLERANZOB | No |
| 11 | Code group (qualitative) | By rule Assigned as the catalog link of a qualitative characteristic; must exist in QPGR | No |
Sample upload file
| 1 | Master characteristic * | Valid from * | Short text * | Language | Type (N quantitative, L qualitative) * | Decimal places | Unit of measure | Target value | Lower limit | Upper limit | Code group (qualitative) |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | NET-AG | 12/01/2026 | Net weight | TR | N | 1 | G | 830 | 825 | 840 | |
| 3 | BRIX | 12/01/2026 | Brix value | TR | N | 1 | % | 28 | 27 | 30 | |
| 4 | GORUNUM | 12/01/2026 | Visual check | TR | L | GORSEL |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Row | Calculated Row number in the file |
| 2 | Master characteristic | QPMK-MKMNR |
| 3 | Version | QPMK-VERSION |
| 4 | Status | Calculated From the BAPI return messages: created, new version or error |
| 5 | Message | Calculated Check message or the first message from the BAPI return table |
Sample result list
| Row | Master characteristic | Version | Status | Message |
|---|---|---|---|---|
| 2 | NET-AG | 000001 | Created | Master inspection characteristic NET-AG created |
| 3 | BRIX | 000002 | New version | Version 2 created for the existing characteristic |
| 4 | GORUNUM | Error | Code group GORSEL not found |
How does the program work?
- The file is read; the plant comes from the selection screen (QPMK-ZAEHLER) and the first row is skipped as the header.
- Every row is checked: the characteristic key and valid-from date are mandatory; for a quantitative characteristic the unit must exist in T006, the decimal places must be given and lower limit ≤ target ≤ upper limit must hold; for a qualitative characteristic the code group must exist in QPGR.
- If the characteristic already exists in QPMK and the new valid-from date is later, a new version is opened; if a version with the same date exists, the row gets an error.
- The row is mapped to the BAPI_QPMK_SAVEREPLICA structures: header and control indicators (quantitative/qualitative, lower and upper limit check, target value check), short text per language (QPMT) and, for a qualitative characteristic, the catalog link.
- In test mode the BAPI is called and rolled back with BAPI_TRANSACTION_ROLLBACK; in a real run BAPI_TRANSACTION_COMMIT is called after each successful row. Result and message are listed per row; failed rows can be downloaded as a separate file.
Performance notes
Characteristic lists are usually a few hundred rows and load in the foreground within minutes. Committing per row isolates failed rows.
Features
- Test mode (check without posting)
- Line-by-line result and error log
- Download failed lines as a separate file
- ALV list (sort, filter, subtotals)
- Delivered as a transport request The same file can be tried in the test system and then loaded with the same result in production.
Authorization objects
- Q_TCODEQM transaction authorization (QS21 / QS23)
Frequently asked questions
What happens if an existing characteristic is in the file?
If the valid-from date in the file is later than the latest version, a new version is opened and the old version is kept for existing inspection plans. If a version with the same date exists, the row is not changed and is listed as an error.
Can inspection methods and sampling settings be loaded as well?
Yes. Inspection method assignment, sampling procedure and additional control indicators can be added as columns to the file template; each additional group of fields raises the effort range slightly.
Does the program work on S/4HANA?
Yes. QPMK, QPMT and BAPI_QPMK_SAVEREPLICA also exist in S/4HANA; the file template and checks stay the same.
Related reports
Inspection Results Upload from Laboratory File Program
A custom interface program that records the measured values in a CSV/XLSX file produced by laboratory instruments or a laboratory information system …
Materials with Missing or Inconsistent QM Inspection Setup Report
A custom ALV report that checks the QM settings in the material master against rules and lists each finding with a suggested action: expected …
Process Capability (Cp/Cpk) Report by Inspection Characteristic
A custom ALV report that calculates the mean, standard deviation, Cp and Cpk for each master inspection characteristic from the quantitative results …
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.