Results for “oke_chg_statuses_tl”

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

Overview

OKE_CHG_STATUSES_TL is the translation (multi-lingual) table for contract change request statuses within the OKE – Project Contracts module of Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, Oracle stores user-facing descriptive text in language-specific ("_TL") tables so that the same functional entity can be presented in multiple installed languages. This table holds the translated status name and description for each change request status defined in the base table OKE_CHG_STATUSES_B.

The object is a child of the base table via a foreign key on CHG_STATUS_CODE, meaning a single base status row can have one translated row per installed language. The metadata's heuristic Data Vault classification is satellite-leaning, which is a modeling suggestion: the table behaves like a satellite carrying descriptive, language-dependent attributes attached to the base status entity, rather than a hub of independent business keys or a link resolving many-to-many relationships.

Key Information Stored

The 10 documented columns center on identification, translation text, and standard EBS audit/MLS bookkeeping.

• CHG_STATUS_CODE – The business key code identifying the change request status. It is the foreign key to OKE_CHG_STATUSES_B and part of both the primary key and the U1 unique index.
• LANGUAGE – The installed language code for the translation row; combined with CHG_STATUS_CODE it forms the primary key OKC_CHG_STATUSES_TL_PK (also index OKE_CHG_STATUSES_TL_U1).
• CHG_STATUS_NAME – The translated, user-visible status name; it participates in the second unique index, OKE_CHG_STATUSES_TL_U2 (CHG_STATUS_NAME, LANGUAGE).
• DESCRIPTION – The translated free-text description of the status.
• SOURCE_LANG – Identifies the source language of the row for MLS (Multi-Lingual Support) processing.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard EBS audit columns recording who created and last modified the translation and when.

The surrogate/business identifier for this table is the composite (CHG_STATUS_CODE, LANGUAGE). The U2 unique index on (CHG_STATUS_NAME, LANGUAGE) enforces that a status name is unique within a language, acting as a business-key candidate for display text.

Common Use Cases and Queries

Typical use cases include resolving a change request status code to its translated display name for reports, contract change management screens, and integration extracts. Because it is an MLS table, queries should filter by the session or requested language.

• Look up a status name by code: SELECT chg_status_name, description FROM oke_chg_statuses_tl WHERE chg_status_code = :code AND language = USERENV('LANG');
• Join base and translation for a complete status list: SELECT b.chg_status_code, t.chg_status_name FROM oke_chg_statuses_b b, oke_chg_statuses_tl t WHERE b.chg_status_code = t.chg_status_code AND t.language = USERENV('LANG');
• Reporting on change request statuses for contract changes, driving picklists or LOVs that must render translated text.
• Data migration or interface validation, confirming that a required translation exists for each installed language.

Related Objects

• OKE_CHG_STATUSES_B – The base table; joined on CHG_STATUSES_TL.CHG_STATUS_CODE = OKE_CHG_STATUSES_B.CHG_STATUS_CODE. This is the documented foreign key relationship and the primary parent of this table.
• OKE_CHG_STATUSES_VL – The MLS view exposing base and translated columns for language-aware querying.
• OKE_CHANGE_REQUESTS / contract change entities – Change request records reference the status code and resolve display text through this translation table.
• OKE_CONTRACTS and OKC-related change objects – Contract change management flows that present status values to users depend on the translated names held here.