SAP QM Valuation Mode and Valuation Rule: Where Set and How They Decide
sap qm valuation mode
Also searched as
- sap qm valuation rule tcode
- sap qm valuation of characteristic accept reject
- sap qm valuation mode attribute variable
- sap qm automatic usage decision valuation
Short answer
In SAP QM the valuation mode decides how a characteristic is judged accepted or rejected from the recorded results, and it is referenced from the sampling procedure and the inspection characteristic. The valuation rule decides how characteristic valuations roll up into the inspection lot valuation that supports the usage decision.
Applies to: SAP ECC 6.0 and S/4HANA QM; configuration node names vary slightly by release
How to review and set valuation behaviour
- 1Open the sampling procedure with QDV3 (display) or QDV2 (change) and read the Valuation Mode field. It controls how results from the sample are valued.
- 2Open the master inspection characteristic (QS23 display, QS22 change) and check whether it is attribute or quantitative, and what control indicators are set.
- 3Check the inspection plan operation in QP03 to see which characteristics and sampling procedure each operation uses.
- 4Use SPRO and search for valuation modes under Quality Management, Quality Inspection, to see how modes are defined and what accept and reject logic they carry.
- 5Check the inspection lot valuation settings, including the valuation rule if you use one, under the same Quality Inspection configuration.
- 6Record test results in QE51N on a sample lot and confirm the characteristic valuations and the lot valuation come out as designed before the usage decision in QA11.
What a valuation mode decides
A valuation mode defines how a characteristic result becomes accepted or rejected. For attribute characteristics the typical logic is based on the number of nonconforming units or defects against the accept and reject numbers of the sampling plan. For quantitative characteristics the result is compared to the tolerance limits.
The sampling procedure ties this together: it states the sample size rule, the valuation mode and, for statistical plans, the accept and reject criteria. Because of this, the same characteristic can behave differently under two sampling procedures.
Manual valuation is also possible, where the inspector sets accepted or rejected directly and the system does not calculate it.
From characteristic result to usage decision
Each characteristic result is stored with a valuation. In table QAMV the field MBEWERTG holds it, A for accepted and R for rejected. A rejected mandatory characteristic can make the whole operation and the inspection lot rejected.
The inspection lot then gets a valuation from the valuation rule and the selected set logic. The usage decision in QA11 can be proposed from that, and with a quality score procedure the lot can be given a score as well.
Automatic usage decision uses these valuations: if all characteristics are accepted, the system can set the decision code without a person. This needs the right control in the inspection type and master data.
Common configuration mistakes
A characteristic marked as not requiring results never produces a valuation, so the lot can be accepted with data missing. Mandatory settings should reflect the quality plan.
Dynamic modification rules (QDR1) change inspection stage and sample size based on history, but do not change the valuation mode. Do not confuse them with valuation rules.
If rejection behaviour seems wrong, trace the one characteristic in QAMV before changing configuration. The cause is usually a sampling procedure or tolerance, not the mode.
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
- !There is no single transaction for valuation rules that holds across releases. Use the SPRO search under Quality Inspection for your release.
- !Changing a sampling procedure affects all plans that use it. Check where-used first.
- !Existing inspection lots keep the valuation logic they were created with.
- !Manual valuation hides statistical rejection. Use it only where the plan intends it.
- !Mandatory characteristics left empty can block the usage decision or, if not mandatory, silently accept.
How an ERP-grounded AI assistant handles this
A grounded assistant can read the inspection plan, the sampling procedure and the results, and explain why a particular lot was rejected: which characteristic, which rule and which result. That is useful for QA engineers who inherit a plan. It stays read-only, and the quality records stay inside your own network when deployed on-prem.
Frequently asked questions
What is a valuation mode in SAP QM?
It defines how the results of a characteristic are judged as accepted or rejected, for example by accept and reject numbers for attributes or by tolerance limits for measured values.
Where is the valuation mode assigned?
It is a field of the sampling procedure, maintained with QDV2, and the procedure is used by the inspection plan and the master inspection characteristic setup.
What is the difference between valuation mode and valuation rule?
The mode values one characteristic from its results. The rule values the operation or inspection lot from the characteristic valuations. They work at different levels.
How do I see why a characteristic was rejected?
Open the results in QE51N or QE03 and check the characteristic valuation. In the database, table QAMV field MBEWERTG holds the accepted or rejected status.
Related
How to Create a Sampling Procedure in SAP QM
In SAP QM, a sampling procedure decides how many units to inspect and how to accept or reject the lot. Maintain it in QDV3, choose a sample type (fixed, percentage, sampling scheme or 100 percent) and a valuation mode, and where needed build the scheme in QDP1. Then assign the procedure to a master inspection characteristic or inspection plan.
How-toSAP QM Sample-Drawing Procedure: Setup and Use (QPV1)
A sample-drawing procedure defines how physical samples are taken for an inspection: how many, in which containers, and what they are used for. Create it with QPV1, then reference it from the inspection plan (or material and inspection setup), so that when a lot is created the system generates the physical sample records, which you can also create manually with QPR1.
How-toHow to Create a Selected Set in SAP QM (QS51)
A selected set is a subset of codes taken from one or more catalog code groups, so users only see the relevant choices. Create it with QS51 for a catalog type and plant, add the codes, save, and then assign it to a master inspection characteristic (QS21), the usage decision, or defect recording.
How-toHow to create an inspection plan in SAP QM (QP01)
Use QP01 to create the plan: enter the material and plant, fill the header (usage, status), add an operation with a work center, assign inspection characteristics, set the sampling procedure and save. The plan is only found at goods receipt when it is assigned to the material and the material has an active inspection type.
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.
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 ERP / S/4HANA?
Talk to engineers who work inside SAP ERP / 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 Sample Size Calculator by Lot Size and Sampling ProcedureCompare the sample size from an AQL table, a percentage rule and a fixed sample for any lot size, and estimate the inspection time.
- SAP QM Sampling Procedure Design TemplateFill in the key choices for a sampling procedure and produce a design document you can review with quality and the SAP team.
ERP fixes and how-tos
- How to Create a Sampling Procedure in SAP QMCreate a sampling procedure and sampling scheme in SAP QM: QDV3, QDP1, sample types, valuation modes and how to assign them to inspection plans.
- How to create an inspection plan in SAP QM (QP01)Create an inspection plan in SAP QM with QP01: header, operations, master inspection characteristics, sampling procedure and material assignment, plus a plan report.
- SAP QM inspection results report: which tcode shows whatFind inspection results in SAP QM: QA32 lot list, QE51N results worklist, QM12 and QGC2 evaluations, MIC history, and the QALS, QAMR and QAVE tables.