Search Results cs_incident_types_vl




Overview
Explore in AI Chat

Overview

The CS_INCIDENT_TYPES_VL view is a multi-lingual (ML) view owned by the APPS schema within the Oracle E-Business Suite Service (CS) product family. It exposes incident type and subtype definitions stored in the underlying base tables, joining the non-translated attributes held in CS_INCIDENT_TYPES_B with the language-specific name and description held in CS_INCIDENT_TYPES_TL. The _VL suffix conventionally denotes a "view with language" — a read-only presentation layer that automatically filters translation rows to the session's current language using USERENV('LANG'), so application code and reports do not need to apply the language predicate manually.

In the context of EBS 12.1.1 and 12.2.2, this view is a key reference object for Service Request (SR) and incident management functionality. It is the standard source from which incident type picklists, service request category lookups, and workflow routing rules are populated. Because it hides the physical split between the base (B) and translation (TL) tables, it is the preferred integration point for reports, concurrent programs, and external interfaces that must present incident type names in the user's language.

Underlying Base Objects

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

  • CS_INCIDENT_TYPES_B — the base table holding language-independent attributes, keyed by INCIDENT_TYPE_ID.
  • CS_INCIDENT_TYPES_TL — the translation table holding NAME, DESCRIPTION, LANGUAGE, and SOURCE_LANG for each language installed.

The view joins the two on INCIDENT_TYPE_ID and restricts rows to T.LANGUAGE = USERENV('LANG'), yielding one translated row per type per active session language. The ROW_ID column is sourced from the base table's ROWID and is exposed for tools that reference rows by physical identifier.

Key Columns

Common Use Cases and Queries

Typical usage includes populating incident type LOVs, driving service request creation, and reporting on configured types. A representative active-types query follows:

SELECT incident_type_id, name, description
FROM   cs_incident_types_vl
WHERE  (start_date_active IS NULL OR start_date_active <= SYSDATE)
AND    (end_date_active   IS NULL OR end_date_active   >= SYSDATE)
ORDER BY name;

To retrieve subtypes for a given parent:

SELECT name, incident_subtype
FROM   cs_incident_types_vl
WHERE  parent_incident_type_id = :p_type_id;

Because the view filters on USERENV('LANG'), callers must run queries from a session whose NLS language is initialized (standard within EBS forms, OAF pages, and concurrent programs). Direct SQL*Plus access outside an EBS session may require setting NLS_LANG consistently to return the expected translation row.