SAPFree referencePDF, Excel, Word exportSAP S/4HANADiscrete Manufacturing

SAP QM Transaction Codes List (QA01, QE51N, QM01, QP01 and More)

Quality consultants and key users spend their day in a small set of QM transactions. This list groups them by task so you can find the right code for an inspection lot, a result, a usage decision, a notification or a piece of master data.

Download:

T-code	Description	Group
QA01	Create inspection lot manually	Inspection lot
QA02	Change inspection lot	Inspection lot
QA03	Display inspection lot	Inspection lot
QA32	Inspection lot overview (list of lots)	Inspection lot
QE01	Record results for inspection lot	Results
QE02	Change inspection results	Results
QE03	Display inspection results	Results
QE51N	Results recording worklist	Results
QA11	Record usage decision	Usage decision
QA12	Change usage decision	Usage decision
QA13	Display usage decision	Usage decision
QM01	Create quality notification	Notification
QM02	Change quality notification	Notification
QM03	Display quality notification	Notification
QP01	Create inspection plan	Inspection plan
QP02	Change inspection plan	Inspection plan
QP03	Display inspection plan	Inspection plan
QS21	Create master inspection characteristic	Master data
QS22	Change master inspection characteristic	Master data
QS23	Display master inspection characteristic	Master data
QS61	Create inspection method	Master data
QS62	Change inspection method	Master data
QS63	Display inspection method	Master data
QS31	Create code group (catalog)	Catalogs
QS32	Change code group	Catalogs
QS33	Display code group	Catalogs
QS41	Create selected set	Catalogs
QS42	Change selected set	Catalogs
QS43	Display selected set	Catalogs
QDV1	Create sampling procedure	Sampling
QDV2	Change sampling procedure	Sampling
QDV3	Display sampling procedure	Sampling
QDP1	Create sampling scheme	Sampling
QDP2	Change sampling scheme	Sampling
QDP3	Display sampling scheme	Sampling
QDR1	Create dynamic modification rule	Sampling
QDR2	Change dynamic modification rule	Sampling
QDR3	Display dynamic modification rule	Sampling
QCC1	Create certificate profile	Certificates

Transaction codes are for SAP GUI. In S/4HANA some tasks also have SAP Fiori apps, and a few legacy transactions are replaced or flagged in the simplification list for your release. Check SE93 in your own system.

Need QM answers without hunting for t-codes?

An optional conversation about read-only natural-language access to your SAP quality data.

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

How to use the list

Search by code or by the task, for example usage decision or sampling. The Group column keeps related transactions together, and the create, change and display variants always end in 1, 2 and 3 for the main QM master data objects. Export the rows to Excel or PDF to build a training cheat sheet for key users, or paste them into an authorization design workbook so that each role maps to the correct transactions.

Typical QM process in transactions

In a standard in-house production or goods receipt flow the system creates the inspection lot automatically when the trigger event happens. The inspector finds it in QA32 or in the worklist QE51N, records results, and the quality engineer records the usage decision in QA11, which posts stock to the target stock type. Problems found along the way go into a notification created with QM01. Behind all this sit the inspection plan from QP01, master characteristics from QS21 and catalogs from QS31 and QS41.

Using the list for authorizations

Transaction codes are the starting point of role design, but SAP checks authorization objects as well as the code. Map each code to the persona that needs it, then verify the QM authorization objects for plant and inspection type in PFCG. Keep display codes in a wide role and create or change codes in narrower ones. Test each role with a user who has no other access, because stray authorizations hide gaps.

Inspector: QE51N, QE01, QE03, QA32
Quality engineer: QA11, QM01, QM02, QP02
Master data owner: QS21, QS31, QS41, QP01
Auditor: display codes only (QA03, QM03, QP03, QS23)

Common mistakes

Teams often train users on transactions that their release no longer favours, or give create rights where display is enough. Check the Fiori app catalog for your release before writing training material, and remember that a transaction listed here may still be blocked by a missing authorization object, a missing plant assignment or a missing QM view on the material master.

Frequently Asked Questions

What is the transaction code to record a usage decision in SAP?

QA11 records the usage decision for an inspection lot. QA12 changes it and QA13 displays it. The decision triggers the stock posting to unrestricted use, blocked, scrap or another target depending on the code you choose.

What does QE51N do in SAP QM?

QE51N is the results recording worklist. It lists inspection lots and operations ready for result entry and lets the inspector record characteristic results from one screen, which is faster than opening each lot separately with QE01.

Which t-code lists all inspection lots?

QA32 gives the inspection lot overview, with selection by plant, material, inspection type, origin, dates and status. It is the standard starting point for lot lists and the place from which users reach results recording and the usage decision.

How do I create a quality notification in SAP?

Use QM01 and choose the notification type such as a customer complaint, a complaint against a vendor or an internal problem report. Fill in the material, defect data and coding, then save. QM02 changes it later and QM03 displays it.

If your key users spend time hunting through QM screens for answers, we can put a read-only natural-language layer over your SAP data so they ask for the lot or notification directly. It can run on-premises.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools