QA11 — Record Usage Decision for an Inspection Lot

QA11 is where the usage decision (UD) for an inspection lot is entered. The UD is a code, drawn from a catalog assigned to the inspection type, that states what the inspected quantity should become: accepted, rejected, scrapped, returned, or a custom variant defined by the plant. The single fact that explains most confusion around QA11 is that the UD is not a passive record of a decision already implemented elsewhere - saving it can itself trigger the goods movement, moving stock out of quality inspection into unrestricted-use or blocked stock via the inventory management interface. If that posting logic is not configured, or the lot's quantities are inconsistent, the UD saves but the physical stock status does not change, and the mismatch surfaces later as a stock discrepancy rather than an error on this screen.

QA11 is reached after inspection results have been recorded, usually through QE51N or a mobile/Fiori results recording app, and the lot needs to be formally closed. It is a manual step used where dynamic modification rules do not auto-close the lot, or where a human sign-off is required regardless of automated valuation. A consultant reaches for QA11 specifically when a lot is stuck open in quality stock and goods movement is expected but has not happened, or when investigating why stock intended for release is still sitting in inspection. It is distinct from QA12, which changes a decision already recorded, and from QA32, which is the worklist for handling many open lots at once rather than one lot at a time.

In SE16 or SE16N, open QALS and filter by the inspection lot number or by material and plant with a status range covering open lots. Check the usage decision code field and status flags to confirm whether a UD has actually been saved, as opposed to the lot simply being closed for results entry. Then open MSEG filtered on the same inspection lot number (via the reference fields carried on the material document) to confirm whether a corresponding goods movement was generated; a UD with no matching MSEG entry, where the UD code is configured for automatic posting, points straight at a posting failure rather than a data entry error.

The underlying logic and the inspection lot data model are unchanged on S/4HANA; QA11 still works the same way and remains the transaction most consultants use for a single lot. A Fiori app for recording the usage decision exists for users who work from a worklist rather than a lot number, and it calls the same backend logic, but it does not replace QA11 for exception handling or investigation work.

Functional QM territory for the decision itself and the catalog configuration behind it. Inventory management or MM colleagues get involved only when the stock posting side fails after a UD is saved. A good handover states the inspection lot number, plant and material, the UD code selected, whether a material document was expected, and the result of checking MSEG for that lot.

QA01, QA02 and QA03 cover the inspection lot itself before a decision is ever considered, and are the right place to check status and quantities when QA11 behaves unexpectedly. QA12 is the transaction for changing a usage decision already recorded and is the natural next stop when a reversal is needed. QA32 is the worklist view for handling usage decisions across many lots rather than one at a time. QE51N is upstream of QA11, since results must be recorded before a decision is meaningful, and QS41 defines the code groups that populate the usage decision catalog seen in QA11.