QM Program Custom development Mass upload

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

  • QS21 Create Master Inspection Characteristic. Creates master inspection characteristics one at a time; no file upload.
  • QS23 Change Master Inspection Characteristic Version. Opens new characteristic versions one at a time.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
QPMKMaster Inspection CharacteristicMaster inspection characteristic header: version, validity, control indicators, target and toleranceRead / writeECC + S/4
QPMTMaster Inspection Characteristic TextsCharacteristic short text (per language)WriteECC + S/4
T006Units of MeasurementUnit of measure checkReadECC + S/4
QPGRInspection Catalog Code GroupsCode group check for qualitative characteristicsReadECC + 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

ParameterDescriptionTypeReference fieldRequiredExample
P_FILEUpload file (XLSX or CSV)Single value—YesC:\temp\karakteristikler.xlsx
P_WERKSPlantSingle valueQPMK-ZAEHLERYes1000
P_RELEACreate with status releasedCheckbox—NoX
P_TESTTest mode (check without saving)Checkbox—NoX

Input file columns

The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.

#ColumnTarget fieldRequired
1Master characteristicQPMK-MKMNRYes
2Valid fromQPMK-GUELTIGABYes
3Short textQPMT-KURZTEXTYes
4LanguageQPMT-SPRACHENo
5Type (N quantitative, L qualitative)By rule Written to the quantitative/qualitative control indicator in QPMK-STEUERKZYes
6Decimal placesQPMK-STELLENNo
7Unit of measureQPMK-MASSEINHSWNo
8Target valueQPMK-SOLLWERTNo
9Lower limitQPMK-TOLERANZUNNo
10Upper limitQPMK-TOLERANZOBNo
11Code group (qualitative)By rule Assigned as the catalog link of a qualitative characteristic; must exist in QPGRNo

Sample upload file

1Master characteristic *Valid from *Short text *LanguageType (N quantitative, L qualitative) *Decimal placesUnit of measureTarget valueLower limitUpper limitCode group (qualitative)
2NET-AG12/01/2026Net weightTRN1G830825840
3BRIX12/01/2026Brix valueTRN1%282730
4GORUNUM12/01/2026Visual checkTRLGORSEL
A view built with fictional sample data; not real system data.

Result list columns

#ColumnSource
1RowCalculated Row number in the file
2Master characteristicQPMK-MKMNR
3VersionQPMK-VERSION
4StatusCalculated From the BAPI return messages: created, new version or error
5MessageCalculated Check message or the first message from the BAPI return table

Sample result list

RowMaster characteristicVersionStatusMessage
2NET-AG000001CreatedMaster inspection characteristic NET-AG created
3BRIX000002New versionVersion 2 created for the existing characteristic
4GORUNUMErrorCode group GORSEL not found
A view built with fictional sample data; not real system data.

How does the program work?

  1. The file is read; the plant comes from the selection screen (QPMK-ZAEHLER) and the first row is skipped as the header.
  2. 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.
  3. 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.
  4. 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.
  5. 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

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.

Related report: Mass Master Inspection Characteristic Upload from Excel Program