How-toSAP QMQuality Management / Procurement and Returns

What is a quality info record in SAP QM, and how do customer returns trigger inspection?

Question
what is quality info record in sap qm

Also searched as

  • sap qm customer return
  • qi01 quality info record
  • sap qm returns inspection

Short answer

The quality info record is a QM master record per material, vendor and plant that stores quality control data for procurement, such as whether inspection is required and which release or block controls apply. Customer returns are a separate flow: the returned goods are received and can be put into inspection through the return process.

Applies to: SAP ECC and S/4HANA QM.

Create and use a quality info record

  1. 1Activate QM in procurement for the plant and set the QM control key in the material master QM view.
  2. 2Create the record in QI01 for the material, vendor and plant and save the control data.
  3. 3Set the QM control key (and assigned inspection type) in the record, plus any release or block information needed for your process.
  4. 4Check the record is used when a purchase order and goods receipt are created, so the inspection lot is generated.
  5. 5Use QI02 to change and QI03 to display, and review blocks when a vendor is under quality hold.
  6. 6For customer returns, configure the return order type and receipt so goods go to quality inspection stock and an inspection lot is created.

What the record controls

It holds the quality-related release for a vendor and material combination: whether the vendor is allowed to deliver, whether inspection or a certificate is required, and the control key that defines what happens at goods receipt. It is the link between purchasing and QM at the vendor level.

How it interacts with the material master

The QM view of the material master and the plant-level QM procurement settings must agree with the quality info record. When a record is missing and the QM control key demands one, the system raises an error at purchase order or receipt. This is a frequent source of procurement errors.

QI01  Create quality info record
QI02  Change quality info record
QI03  Display quality info record

Customer returns and QM

A customer return starts with a returns sales order and a returns delivery. On goods receipt the stock can be posted to quality inspection stock, and an inspection lot is created if an inspection type for the return is activated for the material. The usage decision then decides whether goods go to unrestricted, blocked or scrap. A quality notification can capture the customer complaint.

Try it here, free

SAP QM in Procurement Setup Checklist

Open full tool

Check each step needed to run goods receipt inspection for purchased materials, from QM control key to vendor release.

Common pitfalls

  • !Setting a QM control key that requires a quality info record, then not creating it.
  • !Mismatch between plant QM procurement activation and material QM view.
  • !Forgetting to activate the inspection type for returns.
  • !Letting blocks remain after the vendor issue is resolved.
  • !Not linking the complaint to a quality notification.

How an ERP-grounded AI assistant handles this

An assistant grounded in SAP can answer which vendor and material pairs lack a quality info record, or which returns have no inspection lot, by reading the data read-only. Netray builds this to run on-prem alongside SAP.

Frequently asked questions

What is the quality info record used for?

It stores QM control and release data for a vendor and material at plant level, used during procurement and goods receipt.

Which transaction creates it?

QI01 creates it, QI02 changes it and QI03 displays it.

Do customer returns create an inspection lot?

They can, if the inspection type for returns is configured and activated for the material. Otherwise stock is received without inspection.

What happens if the record is missing?

If the QM control key requires one, the purchase order or goods receipt fails with an error until it is created or the key is changed.

Related

Error fix

Define QM Procurement Key Error in SAP: What It Means and the Fix

The QM procurement key error appears when a material or plant is set up for QM in procurement but the required key has not been defined or assigned. Define the key in customizing (transaction OMJ7, under QM in Procurement), then assign it in the material master QM view (MM02) alongside the QM control key and inspection setup.

Error fix

SAP QM: Inspection Lot Not Created at Goods Receipt

An inspection lot is created only when QM is active for the plant, the material has an active inspection type for the goods movement, and the material carries a QM control key. Check the Quality Management view in MM02, confirm inspection type 01 (purchase order) or 04 (production order) is active, then check QM activation in the plant and the goods movement used.

How-to

How to create a quality notification in SAP QM (QM01) and set up an 8D report

Run QM01, pick the notification type (Q1 customer complaint, Q2 complaint against a vendor, Q3 internal problem), fill the header and item, then add causes, tasks and activities to track the problem to closure. An 8D report is not a separate object: it is a print form over the notification, configured in customizing.

How-to

QM order cost recording and settlement in SAP

A QM order is a cost collector for inspection effort. Costs such as labour confirmed against it and external services are posted to the order, and at period end the order is settled to a receiver, typically a cost center, using a settlement rule and settlement profile. It is a Controlling process as much as a Quality one.

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.

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 SAP S/4HANA, Running On-Prem or in Your Private Cloud

Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.

Stuck on SAP QM?

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