Search Results cs_incident_types_rg_v




Overview
Explore in AI Chat

Overview

CS_INCIDENT_TYPES_RG_V is a PL/SQL view owned by the APPS schema within the Oracle E-Business Suite Service (CS) module. Its documented purpose is to return service request types for a list of values (LOV) on the main service request form. In practice, this view serves as the data source that populates the incident type selector presented to users when creating or updating a service request, filtering and formatting the underlying type definitions so that the LOV displays meaningful, workflow-aware descriptions rather than raw identifiers.

Beyond its role in the concurrent form UI, the view is a useful reporting and integration artifact. Because it resolves workflow display names and related-status counts at query time, it enables reporting layers, custom forms, and external interfaces to present service request types with human-readable context without re-implementing the same lookup logic. The view is marked VALID in the documented metadata, confirming that it compiles successfully against its dependencies in both EBS 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The view is defined over three documented referenced objects:

  • CS_INCIDENT_TYPES_VL (VIEW) — the primary source. This is the multi-language view that supplies the base incident type rows, including identifiers, names, subtypes, dates, and workflow references. The RG view layers additional derived columns on top of it.
  • CS_SR_UTIL_PKG (PACKAGE) — used through the function GET_RELATED_STATUSES_CNT to compute the number of related statuses for each incident type.
  • CS_WORKFLOW_PKG (PACKAGE) — used through GET_WORKFLOW_DISP_NAME to translate workflow internal names into display names for the task, service request, and web workflows.

The SELECT statement references CS_INCIDENT_TYPES_VL as the driving row source and joins no additional tables directly; the package functions are invoked per row, so the view is functionally dependent on both packages being valid and accessible in the APPS schema.

Key Columns

The view exposes eighteen columns. The most significant include:

Common Use Cases and Queries

Typical uses include validating service request type availability for integrations, reporting on which types are active, and building custom LOVs. A simple reporting query follows:

  • SELECT incident_type_id, name, display_name, related_statuses_cnt FROM apps.cs_incident_types_rg_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

To list only types that currently have related statuses:

  • SELECT incident_type_id, name, related_statuses_cnt FROM apps.cs_incident_types_rg_v WHERE related_statuses_cnt > 0;

Because the view calls package functions per row, queries over large result sets should be filtered on active dates or identifiers before invoking the display-name logic, and callers should ensure CS_WORKFLOW_PKG and CS_SR_UTIL_PKG are valid to avoid runtime errors.