Search Results incident_resolved_date




Overview
Explore in AI Chat

Overview

The CS_INCIDENTS_VL_SEC view is a multi-lingual, security-enabled (VL_SEC) reporting object owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It resides in the Service (CS) product family and provides a consolidated, translated, and row-level-secured window into service incident (service request) data. The "VL" designation indicates that the view joins a translatable base entity with its translation table to expose both the base columns and the language-dependent descriptive columns (such as SUMMARY) in a single logical record. The "_SEC" suffix indicates that the underlying base view applies Oracle EBS security predicates, typically MOAC (Multi-Org Access Control) and/or security profile–driven filtering, so that a query returns only the incidents the querying user is authorized to see.

This view is the recommended access layer for custom reports, Discoverer workbooks, OA Framework extensions, and integration extracts that need incident header data without directly joining the base and translation tables. Because it is a view over a secured view, it preserves organizational and functional security while adding language context.

Underlying Base Objects

Two documented objects underpin this view:

  • CS_INCIDENTS_ALL_TL (SYNONYM) — the translation table holding language-specific incident attributes. It supplies the LANGUAGE, SOURCE_LANG, and SUMMARY columns.
  • CS_INCIDENTS_B_SEC (VIEW) — the secured "B" (base) view carrying all non-translated incident columns, aliased as B in the definition.

The view text joins CS_INCIDENTS_B_SEC (B) to CS_INCIDENTS_ALL_TL (TL) on INCIDENT_ID, producing one row per incident per translation language. The security predicates are inherited from the B_SEC view, so no additional filtering logic is required by the caller. Referenced documentation notes the parent view as CS_INCIDENTS_ALL_B_SEC_V, confirming the security-enabled base lineage.

Key Columns

The view exposes the full incident header plus translation columns. Notable columns include:

Common Use Cases and Queries

Typical uses include building service request dashboards, extracting incident data for data warehouses, and joining incidents to order or depot workflows. A representative query retrieving incidents for the current user context, filtered by ship-to and language, follows:

  • SELECT v.incident_id, v.incident_number, v.summary, v.ship_to_site_use_id, v.customer_id, v.org_id FROM apps.cs_incidents_vl_sec v WHERE v.language = USERENV('LANG') AND v.org_id = :p_org_id AND v.ship_to_site_use_id IS NOT NULL ORDER BY v.incident_date DESC;
  • To resolve the ship-to account for a site use: join ship_to_site_use_id to RA_SITE_USES_ALL / HZ_CUST_ACCT_SITES_ALL to obtain the owning customer account, since the view exposes the site use ID rather than the account ID directly.

Because security is embedded in the VIEW, callers should not add redundant org filters from the base tables, and should always constrain LANGUAGE to avoid duplicate rows from multiple translations.