Search Results okc_k_articles_b_u1

Overview

OKC.OKC_K_ARTICLES_B is the foundational table within the Oracle E-Business Suite Contracts (OKC) module that records the use of standard and non-standard (custom, one-time use) clauses in business documents. When a clause is associated with a document header, it governs the entire document; when associated with a line, it governs that line and all of its sublines. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is owned by the OKC schema. Its FND Design Data reference is OKC.OKC_K_ARTICLES_B, and its status is VALID across EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. This suggests that OKC_K_ARTICLES_B functions principally as a descriptive satellite attached to contract and article hubs, capturing attribute history and versioning rather than serving as a pure hub or link. The table contains 56 documented columns in the ETRM 12.2.2 physical schema.

Key Information Stored

The surrogate primary key is ID, defined by the unique index OKC_K_ARTICLES_B_U1 on APPS_TS_TX_IDX. This is the only documented uniqueness constraint and therefore the sole business-key candidate in the schema. Several columns carry the substantive meaning of each record:

• ID — Primary key column for the clause record.
• SAV_SAE_ID — Article ID; foreign key to OKC_ARTICLES_ALL.
• SAV_SAV_RELEASE — Version of the standard clause to which the contract is attached.
• CHR_ID — ID of the contract to which the clause is attached.
• CLE_ID — Contract line to which this clause belongs.
• CAT_ID — Self-referencing key linking clause records (FK to OKC_K_ARTICLES_B).
• SCN_ID — Foreign key to OKC_SECTIONS_B, indicating section placement.
• DNZ_CHR_ID — Document/contract identifier used by the N1 index.
• DOCUMENT_TYPE and DOCUMENT_ID — Polymorphic reference to the owning business document.
• ARTICLE_VERSION_ID and REF_ARTICLE_VERSION_ID — Version tracking for standard and referenced clauses.
• ORIG_SYSTEM_REFERENCE_CODE, ORIG_SYSTEM_REFERENCE_ID1, ORIG_SYSTEM_REFERENCE_ID2 — Cross-system lineage identifiers.
• MANDATORY_YN and MANDATORY_RWA — Flags indicating clause obligation.
• AMENDMENT_OPERATION_CODE and SUMMARY_AMEND_OPERATION_CODE — Amendment action descriptors.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS enforcing row-level access.

Columns SBT_CODE and CAT_TYPE are documented as obsolete as of 11.5.10, with SBT_CODE moved to OKC_ARTICLES_ALL.ARTICLE_TYPE.

Common Use Cases and Queries

Reporting on clause usage is the primary scenario. The following query retrieves all clauses attached to a contract header or its lines:

• SELECT a.ID, a.CHR_ID, a.CLE_ID, a.SAV_SAE_ID, a.MANDATORY_YN FROM OKC.OKC_K_ARTICLES_B a WHERE a.CHR_ID = :contract_id;
• SELECT a.ID, a.ARTICLE_VERSION_ID, a.REF_ARTICLE_ID FROM OKC.OKC_K_ARTICLES_B a WHERE a.DOCUMENT_TYPE = :dtype AND a.DOCUMENT_ID = :doc_id;
• Joining to OKC_ARTICLES_ALL via SAV_SAE_ID resolves the standard clause text for contract printing and audit extracts.
• Tracing amendments uses AMENDMENT_OPERATION_CODE alongside LAST_AMENDED_BY and LAST_AMENDMENT_DATE for a change history report.
• Detecting mandatory clauses leverages the MANDATORY_YN and MANDATORY_RWA flags in compliance reporting.

Related Objects

The following objects reference or are referenced by OKC_K_ARTICLES_B through documented foreign keys:

• OKC_ARTICLES_ALL — referenced via SAV_SAE_ID, holding the standard clause master.
• OKC_BUS_DOC_TYPES_B — referenced via DOCUMENT_TYPE.
• OKC_SECTIONS_B — referenced via SCN_ID, defining section membership.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
• OKC_ARTICLE_TRANS — references OKC_K_ARTICLES_B via CAT_ID.
• OKC_SECTION_CONTENTS — references OKC_K_ARTICLES_B via CAT_ID.
• OKC_K_ARTICLES_B (self) — the CAT_ID self-reference establishes clause hierarchies.