Results for “cs_incident_severities_vl”

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

Overview

CS_INCIDENT_SEVERITIES_VL is a multi-lingual (ML) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the CS (Service) product family and exposes the translatable and non-translatable attributes of service incident severities in a single, language-resolved record set. In Oracle EBS, severity codes classify the impact of a service incident and drive escalation, prioritization, and service-level management behavior. The "_VL" suffix denotes a view that joins the base table (CS_INCIDENT_SEVERITIES_B) with its translation table (CS_INCIDENT_SEVERITIES_TL) and filters the translation rows to the session language through USERENV('LANG'). This design allows applications and reports to retrieve the severity name and description in the user's current language without writing explicit language joins. Because the view is a synonym-backed, read-only projection, it serves as the canonical reference for severity lookups in reporting, integrations, and custom extensions. The view is listed with STATUS = VALID, indicating that it compiles successfully against its base objects in the documented environment.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• CS_INCIDENT_SEVERITIES_B — the base (non-translatable) table holding the primary key INCIDENT_SEVERITY_ID together with operational attributes such as subtype, importance level, color, active dates, seeded flag, defect severity link, DFF attributes, and the OBJECT_VERSION_NUMBER used for optimistic locking.
• CS_INCIDENT_SEVERITIES_TL — the translation table holding LANGUAGE, SOURCE_LANG, NAME, and DESCRIPTION for each severity.

The join condition is B.INCIDENT_SEVERITY_ID = T.INCIDENT_SEVERITY_ID AND T.LANGUAGE = USERENV('LANG'). The view also selects B.ROWID as ROW_ID, which allows row-level identification for downstream processing. Because the filter is applied on the translation side, a row is returned only when a translation exists in the session language; SOURCE_LANG indicates the language in which the source record was originally entered. In 12.2.2 the view text and column set are unchanged from 12.1.1, so queries remain portable across both releases.

Key Columns

• INCIDENT_SEVERITY_ID — primary key uniquely identifying each severity record.
• NAME, DESCRIPTION — language-specific text from the TL table.
• LANGUAGE, SOURCE_LANG — the translated language of the row and the language of the original entry.
• INCIDENT_SUBTYPE — classifies the severity within the service incident model.
• IMPORTANCE_LEVEL — numeric ranking used for ordering or prioritization.
• DISPLAY_COLOR, RGB_COLOR — presentation values used by the UI.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective dating for the severity.
• SEEDED_FLAG — indicates Oracle-seeded (non-deletable) records.
• DEFECT_SEVERITY_ID — links the service severity to a defect severity.
• PRIORITY_CODE — priority association exposed by the view.
• OBJECT_VERSION_NUMBER, audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), ATTRIBUTE1–15, and CONTEXT — standard EBS audit, DFF, and concurrency columns.

Common Use Cases and Queries

Typical scenarios include populating severity LOVs in custom concurrent programs, driving incident aging and escalation reports, and mapping service severities to defect severities for integration. A standard query retrieving the active severities in the current language is:

SELECT incident_severity_id, name, description, importance_level
FROM cs_incident_severities_vl
WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE)
ORDER BY importance_level;

Because the view already resolves USERENV('LANG'), no explicit language predicate is required. For seeded severity reference data, add WHERE seeded_flag = 'Y'. For defect mapping, select INCIDENT_SEVERITY_ID, NAME, and DEFECT_SEVERITY_ID from the same view. All queries should be issued from the APPS schema or through a synonym, and callers should treat the view as read-only, performing DML against the base tables through the supported Service APIs.