Search Results okc_sections_tlh_u1

Overview

OKC.OKC_SECTIONS_TLH is a translation (language) history table in the Oracle Contracts (OKC) schema of Oracle E-Business Suite. It stores the language-dependent, versioned heading text for contract sections, allowing the same logical section to carry a heading in multiple languages across multiple major versions of a contract. The "TLH" suffix denotes a translated table with history/versioning semantics, distinguishing it from the base OKC_SECTIONS_TL (translation) and OKC_SECTIONS_B (base) tables. In EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_TX_DATA tablespace with associated unique index OKC_SECTIONS_TLH_U1 in APPS_TS_TX_IDX. The object is designated Oracle Internal Use Only; supported access is through standard Oracle Applications programs and the Contracts APIs, not direct SQL against the base table.

From a Data Vault modeling perspective, the documented structure — a composite key of ID, LANGUAGE, and MAJOR_VERSION together with descriptive attributes and standard Who columns — suggests classification as a satellite. The ID and MAJOR_VERSION capture the parent contract-section context, LANGUAGE captures the translation context, and the descriptive heading attributes attach to that key combination.

Key Information Stored

The columns below are the most significant as documented in the ETRM metadata:

• ID (NUMBER) — Primary key component identifying the parent contract section. Documented as a primary key column.
• LANGUAGE (VARCHAR2 12) — Standard MLS column indicating the language of the stored heading.
• MAJOR_VERSION (NUMBER) — The version of the contract for this history record; part of the composite primary key.
• HEADING (VARCHAR2 300) — The section heading text, the principal descriptive payload of the row.
• SOURCE_LANG (VARCHAR2 12) — Standard MLS column identifying the source language of the translation.
• SFWT_FLAG (VARCHAR2) — Indicates a value was changed in another language; noted as not fully implemented in 11i.
• CREATED_BY, CREATION_DATE — Standard Who columns recording row creation audit.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns recording the last modification audit.
• SECURITY_GROUP_ID (NUMBER) — Used in hosted environments to partition data by security group.

The surrogate-style primary key is OKC_SECTIONS_TLH_PK (ID, LANGUAGE, MAJOR_VERSION), and the unique index OKC_SECTIONS_TLH_U1 (ID, LANGUAGE, MAJOR_VERSION) — the object the user searched for — enforces the same business-key candidate set. The u1 index therefore guarantees that only one heading row exists per section, language, and major version.

Common Use Cases and Queries

Typical scenarios include multilingual contract reporting, retrieving the heading for a specific contract version and language, and auditing heading changes across versions. A representative query pattern:

• Join to OKC_SECTIONS_TL / OKC_SECTIONS_B on ID to obtain section definitions across all languages.
• Filter by LANGUAGE to render headings for a target locale.
• Filter by MAJOR_VERSION to isolate a specific contract revision.

Sample SQL: SELECT ID, LANGUAGE, MAJOR_VERSION, HEADING FROM OKC.OKC_SECTIONS_TLH WHERE ID = :section_id AND LANGUAGE = USERENV('LANG') AND MAJOR_VERSION = :major_version;

Related Objects

• OKC_SECTIONS_TLH (synonym/view in APPS) — the APPS-layer object referencing the OKC base table.
• OKC_SECTIONS_TL — current translation rows, sharing the ID and LANGUAGE keys.
• OKC_SECTIONS_B — base (non-translated) section definitions keyed by ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID in hosted environments.
• OKC_SECTIONS_TLH_PK / OKC_SECTIONS_TLH_U1 — supporting constraints and the unique index the user searched for.