Search Results css_def_severities_tl

Overview

The CSS_DEF_SEVERITIES_TL table is a translatable seed data table within the Oracle E-Business Suite (EBS) module CSS - Support. Its primary role is to store language-specific translations for the names and descriptions of support case severity codes. This enables the Support application to display severity information in the language of the user's session, a core requirement for global deployments. It is critical to note that the provided ETRM metadata explicitly states this product module is "Obsolete" and that the table is "Not implemented in this database." This indicates the object is part of a legacy or discontinued application component and may not be present or actively used in a standard EBS 12.1.1 or 12.2.2 instance.

Key Information Stored

As a translatable table (denoted by the "_TL" suffix), it holds the translated text for its corresponding base table, which would logically be named CSS_DEF_SEVERITIES_B. Based on standard EBS TL table design and the provided primary key, the key columns are:

• SEVERITY_ID: The foreign key that links to the unique identifier of a severity definition in the base table.
• LANGUAGE: The ISO code for the language of the translated text in that row (e.g., 'US' for American English).
• SOURCE_LANG: A column typically present in TL tables that indicates the original language of the seed data (usually 'US').
• SEVERITY_NAME and/or DESCRIPTION: Columns containing the actual translated text for the severity's display name and descriptive text.

The primary key constraint CSS_DEF_SEVERITIES_TL_PK ensures a unique translation exists per severity per language.

Common Use Cases and Queries

Given the object's obsolete status, direct operational use cases are unlikely in current implementations. Historically, its function would have been integral to multilingual reporting and user interface rendering. A typical query to retrieve translated severities for the current session language would utilize the NLS_LANGUAGE session parameter. A standard reporting pattern would join the base and translatable tables:

SELECT b.SEVERITY_CODE, tl.SEVERITY_NAME, tl.DESCRIPTION
FROM CSS_DEF_SEVERITIES_B b,
     CSS_DEF_SEVERITIES_TL tl
WHERE b.SEVERITY_ID = tl.SEVERITY_ID
AND tl.LANGUAGE = USERENV('LANG');

Any customizations or data fixes for severity translations would have targeted this table, though such activities are now improbable.

Related Objects

The primary documented relationship is its dependency on the base table CSS_DEF_SEVERITIES_B via the SEVERITY_ID column. The structure is a classic EBS seed data model: the "_B" base table holds the code and immutable attributes, while the "_TL" table holds the translatable text. There are no foreign keys documented from this table to others. Applications or views within the obsolete CSS - Support module would have referenced this table to display user-friendly severity names. In a functional instance, the FND_LOOKUP_VALUES table might serve a similar purpose for active lookup codes, but no direct relationship exists between those objects and this deprecated table.