QA03 — Display Inspection Lot

QA03 opens an inspection lot in display mode and shows its header (material, plant, lot origin, quantities), the characteristics assigned for inspection and any results already recorded against them, the usage decision if one has been made, and the linked stock postings. The one fact that explains most support tickets around this transaction: QA03 never lets anyone write anything. It is the twin of QA02, which has an identical screen layout but with editable fields. Consultants and end users routinely land on QA03 from a worklist or a report, try to key in a result or a usage decision code, and conclude the system is broken when in fact they are simply in the wrong transaction.

QA03 is reached for during any investigation where the goal is to see state, not change it: confirming whether a lot has already been assigned a usage decision before someone tries to post one again, checking whether a specific characteristic result was recorded correctly after a complaint about a released batch, verifying stock quantities tied to the lot before a physical inventory discussion, or pulling up a lot referenced in an incident ticket to see its origin and status. It is also the safe transaction to hand to a business user who needs visibility into inspection history but has no authorization to change quality data. QA32 is used instead when the need is a worklist across many lots; QA02 or QE51N are used the moment an actual change is required.

In SE16 or SE16N, open the inspection lot header table (QALS) and filter by the lot number, or by material and plant if the lot number is not known. Confirm the origin field to see how the lot was created (goods receipt, in-process, manual) and check the status-related fields to see whether the lot is still open, has a usage decision, or is stock-posted. From there, cross-reference the lot number against the characteristics results table and the usage decision table to confirm whether a result or decision genuinely exists in the database versus simply not being visible on the QA03 screen due to a selection filter.

The inspection lot object and the QA03 screen behave the same on S/4HANA as on ECC; there is no structural redesign of the lot header or its display logic. S/4HANA adds Fiori-based monitoring apps for inspection lots that give a worklist view with drill-down, which are convenient for mass review, but the detailed single-lot display that QA03 provides is still reached through the classic transaction in most implementations and remains the reliable fallback when the Fiori app filters do not surface a specific lot.

This is functional QM territory; QA03 itself has no configuration to break, so issues are almost always about the underlying lot data or the process that created it, not the transaction. ABAP involvement is limited to custom status logic or interfaces feeding lot data. A good handover includes the lot number, material and plant, what the user expected to see on which tab, and confirmation of which transaction (QA02 versus QA03) was actually used.

QA02 is the natural next stop, since it is the editable version of the same screen and the place most QA03 confusion resolves itself. QA01 explains how the lot was created in the first place, which matters when a lot cannot be found under expected selection criteria. QA32 is the worklist transaction used when the investigation spans many lots rather than one. QE51N is where actual result recording happens and is often the transaction the user meant to use instead of QA03.