Search Results css_def_severities_vl

Overview

CSS_DEF_SEVERITIES_VL is a dated, language-enabled (VL) view defined within the CSS – Support module of Oracle E-Business Suite. In the ETRM metadata for releases 12.1.1 and 12.2.2, the object is documented with the description "Severities" and is classified under CSS – Support (obsolete). The view exists to expose the list of severity definitions used by the support/incident tracking functionality, joining the base table that stores severity attributes to the translation table that holds the language-specific name and description. The VL suffix indicates that the view presents a view of language-dependent data filtered by the session's current language, so that users and applications see severity names and descriptions in their own language rather than the base language only.

Because the module is flagged obsolete, the view is not part of the mainstream Service or CRM foundation model in later releases, and the implementation note confirms it is Not implemented in this database in the documented environment. It therefore functions as a legacy, reporting-oriented object that would be used primarily where historical CSS data or customized support processes remain in scope.

Underlying Base Objects

The view is defined over two documented base objects: CSS_DEF_SEVERITIES_B and CSS_DEF_SEVERITIES_TL. The former stores the base (language-independent) severity record, including identifiers, ordering, audit columns, the descriptive flexfield attributes, and the active date range. The latter stores translated NAME and DESCRIPTION values keyed by SEVERITY_ID and LANGUAGE. The join condition is:

• B.SEVERITY_ID = T.SEVERITY_ID
• T.LANGUAGE = USERENV('LANG')

This is the standard Oracle EBS VL pattern, where the base table supplies structural and audit attributes and the translation table supplies the linguistic content. ETRM documentation for 12.2.2 lists no referenced base objects beyond the view's own definition, so the base tables should be treated as the authoritative sources for the underlying data model.

Key Columns

The view exposes the combined column set of both base tables. The principal columns are:

• ROW_ID – the ROWID of the base table row, useful for direct row identification.
• SEVERITY_ID – the primary key linking base and translation records; the joining key for all related queries.
• OBJECT_VERSION_NUMBER – optimistic locking version column, used to detect concurrent updates.
• CATEGORY_TYPE – the category under which the severity is classified.
• SORT_ORDER – the display ordering sequence for severity lists.
• NAME and DESCRIPTION – the language-specific labels sourced from CSS_DEF_SEVERITIES_TL.
• START_DATE_ACTIVE and END_DATE_ACTIVE – the effective date range for the severity definition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard audit columns.
• ATTRIBUTE1–ATTRIBUTE15 and CONTEXT – descriptive flexfield columns supporting customer-specific extensions.

Common Use Cases and Queries

Because the view resolves the language at query time, it is well suited to reporting and integration work that must present severity values in the user's locale. Typical scenarios include listing active severities for selection lists, joining severity names to incident or interaction data, and extracting the descriptive flexfield attributes for validation or migration. A representative query is:

SELECT severity_id, name, description, sort_order, category_type FROM css_def_severities_vl WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY sort_order;

Where base-language data is required regardless of session language, querying CSS_DEF_SEVERITIES_TL directly with an explicit LANGUAGE predicate is preferable. Given the obsolete status and the documented implementation note, the view should be regarded as legacy and validated in any target instance before use.