SAP Usage Decision Codes Worksheet
When a user records the usage decision for an inspection lot in QA11, SAP QM asks for a code, a valuation and a stock posting. Agree those codes once, in a worksheet, before you configure them.
| Code group | Code | Description | Valuation | Stock posting | Quality score | Lots per year (est.) | Weighted score | |
|---|---|---|---|---|---|---|---|---|
90000 | ||||||||
5600 | ||||||||
0 | ||||||||
0 | ||||||||
300 |
Example codes are illustrative design values, not SAP delivered content. Usage decision code groups, codes and the valuation of each code are maintained in the QM catalog and selected set configuration of your own system.
Want usage decision trends from your SAP data?
Ask us about a read only view of rejection and quality score trends over your QM tables.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add one row for each usage decision code you plan to offer. Give the code group, the code, a plain description, the valuation (accepted, accepted with deviation, rejected), where the stock goes and a quality score. Enter an estimate of lots per year to see the weighted score and the average score across lots. Export to Excel and use it as the workshop document with quality and warehouse teams.
What a usage decision does in SAP QM
The usage decision closes the inspection lot. It records the decision code, a valuation that tells SAP whether the lot passed, and the stock posting that moves the lot's stock out of quality inspection. It can also drive the quality score used in vendor evaluation, and trigger follow up such as quality notifications or batch status changes. Codes live in a catalog and are grouped in selected sets assigned to the plant.
- Valuation decides accepted or rejected for reporting
- Stock posting moves stock to unrestricted, blocked or scrap
- Quality score feeds quality level calculations and vendor evaluation
- Automatic usage decision can apply when all results are accepted
Design tips and common mistakes
Keep the list short. Too many codes make reporting noisy, and users pick the first one on the list. Separate the reason for rejection from the decision, since the reason belongs in defect codes. Make sure every rejected code has a clear stock posting so no lot stays in inspection stock. Review whether a score is needed for each code before you add it.
- Do not mix defect reasons and decision codes in one catalog
- Give every rejected code a physical stock posting
- Check authorizations so that not every user can use every code
- Test automatic usage decision with accepted and rejected sample lots
Frequently Asked Questions
Which transaction records the usage decision?
QA11 records a usage decision for an inspection lot. Related functions include QA12 to change and QA13 to display. The Fiori equivalents depend on your S/4HANA release.
What is the quality score used for?
The quality score is assigned to a usage decision code and feeds the quality score of the lot. It supports quality level calculation and vendor evaluation, so codes with similar outcomes should have consistent scores.
Can usage decisions be made automatically?
Yes. SAP QM supports automatic usage decision when all results are accepted and the inspection type allows it. Many companies still keep manual decisions for critical parts.
Are the example codes SAP standard?
No. They are illustrative design values for planning. Your delivered catalog and selected sets depend on your system and project, so confirm in customizing.
Netray can add an AI assistant over your QM data so quality teams ask about usage decisions and rejection trends in plain language. Read only and on-prem if needed.
Related Tools
SAP QM Inspection Types Reference
Look up the standard SAP QM inspection types, what business event triggers each one and what you must set up in the material master and inspection plan.
SAPSAP QM Quality Notification Types Reference
See what the standard SAP quality notification types Q1, Q2 and Q3 are for, and how related PM types differ.
SAPSAP QM Sampling Procedure Design Template
Fill in the key choices for a sampling procedure and produce a design document you can review with quality and the SAP team.
SAPSAP QM Dynamic Modification Rule Calculator
Model how much inspection effort a skip or reduced stage saves, based on the share of lots that run at the reduced stage.
More SAP tools
See all- SAP Master Inspection Characteristic Upload Worksheet
- SAP QM in Procurement Setup Checklist
- SAP QM Inspection Lot Origins Reference
- SAP PM Breakdown Notification Request Form Template
- SAP PM Measuring Point and Counter Readings Worksheet
- SAP PM Maintenance BOM and Spare Parts Cost Worksheet
- SAP PM Work Clearance and Work Permit Template
- SAP PM Spare Parts Kitting and Reservation Worksheet
- SAP PM Catalog and Code Group Design Worksheet