Search Results display_color




Overview
Explore in AI Chat

Overview

The CS_INCIDENT_URGENCIES_VL view is a multi-lingual (ML) view owned by the APPS schema in Oracle E-Business Suite, belonging to the Service (CS) product family. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view presents incident urgency definitions — the configurable severity classifications used to prioritize service requests and incidents — in the session's language. Urgencies drive escalation logic, response-time calculations, and service-level agreements within Oracle Service, and are surfaced broadly in Service Request forms and related reporting.

Because it joins a language-independent base table with a translation table and filters on the runtime language, the view behaves as the queryable, report-friendly representation of urgency setup data. It is the object that forms, concurrent programs, and integrations should reference when they require the name and description of an urgency in the user's current language, rather than querying the underlying tables directly.

Underlying Base Objects

The view is defined over two documented base objects, exposed in APPS through synonyms:

The two tables are joined on INCIDENT_URGENCY_ID. The WHERE clause restricts the translation row to the current session language via T.LANGUAGE = USERENV('LANG'). This is the standard Oracle EBS ML view pattern: a _B (base) table supplies non-translated columns, and a _TL (translation) table supplies language-specific text, with the _VL view presenting a single joined, language-filtered result set. All columns from the base table are exposed, plus LANGUAGE, SOURCE_LANG, NAME, and DESCRIPTION from the translation table.

Key Columns

  • INCIDENT_URGENCY_ID — primary identifier of the urgency; the join key between base and translation rows.
  • NAME and DESCRIPTION — the translated, user-facing urgency name and description, sourced from the _TL table for the current language.
  • LANGUAGE, SOURCE_LANG — the language of the returned translation row and the source language from which it was created; LANGUAGE is constrained to USERENV('LANG').
  • IMPORTANCE_LEVEL — numeric ranking that determines relative urgency priority for escalation and response-time processing.
  • DISPLAY_COLOR and RGB_COLOR — presentation attributes used to render the urgency in the UI.
  • START_DATE_ACTIVE, END_DATE_ACTIVE — effective-dating columns controlling whether the urgency is currently usable.
  • SEEDED_FLAG — indicates whether the row is Oracle-seeded or customer-defined.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — audit and concurrency-control columns.
  • ATTRIBUTE1–ATTRIBUTE15, CONTEXT — the DFF (descriptive flexfield) columns for customer-defined extensions.
  • ROW_ID — the base table rowid, exposed for compatibility with framework code.

Common Use Cases and Queries

Typical scenarios include building custom urgency lookups for incident forms, extracting urgency reference data for integrations, and validating active urgency setups. The following query returns all usable, currently-active urgencies:

  • List active urgencies with their importance ranking:

SELECT incident_urgency_id, name, importance_level
FROM cs_incident_urgencies_vl
WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
AND NVL(end_date_active, SYSDATE)
ORDER BY importance_level;

  • Join urgency names to incidents for reporting by severity.
  • Retrieve seeded versus user-defined urgencies using SEEDED_FLAG.

Because the view automatically filters translations to the session language, no additional language predicate is required. When translation text is missing for a language, the row will not appear, so integrations must account for gaps between language setup and available translations.

  • View: CS_INCIDENT_URGENCIES_VL 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:CS.CS_INCIDENT_URGENCIES_VL,  object_name:CS_INCIDENT_URGENCIES_VL,  status:VALID,  product: CS - Service ,  description: Multi-lingual view for CS_INCIDENT_URGENCIES_B and CS_INCIDENT_URGENCIES_TL tables. Refer to Base Tables for details. ,  implementation_dba_data: APPS.CS_INCIDENT_URGENCIES_VL , 

  • View: CS_INCIDENT_URGENCIES_VL 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:CS.CS_INCIDENT_URGENCIES_VL,  object_name:CS_INCIDENT_URGENCIES_VL,  status:VALID,  product: CS - Service ,  description: Multi-lingual view for CS_INCIDENT_URGENCIES_B and CS_INCIDENT_URGENCIES_TL tables. Refer to Base Tables for details. ,  implementation_dba_data: APPS.CS_INCIDENT_URGENCIES_VL , 

  • View: CS_INCIDENT_SEVERITIES_VL 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:CS.CS_INCIDENT_SEVERITIES_VL,  object_name:CS_INCIDENT_SEVERITIES_VL,  status:VALID,  product: CS - Service ,  description: Multi-lingual view for CS_INCIDENT_SEVERITIES_B and CS_INCIDENT_SEVERITIES_TL tables. ,  implementation_dba_data: APPS.CS_INCIDENT_SEVERITIES_VL , 

  • View: CS_INCIDENT_SEVERITIES_VL 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:CS.CS_INCIDENT_SEVERITIES_VL,  object_name:CS_INCIDENT_SEVERITIES_VL,  status:VALID,  product: CS - Service ,  description: Multi-lingual view for CS_INCIDENT_SEVERITIES_B and CS_INCIDENT_SEVERITIES_TL tables. ,  implementation_dba_data: APPS.CS_INCIDENT_SEVERITIES_VL , 

  • View: CS_INCIDENT_STATUSES_VL 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:CS.CS_INCIDENT_STATUSES_VL,  object_name:CS_INCIDENT_STATUSES_VL,  status:VALID,  product: CS - Service ,  description: Multi-lingual view for CS_INCIDENT_STATUSES_B and CS_INCIDENT_STATUSES_TL tables. ,  implementation_dba_data: APPS.CS_INCIDENT_STATUSES_VL , 

  • View: CS_INCIDENT_STATUSES_VL 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:CS.CS_INCIDENT_STATUSES_VL,  object_name:CS_INCIDENT_STATUSES_VL,  status:VALID,  product: CS - Service ,  description: Multi-lingual view for CS_INCIDENT_STATUSES_B and CS_INCIDENT_STATUSES_TL tables. ,  implementation_dba_data: APPS.CS_INCIDENT_STATUSES_VL ,