Search Results okc_k_headers_tlh_u1

Overview

OKC.OKC_K_HEADERS_TLH is a table in the Oracle Contracts (OKC) schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The "_TLH" suffix identifies it as a mirrors image table that supports the multilanguage (MLS) translation infrastructure of the base table OKC_K_HEADERS_TL. Per the ETRM metadata, this is a mirror image of the base table OKC_K_HEADERS_TL, and detailed column-level semantics should be obtained by referring to that base table. In practice, the "_TLH" table stores the historical or audit image of the translated contract header content, preserving prior language-specific description and editorial fields across changes.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. It is classified heuristically as standalone in the Data Vault model — meaning it does not reference any database object and acts neither as a classic hub, link, nor satellite interacting directly with other entities. The only downstream dependency is the internal object OKC_K_HEADERS_TLH# (the underlying index-organized/trigger support object). This standalone classification is offered as a modeling suggestion rather than a strict Data Vault designation.

Key Information Stored

The physical schema documented for 12.2.2 lists 18 columns. The most significant are:

• ID — surrogate identifier for the contract header record; part of the composite primary key.
• LANGUAGE and MAJOR_VERSION — together with ID, form the composite primary key OKC_K_HEADERS_TLH_PK and the unique index OKC_K_HEADERS_TLH_U1, the documented business-key candidate.
• SOURCE_LANG — the source language of the row, used by the MLS translation framework.
• SFWT_FLAG — the "Seed/Flatten/Whatever Translation" flag used by the translation runtime.
• SHORT_DESCRIPTION (600), COMMENTS (1995), DESCRIPTION (1995), COGNOMEN (300) — the descriptive text attributes carried in the translated header image.
• NON_RESPONSE_REASON, NON_RESPONSE_EXPLAIN (1995), and SET_ASIDE_REASON — contractual/business classification fields.
• Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS, supporting multi-org security partitioning.

The surrogate/primary key is (ID, LANGUAGE, MAJOR_VERSION); the unique index OKC_K_HEADERS_TLH_U1 mirrors this on the same three columns and is the documented business-key candidate.

Common Use Cases and Queries

This table is primarily queried when investigating the historical or translated state of contract headers. A typical query retrieves the audit trail for a given contract header across languages and major versions:

SELECT ID, LANGUAGE, MAJOR_VERSION, SHORT_DESCRIPTION, DESCRIPTION, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM OKC.OKC_K_HEADERS_TLH WHERE ID = :p_id ORDER BY MAJOR_VERSION, LANGUAGE;

Reporting use cases include translation completeness checks — identifying headers lacking rows for a target LANGUAGE — and audit reporting that compares the "_TLH" image against the live OKC_K_HEADERS_TL row to detect stale or out-of-sync description text. Because SECURITY_GROUP_ID is available, queries can be scoped to a security group for org-isolated extracts.

Related Objects

• OKC.OKC_K_HEADERS_TL — the base table this object mirrors; the authoritative source for column semantics.
• OKC.OKC_K_HEADERS_TLH# — internal object that references this table (per dependency data).
• FND_SECURITY_GROUPS — referenced via the SECURITY_GROUP_ID foreign key.
• OKC.OKC_K_HEADERS_ALL / OKC_K_HEADERS_B — the core contract header entities whose translated child rows this table history tracks.
• OKC_K_LINES and the OKC contract API layer — commonly joined when reporting header-to-line translated content.

The metadata documents no other referencing tables beyond the internal dependency and FND_SECURITY_GROUPS; the list above is a focused set of the most significant related objects.