Search Results oke_chg_statuses_tl




Overview
Explore in AI Chat

Overview

The OKE_CHG_STATUSES_TL table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It functions as a translation table, storing multi-lingual descriptions for the statuses of contract change requests. In Oracle EBS, transactional tables like OKE_CHG_STATUSES_B typically store the base, language-independent codes. The corresponding "_TL" (Translation) table holds the user-facing names and descriptions in multiple installed languages, enabling the application's global deployment. This table is critical for ensuring that status names (e.g., "Draft," "Submitted," "Approved") are displayed correctly in the user's preferred language within the Contract Changes functionality.

Key Information Stored

The table's structure is designed to support multi-lingual data with integrity. The most important columns are defined by its primary and unique keys. The primary key is a composite of CHG_STATUS_CODE and LANGUAGE, which uniquely identifies a single translation for a specific status code. The CHG_STATUS_CODE column is a foreign key linking to the base table OKE_CHG_STATUSES_B. The LANGUAGE column holds the ISO language code (e.g., 'US' for American English). A unique key is also defined on the combination of CHG_STATUS_NAME and LANGUAGE, enforcing that a given status name is unique within a language. While the explicit column list is not fully detailed in the provided metadata, a typical "_TL" table in Oracle Applications also includes a SOURCE_LANG column and columns for the translated name (CHG_STATUS_NAME) and description.

Common Use Cases and Queries

This table is primarily accessed by the Oracle application itself to display localized status values on forms and reports. Common technical and reporting use cases include generating multi-lingual change request status reports and validating or auditing translation data. A typical query to retrieve all translations for a specific status code would be: SELECT language, chg_status_name FROM oke_chg_statuses_tl WHERE chg_status_code = 'DRAFT' AND source_lang = 'US';. For reporting purposes, a join to the base table is standard: SELECT b.chg_status_code, tl.language, tl.chg_status_name FROM oke_chg_statuses_b b, oke_chg_statuses_tl tl WHERE b.chg_status_code = tl.chg_status_code AND tl.language = userenv('LANG'); to fetch statuses in the current session's language.

Related Objects

The OKE_CHG_STATUSES_TL table has a direct and essential relationship with the OKE_CHG_STATUSES_B table, as indicated by the foreign key from CHG_STATUS_CODE. This establishes it as the child table in a base-translation pair. The primary key constraint OKC_CHG_STATUSES_TL_PK and the unique key OKC_CHG_STATUSES_TL_UK01 are critical dependent objects that enforce data integrity. As a central reference table for change statuses, it is likely referenced by various application programming interfaces (APIs) within the OKE module, such as the Change Management APIs, and by views that present a consolidated, language-sensitive perspective of change request data for reporting and processes.