QPCD table — QPCD Table - QM Catalog Codes

One row in QPCD represents a single code defined within a code group of a QM catalog - for example a specific defect type code inside the code group used for surface defects, or a specific usage decision code inside the code group used for lot disposition. The row is identified by catalog type, code group and the code itself, and it carries administrative and status information for that code, such as who created or last changed it and whether it is locked or flagged for deletion. QPCD does not carry the human-readable description of the code - that lives in QPCT - so QPCD alone tells a consultant that a code exists and is usable, not what it means to a user reading a notification screen.

Always restrict by client and, immediately after that, by catalog type before touching code group or code - catalog type is the field that actually narrows the table, since the same code group number can exist independently under different catalog types with completely different meanings. Never scan QPCD by code alone across catalog types; a defect code '10' and a cause code '10' are unrelated rows that happen to share a code value. Because this is a configuration table maintained by a handful of quality engineers, it is small compared to the transaction tables that reference it, so a full unrestricted read is usually harmless, but it is still worth filtering by catalog type and code group to keep the result readable when checking a specific code.

Symptom: a user reports that a defect code they expect to see on a quality notification is missing from the dropdown. Select QPCD where KATART equals the defect type catalog, CODEGRUPPE equals the relevant code group, and CODE equals the missing code. If no row comes back, the code was never created or was deleted at that catalog level. If a row exists but the code still does not appear on screen, check QASE for the same catalog type and code group - the code exists in the catalog but has been excluded from the selected set assigned to that notification type or inspection characteristic.

QPCD carries forward into S/4HANA unchanged as part of the classic QM catalog structure; the catalog, code group and code model was not touched by the broader S/4HANA data model simplification that affected other quality tables. Catalog maintenance in S/4HANA still uses the same underlying tables and the same catalog-type-based logic, and no CDS compatibility view is required to read it in the way older transactional tables sometimes need. Consultants moving from ECC will find QPCD behaves identically.

The QM functional consultant or quality engineer responsible for catalog configuration owns changes to QPCD, since codes are created and maintained through catalog maintenance transactions rather than direct table edits. A data question about why a specific code is missing or locked belongs first with whoever maintains the relevant catalog type, not with basis or an ABAP developer.

QPGR holds the code group header that QPCD rows belong to, and QPCT carries the language-dependent text for each code. QASE defines the selected set that filters which QPCD codes are actually offered on a given inspection characteristic or notification field. QMFE, QMUR and QMMA record the defect, cause and task codes actually used on quality notifications, referencing catalog type, code group and code back into QPCD. Catalog maintenance is done through the QM catalog maintenance transactions (commonly referenced as QS41 through QS49, one per catalog type), not by editing QPCD directly.