QPCT table — Catalog Code Text Table in Quality Management

One row in QPCT represents the short text for a single catalog code, in one language, at one point in the catalog hierarchy: catalog type, code group, code. The catalog hierarchy itself (which code groups and codes exist, and whether a code is blocked) lives in the code master table; QPCT contributes only the human-readable description attached to that code for a given language key. QM uses several catalog types for different purposes: defect type and defect location catalogs, cause catalogs, task catalogs, and usage decision code groups, among others. Every one of those catalog entries can carry a text row per active language. If a plant works in German and English, the same code number can have two QPCT rows, one per language, and either one can be missing without affecting the other.

Always restrict by client first, then by KATART, then CODEGRUPPE, and finally CODE if the investigation is about one specific code; without at least KATART the table returns text for every catalog in the system, mixing defect, cause, task and usage decision entries with no way to tell them apart quickly. Restricting by SPRACHE to the language actually being complained about is the second filter that matters, since a missing text in one language and a present text in another look identical unless the language field is checked explicitly. The table is not huge by transactional standards, but catalog data tends to accumulate unmaintained entries over years, so a KATART-only selection on an older system can still return an inconveniently long list.

Symptom: a defect code on a notification shows a code number but no description in the user's language. Select QPCT with MANDT = current client, KATART = the catalog type used for defects, CODEGRUPPE and CODE copied from the notification item, and SPRACHE = the user's logon language. No row returned confirms the text was never created for that language; a row with a blank KURZTEXT confirms the text exists but was saved empty; a row in a different SPRACHE than expected confirms a language mismatch rather than a missing text.

The QM catalog structure, including the code master and its associated text table, is part of the classic QM data model and continues to be used on S/4HANA without a structural redesign. Catalog maintenance is still done through the same style of transaction rather than through a new Fiori-first data model, and reporting on catalog codes generally still goes back to the underlying tables or their standard views rather than a dedicated compatibility view built specifically for this text table.

Catalog and code group content is functional QM master data, owned by whoever administers quality catalogs for the plant or company, typically the QM configuration lead rather than a basis or ABAP resource. A missing text is a master data gap to be closed in the catalog maintenance transaction; a systemic pattern of missing texts across many codes points to an incomplete catalog rollout during implementation, which is a project scope question, not a table-level defect.

QPCD holds the code master row that QPCT describes; QPGR holds the catalog group definition that groups of codes belong to. Notification tables QMFE, QMUR and QMMA store the KATART, CODEGRUPPE and CODE combination chosen by a user for defects, causes and tasks, and those values resolve into readable text only through QPCT. Catalog codes are maintained through the standard QM code group and catalog maintenance transactions, not by editing these tables directly.