QA32 — Change Inspection Lots Worklist

QA32 opens a selection screen for inspection lots and returns an ALV list rather than acting as a single-lot editor. It is the change-mode worklist for inspection lots: enter plant, material, lot number range, lot origin, inspection type or status, and the system returns every lot matching those criteria for further processing. The structural fact that explains most confusion is that QA32 does not itself record results or usage decisions, it only assembles the worklist. Drilling into one lot from the list, or invoking a list function such as mass usage decision or mass release, takes the user into the same underlying logic as QA02, QA11 or QE01. Consultants who expect QA32 to behave like a standalone data-entry transaction are usually looking for QA02 instead.

QA32 is reached for during routine inspector or supervisor work: building a shift worklist of lots awaiting a usage decision, finding lots stuck in a particular status across several materials, or doing a batch cleanup before month end (releasing or closing a backlog of lots). It sits between goods receipt, in-process inspection, and stock posting in the quality process, wherever more than one lot needs the same treatment at once. A consultant reaches for QA02 or QA03 when the exact lot number is already known and only that lot needs attention; QA32 is chosen when the starting point is a set of criteria rather than a lot number. On newer releases a Fiori worklist app covers similar ground with a different selection experience, but the underlying data and status logic are the same.

The practical sequence for QA32 in daily use follows a fixed pattern.

Pull the lot from QALS by plant and material to get the lot number and its object number (field OBJNR). Check JEST for that object number, joined to TJ30T, to see the exact status texts currently set (for example whether a usage decision has been entered but the lot is not yet marked complete). If a stock movement was expected, search MSEG by material and plant for a document dated around the usage decision date; its absence with a status showing UD entered but not posted indicates the goods movement failed silently and needs to be re-triggered rather than re-entered.

QA32 is available on S/4HANA and functions the same way as on ECC; the selection screen, ALV list, and mass functions are unchanged. SAP has introduced Fiori worklist apps for managing and processing inspection lots as a modern alternative entry point, but they read and write the same underlying inspection lot data (QALS and related tables) rather than replacing it. QA32 has not been withdrawn or formally deprecated.

This is a functional QM problem in the first instance. Stock posting failures after a usage decision cross into Materials Management and need an inventory management colleague to confirm the movement type and posting logic. Basis involvement is limited to authorization object assignment and clearing genuine lock conflicts. A good handover includes the lot number, plant, the exact status texts from status management, and any material document number expected but missing.

QA02 and QA03 cover the single-lot change and display views that QA32 ultimately drills into, and are the right first stop when the lot number is already known. QA33 is the display-only counterpart to QA32 and is safer for pure review work. QA11 and QA12 handle usage decision entry and change directly, useful when the mass UD function in QA32 is not appropriate for a lot. QE01 and QE51N cover results recording, which is often the step that must be checked before a usage decision will even be offered from the QA32 list. QM01 through QM03 govern the inspection type master data that determines which lots are eligible to appear on the selection screen at all.