# How to Create an Inspection Method in SAP QM (QS31)

> Source: https://netray.co/erp-help/sap-qm-create-inspection-method-qs31-how-to
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

An inspection method describes how a characteristic is to be inspected, for example with a micrometer or a visual check, and holds the instructions. Create it with QS31 for a plant, set the status and version, write the text, and assign it to a master inspection characteristic (QS21) or directly in an inspection plan characteristic.

## Kind

how-to

## System

sap

## Erp

SAP S/4HANA and ECC

## Module

Quality Management (QM) / Quality Planning Master Data

## Query

how to create inspection method in sap qm

## Alternate Queries

- sap qs31 inspection method
- assign inspection method master inspection characteristic
- sap qm inspection method task list

## Applies To

SAP ECC 6.0 and SAP S/4HANA on-premise with QM

## Steps

### Create and assign an inspection method

**Items:**

- Run QS31 (Create Inspection Method). Enter the plant and a method name, and press Enter.
- Fill in the short text and, if needed, a search field to help users find it.
- Set the status (for example created, released) and the version. Only released versions can be used in inspection plans.
- Add the long text with the inspection instructions: tools, conditions, sampling and sequence.
- Save. Use QS32 to change and QS33 to display.
- Assign it in the master inspection characteristic (QS21) in the Inspection method field, so every plan using the MIC inherits it.
- Or assign it directly to a characteristic in the inspection plan (QP01) when a one-off is needed.

## Sections

### Inspection method versus characteristic

**Body:**

The master inspection characteristic defines what is inspected (diameter, color, hardness), including the tolerances and result type. The inspection method defines how. Separating the two lets you reuse a single measurement procedure across many characteristics, and change it in one place.

For quantitative characteristics such as dimensions, the method often names the gauge or measuring equipment. For qualitative ones, it describes the visual criteria or the sample board used.

Methods are plant-specific, though you can copy them between plants. This matters in multi-plant companies using different gauges.

### Versions, status and change control

**Body:**

Methods have versions and statuses. A new version lets you change the instruction without changing past inspections. Old lots keep the version that was valid when they were created.

A released status is required for use. If the plan will not accept the method, check the status and the validity date. Methods can also be linked to change numbers if you use engineering change management.

Because the method text is shown to inspectors on the shop floor, review it as a controlled document. In regulated industries, the version history is part of your evidence.

**Code:**

- QS31   Create inspection method
- QS32   Change inspection method
- QS33   Display inspection method
- QS21   Maintain master inspection characteristic
- QP01   Create inspection plan

### Using methods in inspection plans

**Body:**

In an inspection plan, each operation has inspection characteristics. When a characteristic is copied from a MIC, the method comes with it. You can override it at plan level when the need is local.

At results recording (QE51N), the inspector sees the method text with the characteristic. If the text is missing, check the method assignment on the MIC and in the plan, and the version validity.

Keep method names consistent. A naming scheme by technique and plant makes searches and reporting simpler, and prevents duplicates such as 'MICROMETER' and 'MICROMETRE'.

## Pitfalls

- Leaving the method in 'created' status so it cannot be used in a plan.
- Writing the instructions into the MIC short text instead of a controlled method.
- Creating duplicate methods with slightly different names.
- Changing a method text without a new version, losing history.
- Assigning a method from the wrong plant.

## Ai Angle

Inspection methods drift: duplicates, outdated gauges, plans that point at old versions. A grounded assistant can list where each method is used, which plans still reference a superseded version, and which characteristics have none. Netray runs this read-only analysis against your SAP data on your own servers, which suits quality records that must stay inside the plant network.

## Faq

### What is the tcode to create an inspection method in SAP QM?

**Answer:** QS31 creates it, QS32 changes it and QS33 displays it. The method is then assigned in QS21 for master inspection characteristics or in the inspection plan.

### Is an inspection method mandatory for a characteristic?

**Answer:** No. It is optional in the master data, but without one the inspector has no linked instruction on how to measure the characteristic, so most quality systems require it.

### How do I change an inspection method without affecting old lots?

**Answer:** Create a new version and release it. Existing inspection lots keep the version they were created with, so history stays accurate.

### Why can I not select my method in the inspection plan?

**Answer:** Check the plant, status and validity. Only released methods valid on the plan's key date appear. Also check whether the method belongs to the same plant as the plan.

## Search terms

how to create inspection method in sap qm, sap qs31 inspection method, sap inspection method master inspection characteristic, sap qm inspection method task list, sap qm master data inspection method, inspection plan method sap, qs32 change inspection method

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
