QAMV table — Inspection Lot Single Results Table

One row represents a single recorded measured value captured during results recording for one inspection characteristic within one inspection lot. It exists for characteristics that require multiple individual readings rather than a single summarized entry, for example a sample of five units where each unit's measurement must be retained separately to support mean, range or standard deviation calculations, or to support traceability back to an individual reading. The table sits below the characteristic-result record in the data model: the inspection lot record identifies the inspection as a whole, the characteristic result record identifies which characteristic was inspected and its overall valuation, and this table holds the raw individual values that fed into that valuation. Not every characteristic generates rows here. Qualitative characteristics and quantitative characteristics recorded as a single summarized value never populate this table.

Always restrict on MANDT and PRUEFLOS before doing anything else; this table grows with every sample-based reading across every lot in the plant and an unrestricted join to it in a high-volume production environment will run long. Restrict by MERKNR as soon as it is known, since a single lot can carry dozens of characteristics. Do not assume row count per characteristic equals the configured sample size without checking, since partial results recording, rework, or re-recording can leave a count that does not match. Use LFDNR to order the readings but do not treat it as a physical sample or unit identifier unless sample management is separately in use.

Symptom: a characteristic on an inspection lot shows a valuation in results recording but a quality engineer or auditor wants to see the individual readings that produced it. Select QAMV on the exact PRUEFLOS and MERKNR, order by LFDNR, and count the rows against the sample size expected for that characteristic. Cross-check the mean of the values against the valuation stored on the corresponding QAMR record; a mismatch usually points to a re-recording that was not fully reset rather than a calculation error.

The table carries forward into S/4HANA with the same structure and role in the results recording data model; the QM results recording area has not been restructured the way some logistics tables have. No dedicated CDS compatibility view specific to this table is commonly referenced in QM reporting content, so custom reporting built on it in ECC generally continues to work unchanged in S/4HANA, subject to the usual regression testing.

This is a QM consultant and plant quality engineer question, not a materials management or production planning one. Disputes over what a recorded reading actually was are resolved by pulling this table alongside the characteristic result and the inspection lot header, then walking the quality engineer through the sequence of readings rather than relying on the summarized valuation alone.

Sits directly beneath QALS (inspection lot header) and QAMR (characteristic result and valuation) in the results recording chain, and is closely related to QASE for sample-related characteristic data. Populated through results recording transactions such as QA11 and QA12, and reviewed through the inspection lot display transaction QA32; changes to a lot's status or a decision made in usage decision processing can affect whether these rows are considered final.