Results for “okc_article_trans_u1”

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

Overview

OKC.OKC_ARTICLE_TRANS is a transactional association table within the Oracle E-Business Suite Contracts (OKC) schema. It records the translation of free-format Article text, held in OKC_K_ARTICLES_B, into either structured contract Rules (OKC_RULES_B) or Contract Lines (OKC_K_LINES_B, typically deliverables). An article is authored as unstructured narrative; this table captures the derived, structured representation so that contract terms entered as prose can be enforced or reported as rule or line logic.

Because it resolves many-to-many style associations between articles, rules, and lines while carrying its own descriptive columns and standard Who audit attributes, the ETRM metadata classifies this object heuristically as a link table in a Data Vault model. Under that modeling suggestion, ID serves as the link surrogate, and the CAT_ID/RUL_ID/CLE_ID combinations function as the connecting business keys, with DNZ_CHR_ID and the Who columns as descriptive payload.

Key Information Stored

The table persists 12 documented columns. The most operationally significant are:

• ID — Numeric primary key (OKC_ARTICLE_TRANS_PK), the surrogate identifier for each translation record.
• CAT_ID — Identifier of the article (OKC_K_ARTICLES_B) to which the record belongs.
• RUL_ID — Identifier of the rule (OKC_RULES_B) derived from the article.
• CLE_ID — Identifier of the contract line (OKC_K_LINES_B); populated only when the article is associated to a rule at the line level.
• DNZ_CHR_ID — Identifier of the contract owning the record; populated for all rows because an article may attach at header or line level.
• OBJECT_VERSION_NUMBER — Optimistic locking counter, set to 1 on insert and incremented on update, used by APIs.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who audit columns.
• SECURITY_GROUP_ID — Used in hosted environments and for row-level security partitioning.

Two business-key candidates are enforced by unique indexes: OKC_ARTICLE_TRANS_U2 (CAT_ID, CLE_ID) and OKC_ARTICLE_TRANS_U3 (CAT_ID, RUL_ID). These guarantee that a given article maps at most once to a given line and at most once to a given rule.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include tracing which rules were generated from a contract article, verifying that each article linked to a line has a corresponding rule, and auditing article-to-contract lineage. The indexed columns DNZ_CHR_ID and RUL_ID (via OKC_ARTICLE_TRANS_N1 and N2) support efficient filtering.

A representative query joining the principal parents:

SELECT t.ID, t.CAT_ID, t.RUL_ID, t.CLE_ID, t.DNZ_CHR_ID
FROM   OKC.OKC_ARTICLE_TRANS t
WHERE  t.DNZ_CHR_ID = :contract_id;

A lineage query against the article and rule tables:

SELECT a.ID article_id, r.ID rule_id, t.CLE_ID
FROM   OKC.OKC_ARTICLE_TRANS t,
       OKC.OKC_K_ARTICLES_B  a,
       OKC.OKC_RULES_B       r
WHERE  t.CAT_ID = a.ID
AND    t.RUL_ID = r.ID
AND    t.CAT_ID = :article_id;

Hosted deployments should additionally filter on SECURITY_GROUP_ID to honor row-level security.

Related Objects

• OKC.OKC_K_ARTICLES_B — Parent article definition; joined via OKC_ARTICLE_TRANS.CAT_ID.
• OKC.OKC_RULES_B — Structured rule derived from the article; joined via RUL_ID. Indexed by OKC_ARTICLE_TRANS_N2.
• OKC.OKC_K_LINES_B — Contract line or deliverable; joined via CLE_ID when line-level association exists.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID for hosted-environment security.
• OKC_K_HEADERS_B / OKC_K_HEADERS_ALL_B — Contract header implied by DNZ_CHR_ID, anchoring the transaction to a contract.
• OKC Contract APIs — Article, rule, and line APIs insert and update rows, relying on OBJECT_VERSION_NUMBER for concurrency control.