JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

June 26, 2026 · 11 min read

SAP QM Catalog

The Catalog is the first master data object configured in SAP Quality Management — a structured code library that defines every classification code used during inspection processing, defect recording, and quality notification handling. It organizes codes into typed catalogs (usage decision, defect, cause, action), each further subdivided into code groups and individual codes. Without a Catalog in place, Master Inspection Characteristics cannot be fully defined, inspection results cannot be classified, and notifications lack the structured coding that drives reporting and root-cause analysis.

Part 1: Catalog — Core Concepts (All Modules)#

1.1 What Is the Catalog?#

A Catalog is a structured master data table of classification codes used in SAP QM to standardize how inspection outcomes, defects, their causes, and corrective actions are recorded and reported. Rather than allowing free-text entries that are impossible to aggregate, the Catalog imposes a controlled vocabulary that enables consistent quality reporting across plants, materials, and vendors.

1.2 Catalog Types#

Each catalog record carries a fixed type that determines its purpose in the QM process. Using the wrong type — or creating all codes in a single catch-all catalog — makes result analysis and notification reporting unreliable.

Design principle: Define all four catalog types during blueprint, even if some appear optional. Type 3 (Defect) and Type 5 (Cause) are mandatory for effective quality notification reporting; Type 9 (Action) is required for closed-loop CAPA tracking. Retrofitting catalog codes after go-live risks inconsistent historical data.

1.3 Organizational Levels and Data Hierarchy#

The Catalog hierarchy is entirely client-level: a Catalog Type contains Code Groups, and each Code Group contains individual Codes. None of these three levels carry a mandatory plant assignment — the same defect codes are available across every plant in the client by default.

Plant-level filtering is introduced one layer up, through the Selected Set. A Selected Set does not sit inside the Catalog hierarchy itself; it is a separate, plant-specific object that references one or more Code Groups, narrowing which codes an inspector sees at a given plant or operation.

Data hierarchy with a concrete example

Client 100
   │
   └── Catalog (Type 3 — Defect)
          │
          ├── Code Group "DEFECT-SURF"
          ├── Code Group "DEFECT-DIM"     Dimensional Defects
          │      │
          │      ├── Code 01   Dim OOT (Dimension Out of Tolerance)
          │      ├── Code 02   Wrong Ø
          │      └── Code 03   Warpage
          └── Code Group "DEFECT-FUNC"

Plant 1000
   │
   └── Selected Set "SS-PRESS-01"   Press Line Defects
          ── references ──> Code Group "DEFECT-DIM"
          ── references ──> Code Group "DEFECT-SURF"

A single Selected Set commonly references multiple Code Groups — as shown above, “SS-PRESS-01” pulls in both dimensional and surface defect codes so a press-line inspector sees one combined, relevant list instead of switching between catalogs.

Design principle: Keep Code Groups client-level and shared wherever the defect vocabulary is genuinely common across plants. Use plant-level Selected Sets — not plant-restricted Code Groups — as the primary mechanism for tailoring which codes an inspector sees. This keeps the master code library centrally maintained while still giving each plant a filtered, operation-relevant view.

1.4 Integration with Other Master Data Objects#

The Catalog is the lowest-level dependency in the QM master data chain. It must exist before any object that references classification codes can be created.

Part 2: QM-Specific Field Details#

2.0 Scope of QM Ownership#

Legend: ◎ = Owner / Critical, ○ = Direct involvement

2.1 Catalog Header#

The Catalog header establishes the type and scope of the code library. It is configured once during the initial QM system setup and rarely changes after go-live.

2.2 Code Groups#

Code Groups are the mid-level organizational unit within a Catalog. They group related codes under a shared label, enabling faster code selection and more meaningful sub-category reporting.

2.3 Codes#

Codes are the leaf-level entries in the catalog hierarchy — the actual values that inspectors and quality engineers select when recording results, defects, causes, or actions. Code design has the greatest impact on reporting quality.

2.4 Selected Sets#

A Selected Set is a named, plant-level subset of Code Groups from a given Catalog Type. It is the mechanism by which Inspection Plans restrict which codes are available to inspectors during results recording — preventing irrelevant options and reducing selection errors.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction