SAPFree worksheetPDF, Excel, Word exportSAP ECC / S/4HANAManufacturing

SAP Master Inspection Characteristic Upload Worksheet

Master inspection characteristics (MICs) are the reusable measurement definitions in SAP QM. Collecting and cleansing them in a worksheet before the load avoids duplicates and bad tolerances.

Download:
PlantMIC nameShort textTypeUnitLower limitUpper limitTolerance rangeTargetDecimals
0.03999999999999915
25
0.19999999999998863
150
1.6
0.8
10
50
0
0
Total tolerance range
11.84
Number of characteristics
5

Qualitative characteristics have no numeric limits, so leave limits at zero. The worksheet is a planning and cleansing tool. The load itself (LSMW, BAPI, migration cockpit or recording of QS21) must match field names in your release.

Need help migrating quality master data?

We can help map legacy inspection data to SAP QM structures and check it before you load.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

Add one row per characteristic and plant. Enter a short name, whether it is quantitative or qualitative, the unit, the limits and the number of decimals. The worksheet calculates the tolerance range and the target (midpoint) so you can spot reversed or implausible limits straight away. Export to Excel or CSV and hand the file to the person doing the data load.

What a MIC contains in SAP QM

A master inspection characteristic is created in QS21 and holds the descriptive text, the inspection method, the unit and the tolerance defaults. A quantitative characteristic records measured values. A qualitative one records an accept or reject outcome, often with a code catalog. MICs are then referenced from inspection plans so you maintain the definition once and reuse it across plans. Versions and status control who can use a MIC.

  • Quantitative: measured value with limits, unit and decimals
  • Qualitative: coded result with a catalog of codes
  • Plant specific or shared across plants through a controlling area
  • Version and status control the lifecycle of the definition

Common mistakes

Data loads fail or create trouble for several reasons. Limits can be reversed, units may not match the base unit of the method, decimals can be too few for the resolution of the instrument, or names can break the naming rule. Another mistake is creating a MIC per plan instead of a reusable one, which makes later changes a big project.

  • Lower limit larger than upper limit
  • Decimals fewer than the measuring instrument resolution
  • Different spelling of the same MIC across plants
  • Qualitative characteristics loaded without a code catalog

Frequently Asked Questions

Which transaction creates master inspection characteristics?

QS21 creates a master inspection characteristic, QS22 changes it and QS23 displays it. Bulk loads normally use a migration tool or a recording, depending on your release and skills.

Can I load MICs with LSMW?

Many projects do load MICs with LSMW recordings or the migration cockpit, but you should check what is supported for your release. Always do a test load and compare the result with QS23.

What is the difference between a MIC and a characteristic in a plan?

A MIC is a reusable definition. The characteristic in an inspection plan references a MIC and can override some values, such as limits, for the specific plan.

Why does the worksheet calculate a target?

The midpoint helps spot errors in limits. Your plan target may differ from the midpoint for one sided tolerances, so treat the calculated target as a check only.

Netray can help clean legacy quality data and map it to SAP QM structures before migration. Tell us about your source system if you would like help.