Results for “okc_condition_headers_tlh”

50+ results




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

Overview

OKC_CONDITION_HEADERS_TLH is a history (audit) table in the OKC schema belonging to the Contracts Core module of Oracle E-Business Suite. It functions as the translated-history shadow of OKC_CONDITION_HEADERS_TL, the multilanguage translation table that stores language-specific descriptive attributes of contract condition headers. In EBS Release 12.1.1 and 12.2.2, translation-enabled entities maintain three cooperating physical objects: the base table, the "_TL" translation table keyed by ID and LANGUAGE, and the "_TLH" history table that preserves prior versions of the translation rows as changes are applied.

Condition headers represent the top-level definitions of contract terms, clauses, and condition templates used by Oracle Contracts and its integration points (Purchasing, Sales, Order Management). When a condition header is modified or a translation is revised, the previous image of the translation row is written to OKC_CONDITION_HEADERS_TLH. The table therefore supports auditability, point-in-time reconstruction, and incremental extraction in data warehousing pipelines. The ETRM metadata classifies this object heuristically as standalone within a Data Vault model; a reasonable modeling suggestion is to treat it as a versioned satellite keyed on the natural business key plus MAJOR_VERSION, since it captures descriptive change over time rather than relationships between entities.

Key Information Stored

The table contains 15 documented columns. Its primary key, OKC_CONDITION_HEADERS_TLH_PK, is composed of ID, LANGUAGE, and MAJOR_VERSION. The same three columns form the unique index OKC_CONDITION_HEADERS_TLH_U1, which serves as the business-key candidate for the row version identity. ID links the history row back to its parent condition header; LANGUAGE identifies the installed language of the translation; MAJOR_VERSION distinguishes successive historical images of the same translation.

The presence of both the surrogate PK columns and the WHO audit columns, combined with the absence of an FK on ID, distinguishes this object from the live translation table and confirms its archival role.

Common Use Cases and Queries

Primary use cases include historical reporting on condition header wording, compliance auditing of clause changes, and incremental ETL where only prior-version text is required. A typical reconstruction query joins the live translation to its history to compare current and prior descriptions:

  • SELECT h.ID, h.LANGUAGE, h.MAJOR_VERSION, h.NAME, h.DESCRIPTION FROM OKC.OKC_CONDITION_HEADERS_TLH h WHERE h.ID = :p_id ORDER BY h.MAJOR_VERSION DESC;
  • Audit trail query filtering on LAST_UPDATE_DATE within a date range and joining to FND_USERS on LAST_UPDATED_BY.
  • Security-scoped extracts filtering by SECURITY_GROUP_ID to respect operating unit boundaries when feeding downstream reporting schemas.

Related Objects

  • OKC_CONDITION_HEADERS_TL – Live translation table; OKC_CONDITION_HEADERS_TLH preserves its prior rows.
  • OKC_CONDITION_HEADERS_B – Base table holding non-translated condition header attributes, joined on ID.
  • FND_SECURITY_GROUPS – Referenced by SECURITY_GROUP_ID for row-level security.
  • FND_LANGUAGES – Validates LANGUAGE and SOURCE_LANG values.
  • FND_USERS / FND_USER – Resolves CREATED_BY and LAST_UPDATED_BY for audit reporting.
  • OKC_CONDITIONS_B / OKC_CONDITIONS_TL – Condition instances that reference condition headers.