QA12 — Change Usage Decision for an Inspection Lot

QA12 changes a usage decision that has already been recorded for an inspection lot, normally via QA11. The consultant can correct the usage decision code, the associated catalog entries or long text, and in some configurations the stock posting proposal quantities. The structural fact that explains most confusion: the usage decision and the stock posting it triggers are two separate events in the system. If the original UD already generated a goods movement, QA12 reopening the decision does not reverse that movement automatically. Changing the code from, say, an acceptance decision to a rejection decision after stock has already moved to unrestricted use leaves the lot's UD text correct but the physical and system stock wrong until someone manually reverses the earlier posting.

Used after the fact, never as the first step in the inspection workflow. A quality engineer reaches for QA12 when the wrong usage decision code was entered in QA11, when additional inspection results or a lab retest arrive after the initial UD was posted, when a customer complaint forces a reassessment of stock already released, or when a lot needs its posting proposal corrected before the batch is shipped. It sits downstream of QA11 (record UD) and QE01/QE51N (results recording) in the inspection process, and is reached for specifically when someone needs to undo or amend a decision rather than make a fresh one.

Pull QALS by the inspection lot number to read the current usage decision code and status flags. Cross check QAVE for that same lot number to see what stock posting proposal was saved with the decision. If a stock movement was generated, search MSEG for the material document tied to the lot period and material, since the inspection lot reference usually appears in the movement's reference fields. To see what actually changed and when, pull change documents for object type QALS through the standard change document tables, filtering on the lot number and the usage decision fields.

QA12 behaves the same way on S/4HANA as on ECC; the underlying tables and the separation between usage decision and stock posting are unchanged. There is no dedicated Fiori app that replaces the change-usage-decision use case specifically; Fiori apps for quality inspection largely cover recording a new usage decision, and correcting an existing one still runs through this classic transaction.

Functional QM issue in the first instance. If a stock movement already tied to the original decision needs reversal, inventory management or MM ownership is required for that reversal before the UD change is safe. ABAP involvement is rare, typically only if a custom UD workflow or approval step is in place. A clean handover includes the lot number, the original and intended usage decision codes, and any material documents already posted against the lot.

Start with QA11 to understand how the usage decision was first recorded, since QA12 only makes sense against that baseline. QA32 is the practical way to find the lot when only partial information is known. QA01, QA02 and QA03 cover lot creation, change and display for context on the lot's inspection setup. QE01 and QE51N show where the results feeding the original decision came from. QS21 and QS23 explain the catalogs the usage decision codes are drawn from, useful when the available codes on QA12 do not match expectations.