How to Reverse a Usage Decision in SAP QM
how to reverse usage decision in sap qm
Also searched as
- reset usage decision SAP QA12
- cancel usage decision QM
- change usage decision after stock posting
- undo UD inspection lot SAP
Short answer
Reverse a usage decision from QA12 (Change Usage Decision) by changing or resetting the decision on the inspection lot, which also reverses the automatic stock posting from inspection stock, provided nothing has used that stock or closed the lot. If the system refuses, post the stock back with a manual transfer posting and document the reason. The exact menu wording varies by release.
Applies to: SAP ECC 6.0 and S/4HANA on-premise QM. Behaviour depends on QM Customizing, such as lot stock posting and follow-up actions.
How to reverse a usage decision
- 1Display the lot in QA03 and check the status (UD set), the usage decision code and the stock posting made. Note the material, batch and quantity.
- 2Check whether the stock from the UD has moved. If the quantity was already issued, shipped or consumed, a simple reversal cannot put it back.
- 3Open QA12 for the lot. Look under the Usage decision or Edit menu for the function to change or reset the decision. The label differs by release, so confirm it in a test client.
- 4Change the code to the correct one, or reset it, and save. The system reverses the earlier stock posting and makes a new one according to the new code.
- 5Check the material document list (MB51 or the lot's document tab) to see the movements: for example movement types 321 and 322 between inspection stock and unrestricted stock.
- 6Review follow-up actions that were triggered by the old decision, such as notifications, certificate output and inspection type updates, and correct them.
- 7If QA12 will not allow it, correct the stock manually through a transfer posting in MIGO (for example 322 to return quantity to quality inspection) and record the reason on the lot.
- 8Record who approved the reversal. For regulated products this is an audit item.
What a usage decision does
The usage decision (UD) closes an inspection lot, assigns a quality score and a code (for example accepted, rejected, scrap), and usually triggers stock postings that move quantities out of quality inspection stock into unrestricted, blocked or scrap. UD data is stored in table QAVE for the lot.
Because the UD drives stock and often certificates, correcting it later is a controlled act, not an edit. That is why QM restricts changes once downstream processes depend on the result.
When a reversal is possible
The common blocking conditions are: the stock posted from the UD has already been consumed or moved, the lot has been deleted or archived, or a follow-up action cannot be undone automatically. Authorisation also matters: the user needs rights to change usage decisions for the inspection type and plant.
If the stock is still in the posted category, the reset normally works and the system creates the reversing material documents for you.
QA03 Display inspection lot (status, UD, stock posting) QA12 Change usage decision MB51 Material document list (movement types 321, 322, 343, 344, 349, 350) MIGO Manual transfer posting if QA12 is blocked
Manual fallback
Where the standard reset is blocked, a transfer posting in MIGO can move the quantity back to inspection stock or between stock types, using the movement types for the direction you need. This leaves the lot's UD as it is, so the lot data and stock may disagree. Document it and, if needed, raise a correction with the QM owner.
Do not edit the QM tables directly. The UD, stock posting and status are linked.
Prevent the need to reverse
Most reversals come from a rushed UD. Use the dynamic modification and automatic UD only where the results are trustworthy, and add a second approval for high-value or regulated lots. A short hold on certificate output until the UD is confirmed also saves cleanup.
Try it here, free
SAP QM Usage Decision Codes Worksheet
Plan usage decision code groups and codes, with valuation, stock posting and quality score, before you configure them in SAP QM.
Common pitfalls
- !Assuming a UD can always be undone. Stock already used stops a clean reversal.
- !Fixing only the stock and leaving the lot's UD wrong.
- !Forgetting notifications and certificates raised by the first decision.
- !Editing QM tables directly.
- !Not recording an approval for the reversal in a regulated environment.
How an ERP-grounded AI assistant handles this
An assistant grounded in SAP QM can check a lot's UD, the stock posting, whether the quantity has since moved and which follow-ups were created, then say whether a reversal is likely to succeed before a person tries it. Netray keeps that read-only and local on-prem; the reversal itself, being a quality record, stays a human action.
Frequently asked questions
Can I reverse a usage decision in SAP?
Often yes, from QA12, as long as the stock posted by the decision has not been used and the lot is not closed or archived. The system then reverses the earlier stock posting. If it refuses, a manual transfer posting is the fallback.
Which transaction changes a usage decision?
QA12 changes an existing usage decision and QA11 records the first one. QA03 displays the lot and its status. The exact option to reset or change the decision sits in the Usage decision or Edit menu, depending on release.
What happens to stock when a UD is reversed?
The system reverses the earlier movements from inspection stock and creates new ones for the new code. You can see them in the material document list, typically movement types such as 321 and 322 between quality inspection and unrestricted stock.
Why can't I change the usage decision?
Usual reasons are that the stock has already been consumed or moved, the user lacks authorisation, the lot status blocks changes, or follow-up actions cannot be undone. Check QA03 for the status and the document flow first.
Related
SAP QA11 Usage Decision: Make It and Post Stock Correctly
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.
Error fixSAP 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.
How-toInspection Results and Inspection Plan Reports in SAP QM
For inspection results in SAP QM, list lots in QA32, display results per lot in QE03, and analyse them over time with the QM evaluation transactions such as QGC1. For inspection plans, QP01 to QP03 maintain and display plans and QP19 gives the where-used list that ties plans to materials. The data sits in QALS, QAMV, QAMR, QAVE, PLKO and MAPL.
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.
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 / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP QM Usage Decision Codes WorksheetPlan usage decision code groups and codes, with valuation, stock posting and quality score, before you configure them in SAP QM.
- SAP QM Usage Decision BAPI SkeletonAn ABAP skeleton for recording an inspection lot usage decision through the standard BAPI, with error handling and a commit only when no error is returned.
ERP fixes and how-tos
- How to Reverse or Cancel a Usage Decision (UD) in SAP QMHow to reverse or cancel a usage decision (UD) in SAP QM: QA12 changes, what blocks it after stock posting, follow-up actions, authorizations and the safe fallback.
- How to Cancel a Usage Decision in SAP QMReverse or change a usage decision in SAP QM with QA12: prerequisites, effect on stock postings and the reasons the system blocks the change.
- SAP QA11 Usage Decision: Make It and Post Stock CorrectlyHow to make a usage decision in QA11, post stock to unrestricted, blocked or scrap, fix lots that will not close, and what QA12 can and cannot change.