Search Results okc_sections_tlh_pk

Overview

OKC_SECTIONS_TLH is a table in the OKC (Contracts Core) schema of Oracle E-Business Suite. Per the ETRM repository documentation, it stores translatable columns from OKC_SECTIONS_B in accordance with Oracle Multi-Lingual Support (MLS) standards. The table is explicitly designated as obsolete, having been obsoleted in release 11.5.10. As a result, it remains in the schema for historical and upgrade-related reasons but is not populated or maintained by the current Contracts application logic in EBS 12.1.1 or 12.2.2. Its status is recorded as VALID, meaning the object still exists in the data dictionary even though it is functionally retired.

From a modeling perspective, the ETRM heuristic Data Vault classification places this object as a standalone entity, indicating no outgoing many-to-many link relationships were mined from its foreign-key structure. In Data Vault terms it would be treated as a satellite attached to the OKC_SECTIONS_B hub, carrying the language-dependent descriptive attribute (HEADING) keyed by the parent identifier, language, and major version.

Key Information Stored

The documented physical schema contains twelve columns. The most significant are:

• ID — Identifier of the parent section record in OKC_SECTIONS_B; part of the composite primary key.
• LANGUAGE — MLS language code indicating the translation language of the row; part of the primary key.
• MAJOR_VERSION — Version indicator of the parent section row; part of the primary key.
• HEADING — The translated section heading text, the principal business attribute carried by this table.
• SOURCE_LANG — The source language of the translation, per MLS conventions.
• SFWT_FLAG — Standard MLS "seed/fixed/whichever" flag controlling translation behavior.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting function and data security.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO audit columns tracking row creation and maintenance.

The surrogate-style primary key constraint is OKC_SECTIONS_TLH_PK, defined over (ID, LANGUAGE, MAJOR_VERSION). The unique index OKC_SECTIONS_TLH_U1 repeats the same three columns and therefore confirms (ID, LANGUAGE, MAJOR_VERSION) as the business-key candidate. The single documented foreign key, SECURITY_GROUP_ID, references FND_SECURITY_GROUPS.

Common Use Cases and Queries

Because the table was obsoleted in 11.5.10, direct querying is rare. Practical uses fall into three categories: historical reconciliation after upgrade, data migration auditing, and impact analysis before schema cleanup.

• Verifying whether any residual translated headings remain for a section after migration:
  SELECT id, language, major_version, heading FROM okc_sections_tlh WHERE id = :section_id;
• Locating rows whose security group is no longer valid:
  SELECT t.id, t.language, g.security_group_id FROM okc_sections_tlh t, fnd_security_groups g WHERE t.security_group_id = g.security_group_id(+);
• Comparing obsolete MLS content against the current OKC_SECTIONS_B / OKC_SECTIONS_TL columns to confirm migration completeness.
• Reporting on translation coverage per language for archival purposes:
  SELECT language, COUNT(*) FROM okc_sections_tlh GROUP BY language;

Reports should generally read the currently maintained section tables rather than this obsolete object.

Related Objects

The following objects are most relevant when working with OKC_SECTIONS_TLH:

• OKC_SECTIONS_B — The base (non-translatable) sections table from which this table's translatable columns were derived; joined on ID and MAJOR_VERSION.
• OKC_SECTIONS_TL — The current MLS translation table that replaced this obsolete object; joined on ID, LANGUAGE, and MAJOR_VERSION.
• OKC_SECTIONS_V — The view typically used by the Contracts application to expose section data including translated headings.
• FND_SECURITY_GROUPS — Referenced by the SECURITY_GROUP_ID foreign key for function security.
• OKC_SECTIONS_TLH_PK / OKC_SECTIONS_TLH_U1 — The primary key constraint and unique index enforcing row uniqueness on (ID, LANGUAGE, MAJOR_VERSION).

These relationships should be considered when assessing upgrade scripts, custom extensions, or obsolete-object cleanup in an EBS 12.1.1 or 12.2.2 environment.