Search Results cs_incident_severities_tl

Overview

The CS_INCIDENT_SEVERITIES_TL table is a core translation table within the Oracle E-Business Suite Service (CS) module for versions 12.1.1 and 12.2.2. It stores the language-specific, user-facing descriptions for Service Request (incident) severity codes. This table enables the multilingual display of severity values, such as "Critical," "High," "Medium," and "Low," within the application's user interface based on the session language. Its primary role is to support the global deployment of Oracle Service by separating translatable text from the base severity definitions, allowing a single severity code to be presented appropriately across different linguistic territories.

Key Information Stored

The table's structure is designed for the standard Oracle E-Business Suite multilingual model. The primary key is a composite of INCIDENT_SEVERITY_ID and LANGUAGE, ensuring a unique entry for each severity in each language. Key columns include:

• INCIDENT_SEVERITY_ID: Foreign key linking to the base severity definition (e.g., in CS_INCIDENT_SEVERITIES_B).
• LANGUAGE: The ISO language code (e.g., 'US', 'FR', 'DE') for the translation.
• SOURCE_LANG: Indicates the original language in which the data was entered.
• NAME: The translated name of the severity (e.g., "Critique" in French).
• DESCRIPTION: A translated description providing further detail about the severity level.

Standard audit columns like CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY are also present to track data changes.

Common Use Cases and Queries

This table is primarily accessed by the application runtime to display severity names. Common technical and reporting use cases include generating translated lists for reports or data extracts, and validating setup data. A typical query to retrieve all severity translations would join to the base table:

• Sample SQL: SELECT b.SEVERITY_CODE, tl.NAME, tl.LANGUAGE FROM CS_INCIDENT_SEVERITIES_B b, CS_INCIDENT_SEVERITIES_TL tl WHERE b.INCIDENT_SEVERITY_ID = tl.INCIDENT_SEVERITY_ID AND tl.LANGUAGE = userenv('LANG');

For data migration or setup scripts, it is critical to populate this table for each installed language to ensure proper UI functionality. Administrators may query it to audit which severities have been translated into which languages.

Related Objects

CS_INCIDENT_SEVERITIES_TL has direct relationships with several key Service module objects. The most critical is the base table CS_INCIDENT_SEVERITIES_B, which holds the non-translatable attributes (like SEVERITY_CODE, ACTIVE_FLAG). The primary key INCIDENT_SEVERITY_ID is a foreign key to this base table. The table is also referenced by the Service Request entity tables, such as CS_INCIDENTS_ALL_B, where the INCIDENT_SEVERITY_ID column stores the severity assigned to a specific service request. Furthermore, standard Oracle APIs and views that handle translated data, such as FND_LOOKUP_VALUES for flexfield value sets, may follow a similar architectural pattern but are not direct dependencies.