QAVE table — Inspection Lot Characteristic Valuation Table

A row in QAVE represents the valuation of one inspection characteristic for one inspection lot: the conclusion drawn after results were recorded, comparing what was measured or observed against the specification carried on the lot. It answers the question 'was this specific characteristic accepted or rejected', separately from the overall usage decision on the lot header. Quantitative characteristics carry accepted and rejected quantities; qualitative characteristics carry a pass or fail style code. The valuation can be generated automatically by the system from the recorded result against tolerances, or entered and overridden manually by the inspector during results recording. Because the valuation is characteristic-level, a single lot with ten characteristics can have ten QAVE rows, some accepted and some rejected, well before the header-level usage decision is set in QALS.

MANDT is the first restriction in any client-dependent SAP system with multiple clients. After that, always restrict on PRUEFLOS; the table has no useful secondary index for browsing by plant, material, or date, because none of those fields live here directly. To find lots for a material or plant, filter QALS first, then use the resulting PRUEFLOS values to select from QAVE. Selecting QAVE without a PRUEFLOS restriction on a live production system is a full table scan across every characteristic of every lot ever created and will be slow. When a lot has several inspection points or partial results, expect several valuation rows per characteristic over time, not just one; check the most recent by whatever sequencing the results recording (QAMR) history implies rather than assuming one row is definitive.

Symptom: a lot's usage decision shows partial rejection but the reason is not obvious from the header alone. Select QAVE where PRUEFLOS equals the lot number, ordered by MERKNR, and read the valuation code per characteristic. Any characteristic showing rejected is a candidate cause. Cross-check that row against QAMR for the same PRUEFLOS and MERKNR to see the actual recorded value or attribute, and against QAMV for the same keys to see the specification and tolerance it was judged against. This chain confirms which specific characteristic drove the rejection and whether the valuation was automatic or manually forced.

QAVE continues to exist in S/4HANA in the same shape as in ECC; the inspection lot data model was not restructured as part of the S/4 simplification effort in the way finance or logistics documents were. Newer Fiori based quality apps for monitoring inspection results and usage decisions read through CDS views built on top of QALS, QAMR, QAMV, and QAVE rather than replacing the underlying tables, so the table itself remains the correct place to look when reconciling what a Fiori app is showing against the raw data.

The QM configuration and master data team owns the setup that determines how and when characteristic valuations are generated, including tolerance settings and automatic valuation rules. The plant quality engineer or inspector owns whether a specific recorded valuation, especially a manual override, was correct. Disputes over why a lot was rejected on a specific characteristic sit with quality, not with the functional consultant unless the automatic valuation logic itself is suspected of misconfiguration.

QALS holds the inspection lot header and the overall usage decision that QAVE feeds into. QAMR holds the individual recorded results, quantitative or qualitative, that generate each QAVE valuation. QAMV holds the characteristic specification copied onto the lot that the valuation is measured against. Results are recorded through transaction QE51N, the usage decision is set through QA11, and the lot can be reviewed or changed through QA32; all three transactions read or write QAVE indirectly through the results recording and usage decision processes.