SAP QA11 Usage Decision: Make It and Post Stock Correctly
SAP QA11 usage decision stock posting how to
Also searched as
- how to make usage decision SAP QM
- QA11 inspection lot cannot make usage decision
- SAP usage decision stock posting unrestricted blocked scrap
- QA12 change usage decision
Short answer
The usage decision (UD) in QA11 closes an inspection lot, assigns a quality score and a UD code such as accepted or rejected, and posts the lot quantity from quality inspection stock to unrestricted use, blocked stock, scrap or return to vendor. The UD is blocked until required inspection characteristics are closed and results are recorded.
Applies to: SAP ECC 6.0 and SAP S/4HANA with QM. Inspection lots with stock posting active, manual and automatic usage decisions.
How to make a usage decision and post stock
- 1Open QA11 and enter the inspection lot number, or start from QA32 and select the lot and choose Usage Decision.
- 2Check the Inspection Results tab: all required characteristics must have results recorded and be closed. Record missing results in QE51N or QE11 first.
- 3Select the Usage Decision code from the code group, for example an accepted code or a rejected code defined in the selected set.
- 4Check or change the quality score if the score procedure is active; it can be calculated from the results or entered.
- 5Open the Stock Posting tab. Distribute the lot quantity across unrestricted use, blocked, scrap, returns, sample usage and new material as needed. The quantities must add up to the lot quantity.
- 6Save. The system posts the goods movements (for example movement type 321 from quality inspection to unrestricted) and sets the UD status on the lot.
- 7Check the result in MB51 for the material documents created and in QA32 for the lot status showing the usage decision made.
- 8For a wrong decision before posting complete, use QA12 to change it; for posted stock, correct with stock transfer movements rather than editing history.
What the usage decision actually does
The UD is the single step where QM tells inventory management what to do with the lot. It sets the valuation (accepted or rejected), writes a quality score, and triggers the stock posting. It also closes the lot for further results recording and can trigger follow-up actions such as a notification, a task, or an update of the quality level in the vendor evaluation.
Because the UD moves stock, the choice of codes matters. A code in a rejected group can be tied to automatic posting to blocked stock or return to vendor, depending on the configuration of the code. Ask your QM consultant to show you the selected set and the code settings before you let operators pick codes freely.
Why the UD will not save
The most common reason is that mandatory inspection characteristics are not closed. The system will not let you make a UD while required results are missing, because it cannot validate the decision. Record results with QE51N, close the characteristics, and try again. The second reason is the authorisation: the object for usage decisions controls who can set accepted or rejected, and some companies separate those roles.
A third reason is that the lot is already decided, in which case QA11 shows it in display mode. If the stock posting is mismatched, for example you try to post more than the lot quantity or the stock in quality inspection is already partly moved with a manual transfer, the system rejects the posting. Check MMBE or MB52 for the real quality inspection quantity before assuming a system error.
Changing and correcting a usage decision
QA12 changes a usage decision. Whether it is allowed after the stock posting depends on configuration and on the quantities that still sit in the relevant stock type. In many setups the change is allowed only for a lot without stock postings or with a quality score update only. Once the stock has left quality inspection, the clean way to correct is a goods movement.
Common corrective movements are 321 to move from quality inspection to unrestricted use, 322 for the reverse, 343 from blocked to unrestricted, 344 for unrestricted to blocked, 349 from blocked to quality inspection and 350 for quality inspection to blocked. Use them with a reference to the inspection lot so the audit trail shows why the stock moved.
-- Review in SE16N Table QALS (inspection lot: PRUEFLOS, STAT35 usage decision made, QKZVERF) Table QAVE (usage decision data: PRUEFLOS, VCODE, VCODEGRP, VWERKS) Table QAMV (characteristic results per lot) Table MSEG (stock postings: filter on BWART 321, 322, 343, 344, 349, 350)
Automatic usage decisions and dynamic modification
An automatic UD can be set in the inspection setup or the inspection plan. If all characteristics are accepted, the system makes the UD itself and posts stock without an operator. This cuts the queue of lots waiting for a decision, but it should only be used when the acceptance criteria are fully captured in characteristics, since a hidden defect then goes straight to unrestricted stock.
Dynamic modification rules change the inspection scope based on the quality history, for example moving from full inspection to skip lot. A lot can therefore have no stock posting because it was skipped, and the UD is made at creation. If you see lots with a UD and no results, check the dynamic modification rule before assuming data loss.
Common pitfalls
- !Making a UD before all required characteristics are closed, then wondering why the system blocks the save.
- !Splitting the lot quantity so it does not match the lot size, leaving stock in quality inspection with no lot open.
- !Changing UD codes after stock has been posted and expecting the goods movements to reverse themselves.
- !Enabling automatic usage decisions without complete acceptance criteria in the plan.
- !Giving all QM users the authorisation to set both accepted and rejected codes with no review.
How an ERP-grounded AI assistant handles this
An assistant grounded in your SAP data (ERPray, read-only by default) can list inspection lots waiting for a usage decision, ordered by age and stock value, and flag those stuck because characteristics are open, by reading QALS, QAMV and QAVE and showing the query. It does not post the decision. The usage decision and stock posting stay in QA11 with the inspector's authorisation.
Frequently asked questions
What is the difference between QA11 and QA32?
QA32 is the lot list used to find and select inspection lots by plant, material, date and status. QA11 is the usage decision transaction where you decide on one lot. From QA32 you can go straight to the usage decision for the selected lot. Both work on the same lot data in QALS.
Can I make a usage decision without recording results?
Only if the lot has no mandatory characteristics, for example lots created without a plan or lots with characteristics that are not required. Otherwise the system blocks the decision until required results are recorded and closed. Check the Inspection Results tab in QA11 for the open characteristics.
How do I reverse a usage decision after stock was posted?
QA12 may let you change the decision depending on configuration, but the stock that already moved does not return automatically. Post a corrective goods movement such as 322 or 350 with a reference to the inspection lot, and then make the right decision. Keep the audit trail with a clear text.
Why does QA11 show the lot in display mode?
The usage decision has already been made on that lot, or you lack the authorisation to change it. Check the lot status in QA32 for the UD made indicator and check your role for the usage decision authorisation object. If a change is justified, use QA12 if configuration allows it.
Related
SAP QM: Inspection Lot Not Created at Goods Receipt
An inspection lot is created only when QM is active for the plant, the material has an active inspection type for the goods movement, and the material carries a QM control key. Check the Quality Management view in MM02, confirm inspection type 01 (purchase order) or 04 (production order) is active, then check QM activation in the plant and the goods movement used.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
How-toSAP SE16N vs SQVI: Table Browser vs Ad Hoc Query
SE16N is a single-table browser: fast filtering, formatted display, and export from one table at a time, with an optional edit function for authorized users. SQVI (Quick Viewer) builds ad hoc queries that join multiple tables without writing ABAP, and can be saved as a reusable report. Use SE16N for a quick look at one table; use SQVI when you need data joined across two or more tables.
Error fixSAP CO11N Confirmation Errors and How to Fix Them
CO11N (time ticket confirmation for production/process orders) throws several distinct errors: deviation from the standard value is too large, goods movement not possible for a component, or the order/operation status does not allow confirmation. Each has a specific cause in order status, routing tolerance settings, or component availability, not a single generic fix.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
Error fixSAP Short Dump TIME_OUT: Maximum Runtime Exceeded
A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.
AI for ERPAI for SAP Quality Management: Notifications, 8D, and CAPA Without the Manual Drafting
AI grounded on SAP QM data that triages notifications, drafts 8D and CAPA reports, and summarizes inspection trends, deployed on-prem for full traceability.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
Stuck on SAP ECC and S/4HANA?
Talk to engineers who work inside SAP ECC and S/4HANA every week, and who build private AI that answers these questions from your own ERP data.