Search Results cs_incident_statuses_vl




Overview
Explore in AI Chat

Overview

CS_INCIDENT_STATUSES_VL is a multi-lingual (ML) view owned by the APPS schema in Oracle E-Business Suite, belonging to the Service (CS) product family. It presents the translatable and non-translatable attributes of service request incident statuses in a single, language-resolved record set. The view is the standard query interface for incident status setup data, exposing status codes, display colors, active date ranges, seeded flags, and a comprehensive set of behavioral control flags that govern interaction rules on service requests. Because it resolves the user's session language automatically, it is the appropriate object for forms, concurrent programs, OAF pages, and custom reporting or integration logic that must display status names and descriptions in the runtime language of the user. The underlying base objects are registered as the internal tables CS_INCIDENT_STATUSES_B and CS_INCIDENT_STATUSES_TL, and the object holds a VALID status in the EBS data dictionary for both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over two documented base objects, referenced through synonyms: CS_INCIDENT_STATUSES_B, which stores the language-independent (base) attributes of each incident status, and CS_INCIDENT_STATUSES_TL, which stores the translated NAME and DESCRIPTION values keyed by language. The join is performed on INCIDENT_STATUS_ID, and the translation row is filtered by the condition T.LANGUAGE = USERENV('LANG'), so each query returns exactly one translation row per status, matching the session language. The B table contributes identity, audit, and configuration columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The TL table contributes LANGUAGE, SOURCE_LANG, NAME, and DESCRIPTION. Because this is a view and not a table, DML against it is routed through the underlying tables and is normally performed by the application's own forms or APIs rather than by direct SQL.

Key Columns

Common Use Cases and Queries

Typical uses include validating whether a status permits creation, listing active statuses for a picklist, joining status names onto incident reporting queries, and auditing the seeded versus custom status configuration. All queries should filter on the active date range and, where relevant, on the seeded or class-code flags.

  • List all active statuses in the user's language:
SELECT incident_status_id, status_code, name, display_color
  FROM cs_incident_statuses_vl
 WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
                         AND NVL(end_date_active, SYSDATE)
 ORDER BY sort_order;
  • Identify statuses valid at creation time:
SELECT incident_status_id, status_code, name
  FROM cs_incident_statuses_vl
 WHERE valid_in_create_flag = 'Y'
   AND NVL(close_flag, 'N') = 'N'
 ORDER BY sort_order;
  • Report on operational restrictions imposed by each status:
SELECT status_code, name, disallow_new_action,
       disallow_agent_dispatch, disallow_rma
  FROM cs_incident_statuses_vl
 WHERE seeded_flag = 'N';

Because the view resolves language through USERENV('LANG'), the same SQL executed in a different session language returns the corresponding translated NAME and DESCRIPTION, making it well suited to multi-lingual reporting and integration interfaces.