# How to Cancel or Reverse a Usage Decision in SAP ECC QM: Checklist > Source: https://netray.co/tools/sap-ecc-qm-usage-decision-reversal-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A controlled checklist for correcting a wrong usage decision on an SAP ECC inspection lot: assess what was posted, correct stock, change the decision and verify. ## Category sap ## Erp SAP ECC 6.0 ## Audience - SAP QM consultant - Quality engineer - SAP support analyst ## Tool **Kind:** checklist **Groups:** #### Assess **Items:** **Text:** Display the lot in QA03 and note the system status: UD made, ICCO, and SPCO if stock posting is complete **Critical:** true Open the Inspection lot stock tab to see quantities posted to unrestricted, blocked, scrap or other targets **Text:** List the material documents created by the UD (table QAMB links PRUEFLOS to MBLNR, MJAHR and ZEILE) **Critical:** true Check whether any of that stock has already been consumed, shipped or moved since the UD For batch-managed materials, check batch status and classification changes made by the UD Check follow-up actions and notifications triggered by the UD code Check the impact on quality score and vendor evaluation for the lot's vendor **Text:** Decide: is only the UD code wrong (no stock impact) or are stock postings wrong too? **Critical:** true #### Correct the decision without stock changes **Items:** Use QA12 (change usage decision with history) to change the UD code, so the original stays visible Avoid QA14 (change without history) for corrections that auditors need to trace Record the reason in the UD long text and in your quality record Check that QA12 does not repost stock already posted; quantities stay as originally posted #### Correct stock postings **Items:** **Text:** Get QM and inventory owners to agree the target stock type before any posting **Critical:** true Move stock back with counter-movements in MIGO (for example 322 unrestricted to quality, 349 blocked to quality, 554 reverse scrap from quality) where your configuration allows Expect a stock transfer inspection lot (inspection type 08, origin 08) if that type is active for the material **Text:** Do not reverse the original goods receipt to undo a UD; that also reverses the receipt, valuation and PO history **Critical:** true Check SAP Notes for your release on resetting a usage decision before using any reset method; apply only under the note's conditions Restrict any reset method by authorization and log who used it and why #### Re-decide and verify **Items:** Record the correct UD on the lot or on the new stock transfer lot **Text:** Check stock in MMBE per plant, storage location and batch **Critical:** true Check the lot status in QA03 and the stock tab totals Check batch status and classification after the new decision Inform purchasing, warehouse and quality of the correction and file the change record #### Cancelling an inspection lot instead **Items:** If no results and no UD exist yet, cancel the lot in QA02 so it gets status LTCA If results exist but no UD, review whether the lot should be completed or cancelled with your QM lead Once a UD with stock postings exists, the lot cannot simply be cancelled; follow the groups above **Scoring Note:** Standard SAP ECC has no one-click cancel for a usage decision. Critical items keep stock, valuation and the audit trail consistent while you correct it. ## Content **Intro:** This checklist helps a QM consultant or quality engineer correct a wrong usage decision on an SAP ECC 6.0 inspection lot in a controlled way. Standard ECC has no one-click cancel for a usage decision, so the work splits into assessing what was posted, correcting stock, changing the decision and verifying the result. **Sections:** #### What a usage decision changes **Body:** Recording a UD in QA11 sets the UD code and valuation on the lot, can trigger follow-up actions, updates the quality score and, for stock-relevant lots, posts the inspection lot stock from quality inspection to unrestricted, blocked, scrap or other targets. Those stock postings are normal material documents, linked to the lot through table QAMB. Changing the code in QA12 changes the decision record but does not undo the stock already posted. That is why a reversal is really two separate questions: is the decision wrong, and is the stock in the wrong place? **Bullets:** - QA11: record UD, QA12: change UD with history, QA13: display UD - QA14: change UD without history (avoid for audited corrections) - QA03: display lot status and stock #### How to use the checklist **Body:** Start with Assess and do not post anything until you know which material documents the UD created and whether that stock is still where it was posted. If only the code is wrong, QA12 is enough. If stock is wrong, agree the target stock type with inventory, use counter-movements in MIGO, and expect a stock transfer inspection lot if inspection type 08 is active. SAP has published notes describing controlled ways to reset a usage decision in specific situations; check the SAP Support Portal for your release and follow the note's conditions exactly, because a reset touches status and stock logic. #### Worked example **Body:** A lot of 500 bearings was accepted with UD code A and posted 500 to unrestricted with movement type 321. A day later the lab finds a hardness error. Assess shows 120 pieces already issued to production. The team blocks the remaining 380 by moving them from unrestricted back to quality with 322, which creates a stock transfer lot, then records a reject UD on that lot that posts them to blocked. The original lot keeps its history; QA12 adds a long text explaining the correction. The 120 issued pieces are handled through a quality notification on the production orders. #### Common mistakes **Body:** Reversing the goods receipt in MBST to undo a UD, which also unwinds valuation and the PO history and often creates a new lot when the receipt is reposted. Using QA14 so the original decision disappears from the history. Changing the code in QA12 and assuming stock moved with it. Posting counter-movements without checking that the stock was not consumed. Using a reset method from a note without restricting who can run it. **Cta:** If you want quality engineers to ask your ECC system about lot status, UD history and the related stock postings in plain English on your own servers, we can set that up. **Faq:** #### How do I cancel a usage decision in SAP QM? **Answer:** Standard SAP ECC has no direct cancel. Use QA12 to change the decision with history when only the code is wrong. If stock was posted, correct it with counter-movements in MIGO after checking the material documents in QA03 and QAMB. SAP notes describe controlled reset methods for specific cases; check them for your release. #### Does changing the UD in QA12 reverse the stock posting? **Answer:** No. QA12 changes the usage decision code and keeps the change history, but stock already posted from the inspection lot stays where it was. Any stock correction needs its own goods movements, agreed with inventory, and then a new decision on the resulting stock or lot. #### How do I cancel an inspection lot in SAP QM? **Answer:** If the lot has no results and no usage decision, open it in QA02 and cancel it, which sets status LTCA. Once results or a stock-posting UD exist, cancelling is no longer the right tool: complete the lot or correct the decision and stock as described in the checklist. #### Should I reverse the goods receipt to undo a usage decision? **Answer:** Usually not. Reversing the receipt also reverses valuation and purchase order history and may fail if lot stock was already posted. It is a different business event. Correct the stock type with transfer postings and keep the receipt intact, unless the receipt itself was wrong. ## Search terms how to cancel usage decision in sap qm, how to reverse usage decision in sap qm, how to cancel ud in sap qm, how to cancel the inspection lot in sap qm, change usage decision qa12, sap qm usage decision stock posting --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json