Search Results okc_k_articles_bh_pk

Overview

OKC_K_ARTICLES_BH is the history (audit) table that shadows OKC_K_ARTICLES_B in the Oracle Contracts Core (OKC) module. In Oracle E-Business Suite 12.1.1 and 12.2.2, contracting documents such as service agreements, warranties, and subscription terms are decomposed into discrete articles. Each change to the base article definition is preserved here as a versioned record, allowing the full amendment trail of a contract clause to be reconstructed.

Consistent with Oracle's multi-version history pattern, the table is keyed on the combination of the article identifier (ID) and MAJOR_VERSION; the base table holds the current row while this history table accumulates prior and superseded versions. The metadata's heuristic Data Vault classification places this object as a satellite, since it stores descriptive, time-versioned attributes describing the article rather than defining the relationships between business entities.

Because OKC underpins Oracle Service Contracts and Oracle Procurement Contracts, this table is central to amendment auditing, clause lineage reporting, and regulatory traceability of contract language.

Key Information Stored

OKC_K_ARTICLES_BH contains 57 documented columns. The most operationally significant are:

• ID and MAJOR_VERSION — the composite primary key (OKC_K_ARTICLES_BH_PK), also defined by unique index OKC_K_ARTICLES_BH_U1. ID is the surrogate identifier of the article; MAJOR_VERSION distinguishes successive historical snapshots.
• CHR_ID and CLE_ID — the parent contract and line context to which the article belongs.
• DNZ_CHR_ID — the associated document/contract identifier used in the OKC data model.
• CAT_ID — foreign key to BEN_TCS_CAT, identifying the article's category within the contracts taxonomy.
• CAT_TYPE and SBT_CODE — category type and subtype classification of the article.
• LABEL and DISPLAY_SEQUENCE — the user-visible article heading and its ordering on the contract document.
• OBJECT_VERSION_NUMBER — optimistic locking token carried from the base table.
• MANDATORY_YN, FULLTEXT_YN, PRINT_TEXT_YN, CHANGE_NONSTD_YN, and MANDATORY_RWA — behavioral flags governing whether the clause is required, whether full text is stored, and whether printing is suppressed.
• AMENDMENT_OPERATION_CODE and SUMMARY_AMEND_OPERATION_CODE — the operation (add, update, delete) applied during the amendment that created this historical row.
• MANDATORY_YN, LAST_AMENDED_BY, and LAST_AMENDMENT_DATE — audit attribution for the amendment.
• REF_ARTICLE_ID, REF_ARTICLE_VERSION_ID, and ORIG_ARTICLE_ID — lineage pointers to referenced or originating articles.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS enabling multi-tenant or operating-unit data isolation.
• The WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE1–ATTRIBUTE15 DFF columns support standard EBS auditing and extensibility.

Common Use Cases and Queries

The primary use case is reconstructing the amendment history of a specific contract article. A typical query joins history to the base table on ID to compare current versus prior versions:

• Article version audit — select all MAJOR_VERSION rows for a given ID, ordered by version, to trace how clause text or category changed over time.
• Amendment attribution reporting — group by LAST_AMENDED_BY and LAST_AMENDMENT_DATE to identify who changed clauses and when.
• Contract composition reporting — join CHR_ID to the contract header to list all articles and their historical states.
• Category analysis — join CAT_ID to BEN_TCS_CAT to report article distribution by type.
• Mandatory clause compliance — filter MANDATORY_YN = 'Y' to confirm required clauses survived amendment.

Because the table stores history, queries should always restrict by MAJOR_VERSION and often correlate with OKC_K_ARTICLES_B via ID to detect superseded rows.

Related Objects

• OKC_K_ARTICLES_B — the base table; joined on ID (and MAJOR_VERSION for version-aware queries).
• BEN_TCS_CAT — referenced by CAT_ID for article category definitions.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for access control.
• OKC_K_HEADERS_B / OKC_K_LINES_B — parent contract header and line tables linked via CHR_ID and CLE_ID.
• OKC_K_ARTICLES_TL — translation table for article labels.
• OKC_ARTICLE_API / OKC_CONTRACT_API — PL/SQL APIs that write article changes and trigger history capture.
• OKC_K_ARTICLE_VERSIONS — where present, supports version tracking of article content.