Search Results okc_k_articles_tlh_u1

Overview

The OKC.OKC_K_ARTICLES_TLH table is a Multi-Language Support (MLS) history table that stores translated and versioned article content within the Oracle Contracts (OKC) module of Oracle E-Business Suite. In the context of Oracle EBS 12.1.1 and 12.2.2, this object plays a supporting role in the Contracts Core architecture, where contract terms, clauses, and standard articles are maintained with full MLS and version-tracking semantics. The "_TLH" suffix identifies the table as a Translation, Language, and History table, meaning that each row represents a language-specific historical version of an article definition rather than the current operational record.

From a data modeling perspective, the heuristic Data Vault classification supplied in the metadata is standalone. This suggests the object is best modeled as an isolated satellite or reference structure, though because it carries language and major version components alongside a business identifier, it also exhibits characteristics of a multi-active satellite keyed on (ID, LANGUAGE, MAJOR_VERSION). No foreign-key dependencies to parent OKC tables are documented; the only recorded FK reference points outward to FND_SECURITY_GROUPS via SECURITY_GROUP_ID.

Key Information Stored

The table contains seventeen documented columns, of which the following are the most operationally significant:

• ID – Primary key column generated via the sys_guid() database function, serving as the surrogate identifier for each article record.
• LANGUAGE – Standard MLS column (VARCHAR2, 12); identifies the language of the translated article text.
• MAJOR_VERSION – The contract version associated with this historical record.
• SOURCE_LANG – Standard MLS column identifying the source language of the translation.
• SFWT_FLAG – Flag indicating that a value was changed in a different language; documented as not fully implemented in 11i.
• OBJECT_VERSION_NUMBER – Sequential counter initialized to 1 on insert and incremented on update; used by APIs to enforce optimistic locking.
• COMMENTS – User-entered comment text (VARCHAR2, 1995).
• VARIATION_DESCRIPTION – The standard article variation description (VARCHAR2, 240).
• NAME – Used for non-standard articles (VARCHAR2, 150).
• TEXT – CLOB (4000) holding the body text of non-standard articles.
• SAV_SAV_RELEASE – Version of the article (VARCHAR2, 150).
• SECURITY_GROUP_ID – Used in hosted environments; the sole documented FK target (FND_SECURITY_GROUPS).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard Who audit columns.

The business-key candidate is OKC_K_ARTICLES_TLH_U1 (ID, LANGUAGE, MAJOR_VERSION), which mirrors the composite primary key OKC_K_ARTICLES_TLH_PK. A separate LOB unique index, SYS_IL0000085279C00010$$, supports the TEXT CLOB column, stored in the APPS_TS_TX_DATA tablespace. The table itself resides in APPS_TS_TX_DATA with PCT_FREE 10, while the unique index is placed in APPS_TS_TX_IDX.

Common Use Cases and Queries

Because this is an MLS history table, typical usage centers on recovering prior versions of contract articles and retrieving language-specific text. Reporting queries commonly filter by ID and order by MAJOR_VERSION to reconstruct the version lineage:

• Retrieving the latest version of an article for a given language: SELECT * FROM OKC.OKC_K_ARTICLES_TLH WHERE ID = :id AND LANGUAGE = :lang ORDER BY MAJOR_VERSION DESC.
• Auditing changes to non-standard article text by comparing the TEXT CLOB across MAJOR_VERSION values.
• MLS translation reporting, joining against FND_LANGUAGES on LANGUAGE and SOURCE_LANG to display installed language names.
• Hosted-environment security filtering using SECURITY_GROUP_ID, joined to FND_SECURITY_GROUPS.

Note the warning carried in the documentation: Oracle does not support direct access to applications data through this object except from standard Oracle Applications programs. Custom queries should therefore be limited to read-only reporting.

Related Objects

Based on the documented FK and PK relationships, the most significant related objects are:

• FND_SECURITY_GROUPS – Referenced via OKC_K_ARTICLES_TLH.SECURITY_GROUP_ID; supports hosted multi-tenant filtering.
• OKC_K_ARTICLES_TL – The current (non-history) MLS articles table, sharing the ID/LANGUAGE/MAJOR_VERSION key structure.
• OKC_K_ARTICLES_B – The base table holding language-independent article attributes; the ID column is the common join key.
• OKC_K_ARTICLES_H – The primary history table that typically drives creation of the _TLH translation-history rows.
• OKC_K_LINES_B / OKC_K_LINES_TL – Contract lines that reference articles and clauses, joinable through article ID where applicable.
• FND_LANGUAGES – Provides language descriptions for LANGUAGE and SOURCE_LANG columns in MLS reporting.
• OKC_CONTRACT_PUB or OKC_ARTICLE_PUB APIs – Standard Oracle APIs that maintain article and version records, using OBJECT_VERSION_NUMBER to control concurrent updates.

Collectively, these objects support the contract authoring, translation, and versioning lifecycle central to Oracle Contracts.