Search Results okc_condition_lines_tlh




Overview

OKC_CONDITION_LINES_TLH is the history table associated with OKC_CONDITION_LINES_TL, the translation table for contract condition lines in the Oracle Contracts Core (OKC) module. In Oracle EBS releases 12.1.1 and 12.2.2, the "_TLH" suffix denotes a translation history table: it stores prior versions of translatable descriptive columns whenever the corresponding row in the base translation table is updated. The table resides in the OKC schema and is documented as VALID. It is a system-maintained audit object rather than a user-facing entity; end users interact with condition lines through the Contracts authoring UI, while this table captures the historical trail of descriptive text changes.

Under a heuristic Data Vault classification mined from its foreign key structure, this object models as a standalone table. It carries no significant outbound links beyond a reference to the security framework; it functions effectively as a satellite-like history store attached to its parent translation table, with the business key inherited from that parent.

Key Information Stored

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

  • ID — Surrogate identifier of the condition line; together with LANGUAGE and MAJOR_VERSION it forms the primary key.
  • LANGUAGE — Language code of the translated description, enabling multilingual history retention.
  • MAJOR_VERSION — Version discriminator that distinguishes successive historical iterations of the same logical row.
  • SOURCE_LANG — The source language from which the translation originated.
  • SFWT_FLAG — Standard Oracle flag indicating whether the row was processed by the "Seed/Feed With Translation" concurrent program.
  • DESCRIPTION — The translatable text of the condition line at the time the history record was written.
  • CREATED_BY, CREATION_DATE — Standard WHO audit columns recording row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns capturing the last modification context.
  • SECURITY_GROUP_ID — Multi-tenant / security grouping reference, foreign-keyed to FND_SECURITY_GROUPS.

The surrogate primary key is defined by the constraint OKC_CONDITION_LINES_TLH_PK over (ID, LANGUAGE, MAJOR_VERSION). A unique index, OKC_CONDITION_LINES_TLH_U1, covers the same three columns and serves as the documented business-key candidate, confirming that no duplicate historical version may exist for a given line, language, and version combination.

Common Use Cases and Queries

Primary usage centers on audit and reconciliation of contract terms. Typical reporting includes reconstructing the textual evolution of a condition line, identifying when a description changed and by whom, and supporting localization audits across languages.

  • Retrieve full version history for a condition line:
    SELECT id, language, major_version, description, last_updated_by, last_update_date FROM okc.okc_condition_lines_tlh WHERE id = :p_id ORDER BY major_version;
  • Identify recent edits by a specific user:
    SELECT id, language, major_version, last_update_date FROM okc.okc_condition_lines_tlh WHERE last_updated_by = :user_id AND last_update_date > :start_date;
  • Compare current versus prior descriptions by joining the parent translation table on ID, LANGUAGE, and MAJOR_VERSION.
  • Security-scoped extracts filtered on SECURITY_GROUP_ID for multi-org reporting.

Related Objects

  • OKC_CONDITION_LINES_TL — The parent translation table; join on ID, LANGUAGE, and MAJOR_VERSION.
  • OKC_CONDITION_LINES_B — The base (non-translated) condition line table referenced through ID.
  • OKC_CONDITION_LINES_TLH_PK / _U1 — Primary key and unique index enforcing history uniqueness.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security grouping.
  • FND_LANGUAGES — Implicit lookup for valid LANGUAGE and SOURCE_LANG values.
  • FND_USER — Resolves CREATED_BY and LAST_UPDATED_BY to user identities.
  • OKC Contracts Core translation and versioning concurrent programs that populate this table automatically.