Search Results okc_qa_errors_t

Overview

OKC_QA_ERRORS_T is a temporary table in the OKC (Contracts Core) schema of Oracle E-Business Suite. It serves as the transient staging repository for errors and warnings produced by the Quality Assurance (QA) validation engine during contract authoring and processing. When a contract, article, or deliverable is validated — whether through the Contracts Authoring workbench, a concurrent QA check program, or an API-driven validation call — the QA engine writes one row per detected problem into OKC_QA_ERRORS_T. Downstream UI components and reporting layers then read this table to present the user with a consolidated list of violations, their severity, and corrective suggestions.

Because the table is populated and consumed within the scope of a single validation session, its contents are ephemeral. Implementations typically treat it as a working scratchpad rather than a persistent audit store; rows are cleared between runs or scoped by DOCUMENT_TYPE and DOCUMENT_ID. The ETRM metadata classifies the object heuristically as standalone from a Data Vault perspective, meaning it does not function as a conformed hub, link, or satellite in a warehouse sense. In practice this is best modeled as a transient error-log or staging satellite whose grain is one QA finding per document per sequence position, rather than as a durable dimension or fact.

Key Information Stored

The table contains 24 documented columns. The most functionally significant are:

• DOCUMENT_TYPE / DOCUMENT_ID — Identify the parent contract or business document being validated. Together they form the primary business-key candidate for scoping a given QA run.
• SEQUENCE_ID — Ordinal position of the finding within the run, providing a stable ordering for display.
• ERROR_RECORD_TYPE and ERROR_RECORD_TYPE_NAME — Code and decoded description classifying the row (for example, error versus warning versus informational note).
• ERROR_SEVERITY and ERROR_SEVERITY_NAME — Numeric severity and its display label, used to drive highlighting and gating logic.
• QA_CODE and RULE_ID — The identifier of the QA rule or check that generated the finding, enabling traceability to the rule registry.
• MESSAGE_NAME — The message token resolved against the message dictionary for localization.
• PROBLEM_SHORT_DESC, PROBLEM_DETAILS, and PROBLEM_DETAILS_SHORT — Human-readable problem text at varying levels of verbosity.
• SUGGESTION — Recommended remediation guidance shown to the user.
• ARTICLE_ID — Foreign key to OKC_ARTICLES_ALL, linking a finding to a specific contract article when the problem is article-scoped.
• DELIVERABLE_ID and SECTION_NAME — Further contextual anchors identifying the deliverable or section where the problem occurred.
• TITLE — Descriptive title for the finding row.
• CREATION_DATE — Timestamp of insertion, useful for aging transient rows.
• REFERENCE_COLUMN1 through REFERENCE_COLUMN5 — Generic overflow slots used by individual rules to carry rule-specific context.

Common Use Cases and Queries

Typical scenarios include surfacing outstanding validation problems before contract submission, reporting on rule-violation frequency for governance, and debugging QA rule behavior during configuration. A common query pattern retrieves all findings for a document, ordered by severity and sequence:

• SELECT sequence_id, error_severity_name, problem_short_desc, suggestion FROM okc_qa_errors_t WHERE document_type = :p_type AND document_id = :p_id ORDER BY error_severity DESC, sequence_id;
• Joining to OKC_ARTICLES_ALL on article_id to resolve article names for article-level findings.
• Aggregating by qa_code or rule_id to identify the most frequently triggered checks across a population of contracts.
• Filtering on error_severity to separate blocking errors from advisory warnings for gating logic in custom extensions.

Related Objects

• OKC_ARTICLES_ALL — Joined on OKC_QA_ERRORS_T.ARTICLE_ID = OKC_ARTICLES_ALL.ARTICLE_ID; the sole documented foreign key.
• OKC_QA_RULES / QA rule registry — Referenced via RULE_ID and QA_CODE to resolve the originating validation rule.
• OKC_CONTRACTS_ALL — Parent document context referenced through DOCUMENT_ID when the document type denotes a contract.
• OKC_DELIVERABLES — Resolves DELIVERABLE_ID context for deliverable-scoped findings.
• OKC_QA_UTIL / QA validation APIs — PL/SQL packages that populate and consume this temporary table during validation runs.
• FND Messages — Supplies localized text for MESSAGE_NAME.