Results for “okc_k_lines_tlh_pk”

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

Overview

OKC_K_LINES_TLH is a history (audit) table in the OKC — Contracts Core module of Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. It preserves prior versions of rows maintained in OKC_K_LINES_TL, the translation base table that holds language-dependent descriptive attributes for contract lines. Whenever a contract line's translatable text attributes are updated, Oracle's multi-language translation infrastructure writes the superseded row into OKC_K_LINES_TLH, keyed by the original row identifier, language, and a monotonically increasing major version number. The table is owned by the OKC schema and is marked VALID in the ETRM data dictionary.

Under a heuristic Data Vault classification mined from its foreign key structure, OKC_K_LINES_TLH presents as a standalone object — it carries no outgoing links to other business entities beyond a reference to FND_SECURITY_GROUPS. In modeling terms it is therefore best treated as a satellite-like history structure attached to the OKC_K_LINES_TL entity, recording descriptive change over time rather than expressing relationships between business keys.

Key Information Stored

The documented physical schema comprises 17 columns. The most significant are:

• ID — Surrogate identifier of the contract line's translation row; part of the composite primary key and of the unique business-key index.
• LANGUAGE — The language code of the translated text; part of the composite primary key.
• MAJOR_VERSION — Version sequence number that distinguishes successive historical snapshots of the same ID/LANGUAGE pair.
• SOURCE_LANG — The source language from which the translated text was derived.
• SFWT_FLAG — Flag indicating whether the row participates in the "Seed From Working Table" translation process.
• NAME — The contract line name as it stood at the captured version.
• COMMENTS — Free-form descriptive comments associated with the line.
• ITEM_DESCRIPTION — The item description carried on the contract line.
• BLOCK23TEXT — Supplemental descriptive text block used by the contracts line framework.
• OKE_BOE_DESCRIPTION — Description attribute integrated from the OKE (Project Contracts) billing/BOE context.
• COGNOMEN — Secondary name or alias attribute held on the line record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing row provenance and change tracking.
• SECURITY_GROUP_ID — Multi-tenant security grouping column with a foreign key to FND_SECURITY_GROUPS.

The composite primary key OKC_K_LINES_TLH_PK is defined on (ID, LANGUAGE, MAJOR_VERSION). A unique index, OKC_K_LINES_TLH_U1, is defined on the same three columns and serves as the documented business-key candidate.

Common Use Cases and Queries

Typical uses include reconstructing the description history of a contract line for audit or dispute resolution, comparing successive versions of line text, and feeding change-data-capture extracts into downstream reporting. A representative query retrieves the version history for a single line:

• SELECT id, language, major_version, name, comments, item_description, last_update_date FROM okc_k_lines_tlh WHERE id = :line_id ORDER BY major_version DESC;
• Joining to the current translation row to isolate differences: SELECT h.id, h.major_version, h.name hist_name, t.name curr_name FROM okc_k_lines_tlh h, okc_k_lines_tl t WHERE h.id = t.id AND h.language = t.language AND h.name <> t.name;
• Filtering by security group for multi-org reporting: ... WHERE security_group_id = :sgid;

Because the table grows in step with translation updates, reports should always constrain by ID, LANGUAGE, or date range to avoid full scans.

Related Objects

• OKC_K_LINES_TL — The base translation table for which this object is the history repository; joined on ID and LANGUAGE.
• OKC_K_LINES_B / OKC_K_LINES — The contract line base and view entities whose descriptive attributes flow into the translation and history tables.
• OKC_K_HEADERS_TLH / OKC_K_HEADERS_TL — Parallel history and translation structures at the contract header level.
• FND_SECURITY_GROUPS — Referenced by the SECURITY_GROUP_ID foreign key.
• OKC_CONTRACT_LINES_V and related contract line views — Reporting views that surface current line text and can be compared against history rows.