Search Results okc_k_articles




Overview
Explore in AI Chat

Overview

OKC_K_ARTICLES_B is the base table that stores the application of standard clauses and non-standard, custom (one-time-use) clauses to business documents within the Oracle Contracts (OKC) module of Oracle E-Business Suite. Each row represents a single "article" instance — that is, a specific clause attached either to a document header or to an individual line. When an article is associated with a document header, its clause governs the entire document; when associated with a line, the clause governs only that line. This table therefore serves as the operational bridge between contract structures and the clause content they contain, and it is central to clause authoring, printing, amendment tracking, and versioning within the Contracts Core schema.

From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. This suggests it is best modeled as a satellite attached to a document or clause hub, carrying descriptive and versioned attributes rather than serving as an independent hub or a pure many-to-many link.

Key Information Stored

The table contains 56 documented columns. The most significant include:

Common Use Cases and Queries

A dominant use case is reporting the clauses applied to a given document. A typical query joins the article table to OKC_SECTIONS_B and OKC_BUS_DOC_TYPES_B, filtering by DOCUMENT_ID to list sections, labels, and sequence:

SELECT a.ID, a.LABEL, a.DISPLAY_SEQUENCE, a.SCN_ID FROM OKC.OKC_K_ARTICLES_B a WHERE a.DOCUMENT_ID = :p_doc_id ORDER BY a.DISPLAY_SEQUENCE;

Analysts frequently track custom versus standard clauses using CAT_TYPE and SBT_CODE, assess amendment activity through AMENDMENT_OPERATION_CODE and LAST_AMENDMENT_DATE, and audit clause coverage by counting articles per document type. Integration teams use ORIG_SYSTEM_REFERENCE_CODE and ORIG_SYSTEM_REFERENCE_ID1/2 to reconcile contracts with external repositories, while security reporting filters on SECURITY_GROUP_ID. Historical or amended-content reconstruction relies on ARTICLE_VERSION_ID and ORIG_ARTICLE_ID alongside the transaction table OKC_ARTICLE_TRANS.

Related Objects

  • OKC_BUS_DOC_TYPES_B — joined on OKC_K_ARTICLES_B.DOCUMENT_TYPE.
  • OKC_SECTIONS_B — joined on OKC_K_ARTICLES_B.SCN_ID, providing the section containing each article.
  • FND_SECURITY_GROUPS — joined on OKC_K_ARTICLES_B.SECURITY_GROUP_ID for security and org access.
  • OKC_ARTICLE_TRANS — references OKC_K_ARTICLES_B.CAT_ID; holds article transaction/versioning history.
  • OKC_SECTION_CONTENTS — references OKC_K_ARTICLES_B.CAT_ID; links articles into section content structures.
  • OKC_K_ARTICLES_B — self-referencing via CAT_ID for article-to-article relationships.
  • OKC_K_LINES_B and OKC_K_HEADERS_B — the document structures that own and contextualize articles through DOCUMENT_ID and document header identifiers.