Results for “okc_article_trans_h”

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

Overview

OKC_ARTICLE_TRANS_H is a history (audit) table in the Oracle Contracts Core (OKC) module, maintained in the OKC schema. Within Oracle EBS 12.1.1 and 12.2.2, it stores the historical versions of rows held in its transactional parent table, OKC_ARTICLE_TRANSLATIONS. Every time a translation record is inserted, modified, or superseded, the corresponding prior or current image is written to this history table, preserving a versioned trail of translated contract article text.

The table is documented as an Oracle E-Business Suite object with status VALID and is physically described in the ETRM 12.2.2 schema with 13 columns. Because it captures attribute-level state over time, a Data Vault modeling heuristic classifies OKC_ARTICLE_TRANS_H as a satellite: a descriptive, versioned structure keyed to a parent business key with a companion version attribute.

Key Information Stored

The history table is identified by the primary key constraint OKC_ARTICLE_TRANS_H_PK, which spans ID and MAJOR_VERSION. This composite key is also implemented as the unique index OKC_ARTICLE_TRANS_H_U1, making ID plus MAJOR_VERSION the business-key candidate for versioned retrieval. ID is the surrogate identifier inherited from the parent translation record, while MAJOR_VERSION distinguishes successive historical versions of that same record.

Business context is carried through several foreign key columns: CAT_ID references BEN_TCS_CAT and identifies the catalog (or contract terms catalog) to which the translation belongs; SECURITY_GROUP_ID references FND_SECURITY_GROUPS and supports Oracle EBS multi-org / security-group data restriction. RUL_ID and CLE_ID link the translation to the associated rule and clause definitions used in contract terms authoring, and DNZ_CHR_ID associates the row with the contract (denormalized contract header) context. Standard EBS WHO columns track the audit trail: CREATED_BY and CREATION_DATE capture the initial insert, while LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture the most recent change. OBJECT_VERSION_NUMBER supports optimistic concurrency control during DML.

Common Use Cases and Queries

Typical use cases include auditing historic translation changes, reconstructing a point-in-time view of translated article text, and diagnosing translation issues that arose during contract versioning. Reporting queries commonly join the history table to its parent and then join BEN_TCS_CAT via CAT_ID to resolve catalog context.

• Point-in-time lookup: query OKC_ARTICLE_TRANS_H for a given ID and the maximum MAJOR_VERSION at or below a target date, using LAST_UPDATE_DATE as the effective timestamp.
• Change audit: compare consecutive MAJOR_VERSION rows for the same ID to identify who changed a translation and when, using CREATED_BY / LAST_UPDATED_BY.
• Security-scoped reporting: filter rows by SECURITY_GROUP_ID to honor EBS security-group access restrictions.
• Orphan / integrity checks: join CAT_ID to BEN_TCS_CAT to detect translations lacking a valid catalog reference.

A representative pattern selects the latest historical version per ID by aggregating MAX(MAJOR_VERSION) in a subquery and joining back on the composite key (ID, MAJOR_VERSION).

Related Objects

• OKC_ARTICLE_TRANSLATIONS — the parent transactional table for which OKC_ARTICLE_TRANS_H stores historical rows.
• BEN_TCS_CAT — referenced by CAT_ID; supplies catalog context for translated terms.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; governs data security grouping.
• OKC_ARTICLE_TRANS_H_U1 — the unique index enforcing the ID / MAJOR_VERSION business key.
• OKC_ARTICLE_TRANS_H_PK — the primary key constraint on the same columns.
• Rule and clause definition tables associated through RUL_ID and CLE_ID, which link translations to contract terms authoring structures.
• Concurrent programs and contract authoring APIs that write to OKC_ARTICLE_TRANSLATIONS, thereby populating this history structure.