QA10 — Collective Usage Decision
QA10 supports collective usage-decision processing for inspection lots. It is useful when Quality Management needs to process a controlled population rather than entering each decision individually. Before mass processing, verify that results are complete, lot statuses permit the decision, and the usage-decision codes or follow-up stock postings are appropriate for every selected lot.
Verified practitioner reference for QA10 — Collective Usage Decision. The page covers the operational purpose, correct usage sequence, key data to capture, evidence-based diagnosis, S/4HANA context, frequent mistakes, ownership and related SAP objects.
Published 20 Sept 2026· 563 words
Esta página ainda não está disponível em português.
Purpose
generate and process a collective list of inspection lots for which an automatic or collective usage decision is planned. The transaction should be understood as one point in the full operational process. Master data, status, validity dates and preceding execution steps often determine what can happen here, so preserve that context before changing the symptom.
When it is used
QA10 is typically used when quality teams need to work a population of inspection lots rather than entering usage decisions one lot at a time. It is also useful in project testing and support reproduction because it exposes a concrete process state. In production, keep the initial selection narrow and separate display/analysis from actions that mass-change, count, clear or post.
How to use it in practice
- Restrict the selection to the relevant plant, inspection type and date range.
- Review which lots are actually eligible for the collective/automatic decision.
- Open exceptions individually before processing a mass population.
- Execute according to the approved QM decision rules.
- Verify usage-decision status and any resulting stock posting.
Key data objects
These are the fields and objects most useful for explaining a QA10 result. Record them in incident evidence and test scripts.
- plant — verify the exact value, validity/status, and relationship to this transaction's business object.
- inspection type — verify the exact value, validity/status, and relationship to this transaction's business object.
- inspection lot — verify the exact value, validity/status, and relationship to this transaction's business object.
- status — verify the exact value, validity/status, and relationship to this transaction's business object.
- usage-decision eligibility — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove a QA10 result by preserving the selection and recording each representative inspection lot's status, recorded results, and proposed usage decision. After processing, verify the usage-decision code/status and any stock posting for the same lot. For partial failures, open the failed lot individually and identify the specific status or master-data prerequisite.
ECC vs S/4HANA
SAP Help identifies QA10 as the Collective Usage Decision transaction; it remains relevant in S/4HANA QM. Where a classic component is legacy, the page explicitly keeps that context so readers do not mistake technical availability for SAP's strategic architecture for new implementations.
Common pitfalls and how to diagnose them
- Applying a mass usage decision to lots whose results are incomplete. Confirm the exact status and process ownership before applying a correction.
- Assuming all selected lots have identical valuation rules. Confirm the exact status and process ownership before applying a correction.
- Ignoring stock-posting consequences of the usage decision. Confirm the exact status and process ownership before applying a correction.
Whose problem this is
Primary ownership is the QM team, with adjacent functional, technical, Security, or integration teams joining only where the evidence crosses component boundaries. Escalate with the exact object/document, organizational keys, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/qa10ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.