# SAP QM Valuation Mode and Valuation Rule: Where Set and How They Decide > Source: https://netray.co/erp-help/sap-qm-valuation-mode-and-valuation-rule-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System sap ## Erp SAP ERP / S/4HANA ## Module QM Inspection Planning / Results Recording ## Query sap qm valuation mode ## Alternate Queries - sap qm valuation rule tcode - sap qm valuation of characteristic accept reject - sap qm valuation mode attribute variable - sap qm automatic usage decision valuation ## Applies To SAP ECC 6.0 and S/4HANA QM; configuration node names vary slightly by release ## Steps ### How to review and set valuation behaviour **Items:** - Open the sampling procedure with QDV3 (display) or QDV2 (change) and read the Valuation Mode field. It controls how results from the sample are valued. - Open the master inspection characteristic (QS23 display, QS22 change) and check whether it is attribute or quantitative, and what control indicators are set. - Check the inspection plan operation in QP03 to see which characteristics and sampling procedure each operation uses. - Use 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. - Check the inspection lot valuation settings, including the valuation rule if you use one, under the same Quality Inspection configuration. - Record 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. ## Sections ### What a valuation mode decides **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### What is a valuation mode in SAP QM? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap qm valuation mode, sap qm valuation rule tcode, sap qm sampling procedure valuation, sap qm accept reject characteristic, sap QAMV MBEWERTG, sap qm usage decision valuation, QDV2 sampling procedure, sap qm inspection lot valuation --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json