Search Results okc_doc_qa_lists_u1




Overview
Explore in AI Chat

Overview

OKC.OKC_DOC_QA_LISTS is a configuration (seed data) table in the Oracle E-Business Suite Contracts (OKC) schema that stores the list of quality assurance (QA) checks to be performed for a given business document type, along with the severity of each check. It acts as the setup repository that drives QA validation behavior during document authoring, approval, and generation flows within Oracle Contracts and related business document processes. The table resides in the APPS_TS_SEED tablespace, confirming its role as seeded, reference-style configuration rather than transactional data, and carries a VALID status in the ETRM documentation for both 12.1.1 and 12.2.2.

Because the table holds descriptive attributes about QA checks keyed to a parent business document type, its heuristic Data Vault classification is satellite-leaning. In a Data Vault model, it would logically attach as a satellite to a business-document-type hub (represented here by OKC_BUS_DOC_TYPES_B), holding the QA_CODE, severity, and enablement descriptors. The dependency metadata confirms it does not reference any other database object, and it is referenced only by the OKC_DOC_QA_LISTS# editioning view.

Key Information Stored

The table contains 11 documented columns. The most significant are:

  • QA_CODE (VARCHAR2, 30) — the code identifying the QA check; part of the composite primary key.
  • DOCUMENT_TYPE (VARCHAR2, 30) — the business document type the QA check applies to; the other half of the composite primary key and a foreign key to OKC_BUS_DOC_TYPES_B.
  • SEVERITY_FLAG (VARCHAR2) — indicates the severity level of the QA check.
  • ENABLE_QA_YN (VARCHAR2) — flag indicating whether the QA check is enabled or disabled.
  • OBJECT_VERSION_NUMBER (NUMBER) — sequential number set to 1 on insert and incremented on update, used by APIs for optimistic locking.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "Who" audit columns.
  • ZD_EDITION_NAME (VARCHAR2, 30) — the editioning column supporting Oracle EBS 12.2 online patching.

The surrogate primary key is OKC_DOC_QA_LISTS_PK (DOCUMENT_TYPE, QA_CODE). The unique index OKC_DOC_QA_LISTS_U1 (DOCUMENT_TYPE, QA_CODE, ZD_EDITION_NAME) represents the business-key candidate, extending the PK with the editioning column to remain unique across editions.

Common Use Cases and Queries

Typical use cases include auditing which QA checks are active for a document type, reviewing severity assignments, and troubleshooting why a QA check did not fire (often because ENABLE_QA_YN is set to N). Administrators frequently run queries to list all enabled checks for a given document type during setup validation.

Sample query listing enabled checks for a document type:

  • SELECT QA_CODE, SEVERITY_FLAG, ENABLE_QA_YN FROM OKC.OKC_DOC_QA_LISTS WHERE DOCUMENT_TYPE = :p_doc_type AND ENABLE_QA_YN = 'Y' ORDER BY QA_CODE;

A reporting query joining to the business document type to display the document type name alongside QA checks, and a diagnostic query identifying disabled checks, are also common. Because the table is seed data, direct DML is generally discouraged; changes should be applied through supported setup paths.

Related Objects

The most significant related objects, grounded in the documented relationship data, are:

  • OKC_BUS_DOC_TYPES_B — referenced via OKC_DOC_QA_LISTS.DOCUMENT_TYPE; the parent business document type definition.
  • OKC_DOC_QA_LISTS# — the editioning view that exposes OKC_DOC_QA_LISTS to the application in 12.2.x.
  • OKC_DOC_QA_LISTS_PK — the composite primary key (DOCUMENT_TYPE, QA_CODE).
  • OKC_DOC_QA_LISTS_U1 — the unique index (DOCUMENT_TYPE, QA_CODE, ZD_EDITION_NAME) and business-key candidate.

The metadata documents no further direct dependents, so additional integration points should be confirmed against the application API layer for the specific QA check being administered.