QE51N — Record Results for Inspection Lots

QE51N is the entry point for recording inspection results against an open inspection lot. A user selects a lot (or works from a worklist), the system displays the characteristics due for that operation, and the user enters values, defects, or attribute pass/fail decisions against each one. The structural fact that explains most confusion: QE51N is a consolidated single-screen transaction covering several different recording scenarios that used to be separate transactions (lot-related, sample-related, without inspection lot, equipment-based). Which sub-screen, which fields, and which valuation logic appear depend entirely on which selection tab and object type was chosen on entry, so two consultants describing 'results recording' may be looking at structurally different screens even though both call it QE51N.

QE51N sits between inspection lot creation and the usage decision. A lot is created (manually via QA01, or automatically from a goods receipt, production order confirmation, or delivery), the lot carries a set of characteristics copied from the inspection plan at creation time, and QE51N is where those characteristics get values. A consultant reaches for QE51N directly when troubleshooting why a lot cannot be closed, when reproducing a data entry error reported by shop floor, or when checking whether recorded values match tolerance limits. In production, actual entry is often done through a Fiori result recording app, an MES/LIMS interface posting results via API, or handheld devices — QE51N is the fallback and the diagnostic tool when those interfaces fail or disagree with what is stored.

Start in QALS filtered on the inspection lot number (field PRUEFLOS) and read the status field to confirm whether results were actually recorded before someone claims they were not, and whether a usage decision already closed the lot. Then query the results table filtered on the same PRUEFLOS plus the characteristic number (MERKNR) to see the recorded value, the valuation flag, and the entry timestamp and user. Compare the characteristic sequence on the lot against the current inspection plan in QP03 — a plan change after lot creation does not retroactively appear on an already-open lot, which is a frequent source of 'why is this characteristic missing' questions.

QE51N is not an S/4HANA-specific transaction; it was introduced as the unified results recording transaction well before S/4HANA and already replaced the older separate QE0x transactions in ECC. On S/4HANA the transaction and underlying tables are unchanged. A Fiori app for recording quality inspection results is available for simpler, single-lot entry scenarios, typically used by shop floor operators, while QE51N in SAP GUI remains the tool for multi-characteristic, multi-lot, or diagnostic work.

This is a functional QM problem in almost all cases. ABAP involvement is only needed if a custom user exit or BAdI drives characteristic selection or automatic valuation. Basis is relevant only for lock and authorization errors. A good handover includes the inspection lot number, plant, material, characteristic number, the exact status string from QALS, and a screenshot of the entry screen at the point of failure.

Read QA01 and QA02 first to understand how a lot is created and what determines its status before results even begin. QA11 explains what happens after QE51N saves, since the usage decision consumes the recorded results. QP01 and QP02 show where the characteristic sequence and tolerance limits actually come from, which resolves most missing-characteristic questions. QS21 and QS23 are worth checking when defect recording inside QE51N references a catalog code that seems wrong or missing.