SAP transaction codeObjectQS23ModuleQM

QS23 — Change Master Inspection Characteristic

QS23 changes an existing Master Inspection Characteristic in SAP Quality Management. SAP's current S/4HANA documentation lists QS21 as Create, QS23 as Change, and QS24 as Display for MIC master data. Use QS23 to maintain permitted characteristic settings and versions; it is not a selected-set display transaction.

QS23 is the display transaction for a Selected Set in Quality Management catalog maintenance, the curated list of codes pulled from one or more code groups that gets attached to a characteristic or catalog profile so recording screens only offer a restricted code list. The page covers where selected sets sit relative to code groups and codes, what breaks when a code group changes underneath a set, and how to prove a display discrepancy in the underlying data.

Published 20 Sept 2026· 503 words

Esta página aún no está disponible en español.

Purpose

QS23 changes Master Inspection Characteristic master data. Depending on status, usage, and validity, it allows controlled maintenance of characteristic descriptions, control indicators, specifications, catalog assignments, inspection methods, and other MIC attributes. Because MICs can be reused across many inspection plans, a change can have wide downstream impact.

When it is used

Use QS23 when an approved quality-standard change requires an existing MIC to be corrected or updated. Before changing a characteristic already used in productive inspection plans, determine whether a new version/effective-dated change is more appropriate than altering existing semantics.

How to use it in practice

  • Enter the plant and MIC identifier/version.
  • Review current status, usage, and existing inspection-plan references before changing anything.
  • Change only attributes approved by the quality master-data process.
  • Use valid-from/version controls where the change must not alter historical inspection meaning.
  • Save, then regression-test a representative inspection plan/results-recording scenario.

Key data objects

The same MIC master-data elements created in QS21 are maintained here.

  • Plant, MIC and version/status.
  • Characteristic type and control indicators.
  • Unit, target values, limits, or qualitative valuation settings.
  • Catalog/selected-set and inspection-method assignments where applicable.
  • QPMK/QPMT — core MIC master/text tables identified by SAP for migration analysis.
  • Inspection-plan usage — understand where the MIC is referenced before changing shared semantics.

How to prove it in the data

Compare the MIC before and after the change using the standard display function and change history where available. Then identify inspection plans that reference the characteristic and execute a controlled inspection/results-recording test. This proves both that the master change was saved and that its operational effect is the intended one.

ECC vs S/4HANA

QS23 remains the SAP-documented Change transaction for Master Inspection Characteristics in current S/4HANA documentation. Fiori MIC apps may provide alternate maintenance/display surfaces, but QS23 should be understood as MIC maintenance—not QM selected-set display.

Common pitfalls and how to diagnose them

  • Changing a shared MIC without identifying all inspection plans that reuse it.
  • Editing a productive characteristic when a new version/effective date is required for traceability.
  • Confusing MIC maintenance with catalog or selected-set maintenance.
  • Changing valuation/control indicators and testing only master data rather than results-recording behavior.

Whose problem this is

QM owns MIC maintenance and governance. Quality engineering/laboratory owners define the specification, while QM functional consultants manage SAP behavior and impact analysis. ABAP is involved only for proven custom valuation or enhancement logic.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-tcodes/qs23ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.