Results for “cs_incident_severities_tl”

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

Overview

CS_INCIDENT_SEVERITIES_TL is the translation (TL) table in the Oracle E-Business Suite Service (CS) module that stores language-specific, translated descriptive information about Service Request severities. In Oracle EBS, severity values such as "Critical," "High," "Medium," and "Low" are defined once in the base table CS_INCIDENT_SEVERITIES_B and then rendered in multiple installed languages through the corresponding _TL table. This table is owned by the CS schema and is marked VALID in the ETRM 12.2.2 documentation, with equivalent behavior in 12.1.1.

From a Data Vault modeling perspective, the mined classification for this object is standalone. This heuristic suggests modeling the table as a satellite-like structure keyed by its business identifier plus LANGUAGE, rather than as a hub or link, because it does not participate in documented foreign-key chains beyond a security group reference.

Key Information Stored

The physical schema documents 11 columns. The most significant are:

• INCIDENT_SEVERITY_ID — The surrogate primary key identifying the severity record; it links back to the base CS_INCIDENT_SEVERITIES_B table.
• LANGUAGE — The language code (from FND_LANGUAGES) qualifying the translated row. Together with INCIDENT_SEVERITY_ID it forms the composite primary key CS_INCIDENT_SEVERITIES_TL_PK.
• NAME — The translated severity name displayed to users, e.g., "Critical" in English or its localized equivalent.
• DESCRIPTION — The translated long description explaining the meaning or usage of the severity.
• SOURCE_LANG — The language in which the source record was originally authored, used by the translation (MLS) framework.
• SECURITY_GROUP_ID — A foreign key to FND_SECURITY_GROUPS, restricting visibility based on the operating unit or security context.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — The standard Oracle EBS audit columns recording who created and last modified the row and when.

The unique index CS_INCIDENT_SEVERITY_TL_U1 on (INCIDENT_SEVERITY_ID, LANGUAGE) serves as the business-key candidate and enforces one translation per severity per language.

Common Use Cases and Queries

Because the _TL table drives the multilingual user interface, it is used whenever severity labels must be retrieved in the session language. A typical query joins the base and translation tables, filtered to the current language, to produce a lookup list:

• Populating a severity LOV: SELECT t.incident_severity_id, t.name FROM cs_incident_severities_tl t WHERE t.language = USERENV('LANG').
• Reporting on service request volumes by severity name, joining CS_INCIDENT_SEVERITIES_TL to CS_INCIDENTS (or the SR tables) on INCIDENT_SEVERITY_ID.
• Data-quality checks confirming every base severity has a translation row in each implemented language.
• Security-scoped extracts filtered by SECURITY_GROUP_ID for multi-org deployments.

Administrators generally maintain these rows through the Service Request severity setup forms rather than direct DML, but read-only queries are common in custom reports and extracts.

Related Objects

The following objects are most significant given the documented relationships:

• CS_INCIDENT_SEVERITIES_B — The base table holding language-independent severity data; joined on INCIDENT_SEVERITY_ID.
• CS_INCIDENT_SEVERITIES_VL — The MLS view typically exposed to forms and reports, combining _B and _TL rows for the current language.
• FND_SECURITY_GROUPS — Referenced by the SECURITY_GROUP_ID foreign key.
• FND_LANGUAGES — Supplies the LANGUAGE and SOURCE_LANG values.
• CS_INCIDENTS / CS_INCIDENT_TYPES — Service Request entities whose severity references resolve through this table.

These objects, together with the standard MLS framework, make CS_INCIDENT_SEVERITIES_TL a small but essential configuration table for localized Service Request processing.