QA33 — Display Inspection Lot List

QA33 builds a report-style worklist of inspection lots based on a selection screen (plant, material, order, batch, inspection type, lot origin, date range, status flags) and displays the results in a list from which any individual lot can be opened in display mode. It is the read-only sibling of QA32, which offers the same selection logic but allows mass or individual change. The structural fact that causes most confusion is that QA33 shows nothing about lots that do not match the selection criteria; a lot that genuinely exists in the system can be completely absent from the list because a status checkbox, plant restriction, or date window silently excluded it. Consultants new to the transaction often mistake this for a data problem when it is a selection problem.

QA33 is reached for whenever the question is about a set of lots rather than one lot: checking the backlog of open lots for a plant before month end, auditing all lots closed last week, confirming that usage decisions were actually posted for a batch of receipts, or exporting a list to a spreadsheet for a quality audit. QA03 is used instead when the identity of one specific lot is already known. QA32 is used instead when the same list needs to be changed in place, for example setting usage decisions on several lots at once. In S/4HANA landscapes with quality monitoring apps available, those apps may be preferred for dashboard-style review, but QA33 remains the fastest way to get an ad hoc list with full selection control.

Run SE16 or SE16N on QALS filtered by plant and material to get the candidate lot numbers and their object number field. Take that object number into JEST to see the active status entries and compare them against the checkbox the user expected to match in QA33 (open, usage decision set, closed, and so on). If a lot exists in QALS but was missing from the QA33 list, the mismatch is almost always between the actual JEST status and the status flags selected on the QA33 screen, not a missing record.

The inspection lot data model is unchanged on S/4HANA; QALS remains the header table and was not absorbed into the universal journal, so QA33's selection and display logic behaves the same as on ECC. S/4HANA does add Fiori-based quality monitoring apps aimed at dashboard-style review of open lots, but QA33 continues to work exactly as before and is still the transaction consultants reach for when they need a precise, criteria-driven list rather than a tile-based overview.

This is functional QM territory; the quality consultant owns the selection logic, status profile design and interpretation of results. Basis involvement is limited to authorization objects restricting plant or inspection type visibility. ABAP involvement is rare and only needed for custom selection variants or list layout enhancements. A good handover states the exact selection criteria used, the plant, and which status checkboxes were set, not just 'the lot is missing'.

QA32 is the direct next step for anyone who needs to act on the list rather than just view it. QA03 is the equivalent single-lot display for drilling into one lot without running a selection. QA12 shows the usage decision detail that QA33's list only summarizes. QE51N covers results recording for lots that appear open in the list. QM03 is useful when a lot's defects have generated a linked quality notification that needs separate review.