Results for “okc_article_trans”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKC_ARTICLE_TRANS table resides in the OKC schema and belongs to the Oracle Contracts Core (OKC) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It records the relationship between a contract Article — a reusable clause or boilerplate provision — and the Rules or Lines that were generated from, or associated with, that Article. In effect, it is an intersection entity that materializes the many-to-many links between authored article content and the executable contract structures produced from it.

Under Data Vault modeling heuristics mined from its foreign key structure, this table is best classified as a link table. It does not hold descriptive attributes about a single business entity; rather, it captures associations between multiple hubs (articles, lines, and rules). Practitioners designing downstream analytical models should treat OKC_ARTICLE_TRANS as a relationship/link object rather than a reference or transaction hub.

Key Information Stored

The table contains 12 documented columns. The most significant are summarized below.

• ID — the surrogate primary key, enforced by the constraint OKC_ARTICLE_TRANS_PK and the unique index OKC_ARTICLE_TRANS_U1. This is the recommended join key for any application or reporting query.
• CAT_ID — the article identifier, referencing OKC_K_ARTICLES_B. It identifies the source article from which rules or lines were derived.
• CLE_ID — the contract line identifier, referencing OKC_K_LINES_B. It identifies the line to which the article relationship applies.
• RUL_ID — the rule identifier, referencing OKC_RULES_B. It identifies the rule generated from or attached to the article.
• DNZ_CHR_ID — the associated contract/charter identifier, tying the relationship to the parent contract record.
• OBJECT_VERSION_NUMBER — supports optimistic locking and concurrency control in the Oracle Applications Framework (OAF) layer.
• SECURITY_GROUP_ID — the multi-tenant security partition key, referencing FND_SECURITY_GROUPS; used to isolate data across security groups.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing record creation and last modification metadata.

Beyond the primary key, two business-key candidate unique indexes are documented: OKC_ARTICLE_TRANS_U2 on (CAT_ID, CLE_ID) and OKC_ARTICLE_TRANS_U3 on (CAT_ID, RUL_ID). These enforce that a given article may link to a particular line only once and to a particular rule only once.

Common Use Cases and Queries

Typical scenarios include tracing which contract lines were influenced by a standard clause, auditing rule propagation from articles, and reporting article usage across contracts.

To retrieve all lines generated from a specific article:

• SELECT cle_id FROM okc_article_trans WHERE cat_id = :article_id;

To join article, line, and rule detail for a contract:

• SELECT t.id, t.cat_id, t.cle_id, t.rul_id, b.title
• FROM okc_article_trans t, okc_k_articles_b b
• WHERE t.cat_id = b.id AND t.dnz_chr_id = :contract_id;

Common reporting uses include clause-usage frequency reports, contract clause-library audits, and analysis of which rules are derived from boilerplate articles. Always filter by SECURITY_GROUP_ID where multi-org access is enforced.

Related Objects

The following objects are directly related through the documented foreign key and primary key structures:

• OKC_K_ARTICLES_B — joined via OKC_ARTICLE_TRANS.CAT_ID = OKC_K_ARTICLES_B.ID.
• OKC_K_LINES_B — joined via OKC_ARTICLE_TRANS.CLE_ID = OKC_K_LINES_B.ID.
• OKC_RULES_B — joined via OKC_ARTICLE_TRANS.RUL_ID = OKC_RULES_B.ID.
• FND_SECURITY_GROUPS — joined via OKC_ARTICLE_TRANS.SECURITY_GROUP_ID.
• OKC_ARTICLE_TRANS_PK / _U1 / _U2 / _U3 — the primary key constraint and unique indexes governing data integrity.

These relationships make OKC_ARTICLE_TRANS a focal point for queries that reconcile article content with the actionable contract constructs generated from it.