Search Results sys_il0000085397c00007




Overview
Explore in AI Chat

Overview

OKC.OKC_RULES_TLH is a history table in the Oracle E-Business Suite (EBS) Contracts (OKC) schema, holding multi-lingual history records for the OKC_RULES_TL repository. Its principal purpose is to preserve prior major versions of contract rule translations, enabling audit, versioned comparison, and correction of contractual terms across releases of a contract. In Oracle EBS 12.1.1 and 12.2.2, OKC_RULES_TLH is stored in the APPS_TS_TX_DATA tablespace with PCT Free of 10 and is designated VALID at the time of the underlying ETRM documentation.

Heuristic Data Vault classification for this object, mined from its foreign key structure, is standalone. In practical modeling terms, the table behaves as a multi-active history satellite attached to the OKC_RULES_TL business key via ID, LANGUAGE, and MAJOR_VERSION, rather than as a hub or link. It carries descriptive attributes (COMMENTS, TEXT) alongside standard multi-lingual and Who audit columns.

Key Information Stored

The surrogate primary key is defined by OKC_RULES_TLH_PK on (ID, LANGUAGE, MAJOR_VERSION). A parallel unique index, OKC_RULES_TLH_U1, is documented on the same columns (ID, LANGUAGE, MAJOR_VERSION) in the APPS_TS_TX_IDX tablespace, making these three columns the documented business-key candidates for version-aware lookup.

  • ID (NUMBER) — Primary key column identifying the rule translation record.
  • LANGUAGE (VARCHAR2, 12) — Standard MLS column indicating the language of the historical translation.
  • MAJOR_VERSION (NUMBER) — The version of the contract for this history record; partitions the history for a given rule and language.
  • SOURCE_LANG (VARCHAR2, 12) — Standard MLS column recording the source language of the translation.
  • COMMENTS (VARCHAR2, 1995) — User entered comment retained with the historical record.
  • TEXT (CLOB, 4000) — Text column holding the translated rule content, with an associated LOB index SYS_IL0000085397C00007$$.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who audit columns recording who created and last touched the history row.
  • SFWT_FLAG (VARCHAR2) — Documented as not used.
  • SECURITY_GROUP_ID (NUMBER) — Used in hosted environments; documented as a foreign key to FND_SECURITY_GROUPS.

Common Use Cases and Queries

Typical scenarios include reconstructing a rule's text as of a prior contract version, comparing translated comments across versions, and reporting on translation changes for audit or dispute resolution. A straightforward query filters by the business-key candidates:

  • SELECT ID, LANGUAGE, MAJOR_VERSION, SOURCE_LANG, COMMENTS, TEXT FROM OKC.OKC_RULES_TLH WHERE ID = :id AND LANGUAGE = :lang ORDER BY MAJOR_VERSION;
  • Version delta reporting: compare COMMENTS and TEXT between adjacent MAJOR_VERSION values for a given ID and LANGUAGE.
  • Audit extraction: filter on CREATION_DATE / LAST_UPDATE_DATE ranges to isolate history rows produced during a contract amendment cycle.
  • Hosted-environment scoping: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS when operating in a multi-tenant deployment.

Related Objects

The documented relationship metadata identifies OKC_RULES_TL as the base table for which OKC_RULES_TLH is the history repository. The only documented foreign key is on SECURITY_GROUP_ID to FND_SECURITY_GROUPS. The table is accessed via the APPS synonym OKC_RULES_TLH. Because the ETRM extraction lists no additional inbound or outbound dependencies, the most significant related objects are:

  • OKC.OKC_RULES_TL — Base multi-lingual rules table; join on ID, LANGUAGE (with SOURCE_LANG alignment) to correlate current versus historical translations.
  • OKC.OKC_RULES_TLH_U1 — Unique index supporting version-aware lookups on (ID, LANGUAGE, MAJOR_VERSION).
  • OKC.OKC_RULES_TLH_PK — Primary key constraint backing the same column set.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for hosted environments.
  • APPS.OKC_RULES_TLH — Synonym exposing the table to application code and reports.
  • OKC_RULES and related OKC rule definition tables — conceptual parents of the rule text stored in OKC_RULES_TL / OKC_RULES_TLH.

Queries should generally target the APPS synonym and respect the unique business-key candidates to avoid duplicate version rows in reporting output.