QS51 — Edit Selected Set
QS51 maintains selected sets of catalog codes used by Quality Management for controlled qualitative results, valuations, or usage-decision choices. Use it when the business needs a defined subset of codes from a catalog for a specific plant or application context. Changes should preserve code semantics and validity because existing inspection processes may depend on the selected set.
Verified practitioner reference for QS51 — Edit Selected Set. 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· 551 words
Esta página aún no está disponible en español.
Purpose
maintain selected sets of catalog codes used for qualitative results, valuations and usage-decision choices. 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
QS51 is typically used when QM configuration/master data needs a controlled subset of catalog codes for inspection or decision processing. 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
- Confirm the catalog type and business use of the selected set.
- Open the selected set and review existing codes and valuations.
- Add or remove only approved catalog codes.
- Check plant/application relevance.
- Test results recording or usage decision with the updated set.
Key data objects
These are the fields and objects most useful for explaining a QS51 result. Record them in incident evidence and test scripts.
- catalog type — verify the exact value, validity/status, and relationship to this transaction's business object.
- selected set — verify the exact value, validity/status, and relationship to this transaction's business object.
- code group/code — verify the exact value, validity/status, and relationship to this transaction's business object.
- plant — verify the exact value, validity/status, and relationship to this transaction's business object.
- valuation/status — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove a QS51 change by recording catalog type, selected-set identifier, plant or application context, and the included codes with valuations before and after maintenance. Then execute a representative results-recording or usage-decision scenario to confirm the correct code list appears. If a code is missing, distinguish selected-set membership from the underlying catalog/code-group definition.
ECC vs S/4HANA
SAP Help references QS51 for editing selected sets used by inspection and usage-decision processes. 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
- Editing the wrong catalog type. Confirm the exact status and process ownership before applying a correction.
- Removing a code already used by active processes without impact analysis. Confirm the exact status and process ownership before applying a correction.
- Confusing a selected set with the underlying code group/catalog maintenance. 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/qs51ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.