Results for “okc_changes_tl_u1”

10 results




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

Overview

OKC.OKC_CHANGES_TL is the translation (MLS) table for the Oracle Contracts Core changes entity. It stores language-specific, user-facing text associated with contract change records defined in the base table OKC_CHANGES_B. As documented in the ETRM metadata, the table consists of translatable columns from OKC_CHANGES_B, maintained according to Oracle Multi-Language Support (MLS) standards. This design separates language-independent change attributes from their textual descriptions, allowing the same change record to be rendered in multiple installed languages without duplicating transactional data.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, while its unique index is placed in APPS_TS_TX_IDX. Its primary key, OKC_CHANGES_TL_PK, is composed of (ID, LANGUAGE), enforcing one row per change per language. The heuristic Data Vault classification for this object is standalone, meaning it does not participate in FK relationships with other business entities; it should therefore be modeled as a dependent satellite of the base changes entity rather than as an independent hub or link.

Key Information Stored

  • ID — Numeric primary key column, shared with OKC_CHANGES_B; identifies the change record.
  • LANGUAGE — Standard MLS column (VARCHAR2 12) indicating the language of the row; part of the composite primary key and of the unique index OKC_CHANGES_TL_U1.
  • SOURCE_LANG — Standard MLS column recording the language of the source record from which the translation was derived.
  • SFWT_FLAG — Flag indicating a value was changed in another language; the metadata notes it is not fully implemented in 11i.
  • SHORT_DESCRIPTION — User-entered free-format abbreviated description of the change (VARCHAR2 600).
  • CHANGE_TEXT — CLOB (4000) holding the full change text; this is the primary translatable payload.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns providing audit trail information.
  • SECURITY_GROUP_ID — Used in hosted environments; the sole documented FK reference, pointing to FND_SECURITY_GROUPS.

The unique index OKC_CHANGES_TL_U1 on (ID, LANGUAGE) is the business-key candidate, functionally equivalent to the primary key. A LOB unique index, SYS_IL0000085446C00006$$, supports the CHANGE_TEXT CLOB segment.

Common Use Cases and Queries

Because the table is purely descriptive, the dominant use case is reporting and retrieval of contract change text in a selected language. A typical join resolves the base row with its translation:

  • Fetch change text by language: SELECT b.ID, t.SHORT_DESCRIPTION, t.CHANGE_TEXT FROM OKC.OKC_CHANGES_B b, OKC.OKC_CHANGES_TL t WHERE b.ID = t.ID AND t.LANGUAGE = USERENV('LANG');
  • List all translations for a change: SELECT LANGUAGE, SOURCE_LANG, SHORT_DESCRIPTION FROM OKC.OKC_CHANGES_TL WHERE ID = :change_id ORDER BY LANGUAGE;
  • Identify missing translations: compare distinct LANGUAGE values against FND_LANGUAGES to detect changes lacking a localized row.
  • Audit reporting: filter on LAST_UPDATE_DATE or LAST_UPDATED_BY to trace translation maintenance activity.

Translation maintenance is typically performed through the Oracle Forms-based Contracts application or concurrent MLS programs rather than direct DML, ensuring consistency with OKC_CHANGES_B.

Related Objects

  • OKC.OKC_CHANGES_B — Base (language-independent) table; joined on ID. This is the parent entity for all translation rows.
  • FND_SECURITY_GROUPS — Referenced through the SECURITY_GROUP_ID FK for hosted (multi-tenant) deployments.
  • FND_LANGUAGES — Provides the valid LANGUAGE code list and installed-language validation.
  • APPS.OKC_CHANGES_TL — The APPS-layer synonym/view used by application code and reports in place of the OKC schema object.
  • OKC_CHANGES_TL_U1 — Unique index enforcing business-key uniqueness on (ID, LANGUAGE).
  • OKC_CHANGES_TL_PK — Primary key constraint underpinning row identity.

Together these objects form the complete retrieval path for contract change descriptions across languages, with OKC_CHANGES_TL supplying the localized narrative and OKC_CHANGES_B supplying the structural attributes.