How-toSAP ERP / S/4HANAQM / Master Inspection Characteristics

How to Create a MIC (Master Inspection Characteristic) in SAP QM

Question
how to create mic in sap qm

Also searched as

  • what is mic in sap qm
  • mic's table in sap qm
  • how to create catalog profile in sap qm

Short answer

A MIC is a reusable inspection characteristic in SAP QM, created in QS21 with a plant, a name and a version, then defined as quantitative (measured values with limits) or qualitative (codes from a catalog). Inspection plans (QP01) pick MICs so tolerances are maintained once. MIC data is in table QPMK, with text in QPMT.

Applies to: SAP ECC 6.0 and S/4HANA QM; QS21, QS22 and QS23 for create, change and display

Create a MIC with QS21

  1. 1Run QS21 (Create Master Inspection Characteristic). Enter the plant, the MIC name (up to 8 characters) and press Enter.
  2. 2On the General data screen, give a short text and set the status of the new version, for example in preparation, then released when ready.
  3. 3On the Control indicators, choose quantitative or qualitative behaviour by the indicators: Quantitative characteristic for measured values, or Required characteristic and Attributive for qualitative.
  4. 4For quantitative MICs, enter the unit of measure, number of decimal places, target value and tolerance limits.
  5. 5For qualitative MICs, assign the catalog (code group or selected set) for the allowed codes. Catalog type 1 is for characteristic attributes.
  6. 6Set the sampling procedure and inspection method in their tabs if standard for all plans.
  7. 7Save, release the version, then use the MIC in the inspection plan (QP01) by selecting it in the characteristics overview.

What a MIC is and why use one

A master inspection characteristic is a template for something to inspect: a dimension, a hardness, appearance. Plans reference it rather than retyping tolerance values, so changing the MIC in one place updates all plans that use it, subject to versioning rules.

MICs are plant-specific unless you use a shared plant setup. Each MIC has versions, with only one active version at a time, and a status such as in preparation, released, or blocked. Plans can reference a MIC in a reference characteristic way, copy it, or use it as a model.

Quantitative versus qualitative

Quantitative characteristics record measured numbers, so you give a unit, decimals, target and limits. They support statistical analysis and charts. Qualitative characteristics record a code from a catalog, such as good or damaged, and are evaluated by an accept or reject rule.

Choose per characteristic. A hole diameter is quantitative. A visual check is qualitative. Quantitative MICs can also use classes and a defect catalog to explain failures.

Catalogs, code groups and profiles

Catalogs hold codes. Each catalog type serves a purpose: type 1 for characteristic attributes, type 3 for usage decisions, and others for defects and causes. Codes are grouped into code groups (QS41) and optionally into selected sets (QS51), which a MIC uses to restrict the codes shown.

Catalog profiles, set up in customizing, bundle catalog types and defaults so users working in a plan or notification see the right catalogs. The underlying tables include QPCD for codes and QPGR for code groups. MIC master data is QPMK, with texts in QPMT.

Try it here, free

SAP Master Inspection Characteristic Upload Worksheet

Open full tool

Collect master inspection characteristics in one worksheet, check tolerances and export a clean file for your data load.

Common pitfalls

  • !Forgetting to release the new MIC version, so plans cannot use it.
  • !Changing a MIC that is widely used without checking the impact on open plans.
  • !Using a qualitative MIC where numeric data is needed for SPC.
  • !Missing the catalog assignment, so the results screen shows no codes.
  • !Creating MICs per plan instead of reusing common ones.

How an ERP-grounded AI assistant handles this

A private AI layer can query QPMK and your inspection plans to answer which plans use a given characteristic or which MICs are still unreleased, and propose naming clean-up. It reads and reports, while MIC creation and changes remain in QS21 under your change control.

See ERPray

Frequently asked questions

What is a MIC in SAP QM?

A master inspection characteristic is a reusable definition of a quality feature to inspect, such as a dimension or visual check. It stores unit, tolerances, catalogs and methods once, and inspection plans reference it.

What transaction creates a MIC?

QS21 creates, QS22 changes and QS23 displays a master inspection characteristic. You create it per plant, give it a name, set the control indicators and release the version before using it in a plan.

What is the MIC table in SAP?

QPMK holds the master inspection characteristic data and QPMT holds its text. Catalog codes are in QPCD and code groups in QPGR, which the MIC references for qualitative results.

How do I create a catalog profile?

Catalog profiles are set in QM customizing, where you group catalog types and defaults, then assign them where the profile is used. Codes and code groups themselves are maintained with QS41 and selected sets with QS51.

Related

How-to

How to Create a Sampling Procedure in SAP QM

In SAP QM, a sampling procedure decides how many units to inspect and how to accept or reject the lot. Maintain it in QDV3, choose a sample type (fixed, percentage, sampling scheme or 100 percent) and a valuation mode, and where needed build the scheme in QDP1. Then assign the procedure to a master inspection characteristic or inspection plan.

How-to

What Is First Article Inspection in SAP, and How to Run It in QM

First article inspection (FAI) in SAP is not a single button. You model it in SAP QM with an inspection type that creates an inspection lot when the production order is released, an inspection plan with the characteristics to verify on the first piece, and results recorded then closed by a usage decision. Aerospace AS9102-style FAI forms normally need extra reporting on top.

How-to

SAP QA11 Usage Decision: Make It and Post Stock Correctly

The usage decision (UD) in QA11 closes an inspection lot, assigns a quality score and a UD code such as accepted or rejected, and posts the lot quantity from quality inspection stock to unrestricted use, blocked stock, scrap or return to vendor. The UD is blocked until required inspection characteristics are closed and results are recorded.

Error fix

SAP M7 021: Deficit of SL Stock Quantity

M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.

Error fix

SAP IDoc Status 51: Application Document Not Posted

Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.

Error fix

SAP Short Dump TIME_OUT: Maximum Runtime Exceeded

A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.

AI for ERP

AI for SAP Quality Management: Notifications, 8D, and CAPA Without the Manual Drafting

AI grounded on SAP QM data that triages notifications, drafts 8D and CAPA reports, and summarizes inspection trends, deployed on-prem for full traceability.

AI for ERP

AI for NCR, CAPA, and 8D Drafting in AS9100 and ISO 9001 Quality Systems

AI drafts NCR, CAPA, and 8D reports from ERP quality data for engineer review, cutting drafting time under AS9100 and ISO 9001 without changing sign-off.

Stuck on SAP ERP / S/4HANA?

Talk to engineers who work inside SAP ERP / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos