SAP QM inspection results report: which tcode shows what
sap qm inspection results report
Also searched as
- sap qm report tcode
- inspection report in sap qm
- mic report in sap qm
- sap qm result recording report
Short answer
Use QA32 for the list of inspection lots, QE51N or QE03 for recorded results, the QM information system (for example QM12) and QGC2 for evaluations of characteristics over time, and QA11 or QAVE for usage decisions. If none fits, read the tables QALS, QAMV, QAMR and QAVE directly.
Applies to: SAP ECC 6.0 and S/4HANA on-premise; some Fiori apps exist in S/4HANA
Choose the right report for the question
- 1Which lots exist and in what state: run QA32 (Inspection Lot List), select by plant, material, date, status and origin, and use the layout to add columns such as inspection quantity and usage decision code.
- 2What results were recorded for a lot: use QE03 (Display Results) or open the lot in QA33 and navigate to results; QE51N shows the worklist of characteristics still to be recorded.
- 3How a characteristic behaves over time (MIC history): run a characteristic evaluation from the QM information system, such as QM12 where it is available in your menu, or build a control chart in QGC2.
- 4What decisions were taken: open the usage decision list from QA32 with the decision code column, or use the quality score evaluations for scores by vendor or material.
- 5Which vendors or materials have most defects: use the quality notification list IQM1 together with the defect catalog codes.
- 6If a standard report does not give the layout you need, create a query or a CDS-based report on the tables below, or export from QA32 to spreadsheet.
- 7Save selection variants for each recurring report so the quality team runs the same selection each time.
The core tables behind every QM report
All standard QM reporting reads a small set of tables. QALS is the inspection lot header with material, plant, origin, inspection type, quantities and status flags. QAMV holds the specification of each characteristic in the lot, QAMR the recorded results per characteristic, QASR the results per sample unit, and QAVE the usage decision. QMEL is the quality notification header.
Knowing this lets you debug a report that disagrees with the screen: if QE03 shows a result and your report does not, the report is usually filtering on a status or reading the wrong lot origin. Join QALS to QAMV on PRUEFLOS (inspection lot) and to QAMR on PRUEFLOS and VORGLFNR (operation sequence) and MERKNR (characteristic number).
QALS PRUEFLOS, MATNR, WERK, ART, LOSMENGE, ENSTEHDAT
QAMV PRUEFLOS, VORGLFNR, MERKNR, VERWMERKM (master characteristic), SOLLWERT, TOLERANZOB, TOLERANZUN
QAMR PRUEFLOS, VORGLFNR, MERKNR, MITTELWERT (mean), ORIGINALWERT (result)
QAVE PRUEFLOS, VCODE (decision code), VDATUM, VNAME
Result recording and why results look missing
Results are recorded in QE01 (by lot and operation) or in QE51N (worklist). Reports only see results that have been saved with a valid status; characteristics that were skipped or that are still in recording show as open. If a report seems empty, check the lot is in status REL or later and that the characteristic was set up for results recording.
Qualitative characteristics store a code selection rather than a numeric value, so they cannot feed an SPC chart. Only quantitative characteristics appear with mean values in QAMR and are suitable for statistical evaluation.
MIC reports and evaluations over time
A master inspection characteristic (MIC) report answers how a specific characteristic has performed across lots, plants or vendors. The quality control chart functions (QGC1 and QGC2) work from the same data. Choose the characteristic, the time window and the chart type, and the system builds the chart from the results in QAMR.
For compliance exports such as a certificate of analysis or a goods receipt record, check whether your release has a quality certificate function (QC20 and QC21 are the usual quality certificate transactions) before building a custom report.
Custom reports and S/4HANA options
If the standard output does not match, an ABAP query (SQ01), an SE16N export or a CDS view on QALS, QAMV and QAMR is faster than modifying a standard report. In S/4HANA, check the Fiori apps catalog for quality inspection and results analysis apps, which can replace a number of classic list transactions depending on the release.
Try it here, free
SAP QM Inspection Results Recording Worksheet
Record measured values per characteristic, see deviation from target and in-tolerance status, and keep a paper copy to key into SAP QE51N.
Common pitfalls
- !Reporting on QALS alone and counting lots rather than characteristics, which hides which attribute failed.
- !Including cancelled lots in statistics because the status filter was left open.
- !Mixing quantitative and qualitative characteristics in one chart.
- !Using screenshots as quality records instead of the saved results in QAMR, which break when a lot is reset.
- !Assuming a transaction code in your menu is the same as in a different release; verify the menu path.
How an ERP-grounded AI assistant handles this
Quality managers often know the question but not the tcode. A grounded assistant can translate a plain question such as which lots failed dimension A this quarter, show the table query it ran against QALS, QAMV and QAMR, and return the table. It reads on-prem under existing QM roles, and leaves any change to the people who own the records.
Frequently asked questions
Which tcode shows inspection results in SAP QM?
QE03 displays recorded results for a lot, QE51N is the results worklist, and QA32 lists the lots themselves. For trends over time, use the QM information system evaluations or a control chart in QGC2.
What tables store SAP QM inspection results?
Results are in QAMR at characteristic level and QASR at sample level. QALS holds the lot header, QAMV the characteristic specification and QAVE the usage decision. Join them on the inspection lot number PRUEFLOS.
How do I report on a master inspection characteristic?
Use a characteristic evaluation from the QM information system or build a control chart in QGC1 and QGC2 for the characteristic. Both read the recorded values in QAMR across the selected lots and period.
Why does my QM report not show results I entered?
Typically the results were not saved, the lot is not released, the selection excludes the lot origin or status, or the characteristic is qualitative and the report expects numeric values. Compare with QE03 for the same lot.
Related
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.
How-toSAP QM SPC: control charts, Cpk and stability studies
SAP QM supports statistical process control through quality control charts, created in QGC1 and evaluated with QGC2, fed by quantitative results recorded in inspection lots. Cpk and process capability indices are calculated from those results. Stability studies are a separate, time-based sampling function used mainly in regulated industries.
How-toHow to release (and cancel) an inspection lot in SAP QM
Open the lot in QA02, check the system status, and use the Release function so the status moves from CRTD (created) to REL (released); only then can results be recorded in QE01 and a usage decision made in QA11. To cancel a lot, use the cancel function in QA02, which only works while no usage decision exists and no stock posting blocks it.
How-toSAP SE16N vs SQVI: Table Browser vs Ad Hoc Query
SE16N is a single-table browser: fast filtering, formatted display, and export from one table at a time, with an optional edit function for authorized users. SQVI (Quick Viewer) builds ad hoc queries that join multiple tables without writing ABAP, and can be saved as a reusable report. Use SE16N for a quick look at one table; use SQVI when you need data joined across two or more tables.
Error fixSAP 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 fixSAP 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 ERPAI 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.
Stuck on SAP ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP QM Inspection Results Recording WorksheetRecord measured values per characteristic, see deviation from target and in-tolerance status, and keep a paper copy to key into SAP QE51N.
- SAP QM Tables Map: Notification, Inspection Plan and ResultsFind the SAP QM table for a quality notification, inspection plan, sample or result, with key fields and the table it joins to.
- SAP QM Inspection Lot ABAP SELECT GeneratorFill in plant, inspection type and date range and get a ready ABAP SELECT joining the inspection lot table QALS to the usage decision table QAVE.
ERP fixes and how-tos
- Inspection Results and Inspection Plan Reports in SAP QMWhich SAP QM transactions report inspection results and inspection plans? Use QA32, QE03, QGC1 for evaluation and QP19 for plan lists, plus the QM tables behind them.
- SAP QM QA32: user exits, enhancements and standard lot reportsOptions to customise the QA32 inspection lot list, how to find user exits and BAdIs, and the standard SAP QM lot and results reports you can use instead.
- SAP QM: Inspection Lot Not Created at Goods ReceiptWhy SAP QM creates no inspection lot at MIGO goods receipt: QM view, inspection type 01 or 04, QM control key, plant activation, and the QA32 checks to run.