Results for “okc_changes_tl”

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

Overview

OKC_CHANGES_TL is the translation table for OKC_CHANGES_B within the OKC – Contracts Core product of Oracle E-Business Suite. It stores the language-dependent (translatable) columns of the base changes entity in accordance with Oracle's Multi-Lingual Support (MLS) standards. For each base row in OKC_CHANGES_B, one row exists in OKC_CHANGES_TL per installed language in which the change record has been translated. This separation of translatable text from language-independent attributes improves performance, reduces redundancy, and enables multi-language contract change documentation.

Under a heuristic Data Vault classification mined from the foreign key structure, this table is assessed as standalone. In Data Vault modeling terms, it functions as a satellite attached to the OKC_CHANGES_B hub, since it carries descriptive, language-specific attributes keyed by the parent entity's identifier plus LANGUAGE. This is a modeling suggestion only; the authoritative definition remains the Oracle EBS schema.

Key Information Stored

• ID – Surrogate identifier of the parent change record; part of the composite primary key OKC_CHANGES_TL_PK (ID, LANGUAGE) and of the unique index OKC_CHANGES_TL_U1. It joins back to OKC_CHANGES_B.
• LANGUAGE – The installed language code for the translated row; the second component of the primary key and unique index.
• SOURCE_LANG – Indicates the source language from which the translation originated, supporting MLS auditing.
• SFWT_FLAG – The "Seed/Force/Whatever Translation" flag used by Oracle's translation framework to govern whether the row may be overwritten by seeded translation data.
• SHORT_DESCRIPTION – The short, translated description of the contract change.
• CHANGE_TEXT – The translated body or narrative text of the change record; the primary business content in the translation row.
• CREATED_BY, CREATION_DATE – Standard audit columns recording who created the translation row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard audit columns capturing the most recent modification, its author, and the associated login session.
• SECURITY_GROUP_ID – Multi-org / security grouping reference; documented FK to FND_SECURITY_GROUPS, used for row-level access control.

The surrogate primary key is the composite (ID, LANGUAGE), while OKC_CHANGES_TL_U1 (ID, LANGUAGE) documents the business-key candidate that enforces one translation per entity per language.

Common Use Cases and Queries

Typical scenarios include retrieving contract change descriptions in a specific language, auditing translation coverage, and joining translatable text with the base attributes.

• Fetching a translated change for a given language:

  SELECT id, language, short_description, change_text FROM okc_changes_tl WHERE id = :p_id AND language = USERENV('LANG');

• Joining base and translation rows (territory = OKC, MLS pattern):

  SELECT b.id, t.short_description, t.change_text FROM okc_changes_b b, okc_changes_tl t WHERE b.id = t.id AND t.language = USERENV('LANG');

• Reporting on translation completeness for a source language:

  SELECT id, language, source_lang FROM okc_changes_tl WHERE source_lang = 'US' ORDER BY id;

• Auditing recent translation activity using the standard WHO columns (last_updated_by, last_update_date).

Related Objects

• OKC_CHANGES_B – Base (non-translatable) changes table; joined on ID and paired with LANGUAGE for MLS lookups.
• OKC_CHANGES_VL – The MLS view that typically joins OKC_CHANGES_B to OKC_CHANGES_TL, presenting a single logical row per language.
• FND_SECURITY_GROUPS – Referenced by SECURITY_GROUP_ID for access control.
• FND_LANGUAGES – Provides the valid values for LANGUAGE and SOURCE_LANG.
• OKC_CHANGES_TL_PK / OKC_CHANGES_TL_U1 – Primary key and unique index enforcing uniqueness on (ID, LANGUAGE).