Search Results cs_incident_statuses_tl




Overview
Explore in AI Chat

Overview

The CS_INCIDENT_STATUSES_TL table is a core translation table within the Oracle E-Business Suite Service (CS) module. It stores the language-specific, user-facing descriptions for Service Request (also referred to as Incident) status codes. This table enables the multi-language support (MLS) capability of Oracle EBS, allowing status names to be displayed in a user's preferred language. It operates in conjunction with its base table, CS_INCIDENT_STATUSES_B, which holds the language-independent seed data. The TL table is essential for any interface or report that presents Service Request status information to end-users in a global deployment.

Key Information Stored

The table's structure is designed to manage translated text. The primary key is a composite of INCIDENT_STATUS_ID and LANGUAGE, ensuring a unique translation entry for each status in each language. The NAME column holds the actual translated status description (e.g., "Open," "Closed," "Pending Customer Input") for the specified LANGUAGE. The SOURCE_LANG column identifies the original language in which the data was seeded, which is typically 'US' for American English. Other standard translation table columns, such as CREATION_DATE and LAST_UPDATE_DATE, are also present to track row history. The critical columns for functional use are INCIDENT_STATUS_ID, LANGUAGE, and NAME.

Common Use Cases and Queries

The primary use case is retrieving a status name in a user's session language for display in forms, reports, and self-service portals. A standard query involves joining the base and translation tables while filtering for the current language. For example, to list all active statuses in the current session language, a developer might use:

  • SELECT b.INCIDENT_STATUS_ID, tl.NAME FROM CS_INCIDENT_STATUSES_B b, CS_INCIDENT_STATUSES_TL tl WHERE b.INCIDENT_STATUS_ID = tl.INCIDENT_STATUS_ID AND tl.LANGUAGE = USERENV('LANG');

Reporting on Service Request volumes by status across different language installations also requires this table to ensure accurate labeling. Data migration or integration scripts that populate status descriptions for non-English users must insert corresponding rows into this TL table.

Related Objects

CS_INCIDENT_STATUSES_TL has defined foreign key relationships with several key objects, as documented in the ETRM metadata:

  • CS_INCIDENT_STATUSES_B: The primary base table. The foreign key on CS_INCIDENT_STATUSES_TL.INCIDENT_STATUS_ID references CS_INCIDENT_STATUSES_B.INCIDENT_STATUS_ID. All translations are child records of a seed status defined in the base table.
  • FND_LANGUAGES: The table is referenced twice for language validation. The foreign key on CS_INCIDENT_STATUSES_TL.LANGUAGE ensures the translation row uses a valid language code. A separate foreign key on CS_INCIDENT_STATUSES_TL.SOURCE_LANG validates the original source language of the data.

Applications will typically access this data via views or public APIs provided by the Service module rather than querying the table directly.