Search Results cs_incident_types_rg_v_sec




Overview
Explore in AI Chat

Overview

The CS_INCIDENT_TYPES_RG_V_SEC view is a security-enabled (RLS-filtered) database object owned by the APPS schema within the Oracle E-Business Suite Service (CS) module. Its documented purpose is to return valid service request (incident) types for a List of Values (LOV) on the main Service Request form. The _SEC suffix indicates that this view applies Oracle row-level security policies, ensuring that only those incident types accessible to the currently authenticated user or responsibility are exposed. In practical reporting and integration terms, this view serves as the authoritative source for service request type metadata, including the associated workflow assignments, status grouping, and operational flags such as MAINTENANCE_FLAG and CMRO_FLAG. It is queried at runtime by the Service Request LOV and is equally suitable for downstream reporting, data extraction, and interface development in both Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over three documented base objects within the APPS schema:

  • CS_INCIDENT_TYPES_VL_SEC (VIEW) — the primary security-enabled source supplying the core incident type attributes such as ID, name, subtype, description, parent type, active dates, workflow, weight, task workflow, web workflow, status group, and the maintenance and CMRO flags.
  • CS_WORKFLOW_PKG (PACKAGE) — invoked via GET_WORKFLOW_DISP_NAME to resolve human-readable display names for the task workflow, action or service request workflow, and web workflow columns.
  • CS_SR_UTIL_PKG (PACKAGE) — invoked via GET_RELATED_STATUSES_CNT to compute the count of related statuses associated with each incident type.

By selecting through CS_INCIDENT_TYPES_VL_SEC rather than the base table directly, the view inherits the organization and responsibility-level access restrictions enforced by Oracle row-level security.

Key Columns

  • INCIDENT_TYPE_ID — primary identifier of the service request type.
  • NAME / DESCRIPTION — the type name and descriptive text.
  • INCIDENT_SUBTYPE — indicates the subtype category (e.g., 'ACT'); influences workflow resolution logic.
  • PARENT_INCIDENT_TYPE_ID — references the parent type, supporting hierarchical type structures.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the type.
  • WORKFLOW / TASK_WORKFLOW / WEB_WORKFLOW — internal workflow identifiers, paired with their resolved DISPLAY_NAME, TASK_WORKFLOW_DISPLAY_NAME, and WEB_DISPLAY_NAME columns.
  • WEIGHT — ordering attribute used in LOV presentation.
  • RELATED_STATUSES_CNT — count of statuses linked to the type.
  • STATUS_GROUP_ID — the associated status group.
  • MAINTENANCE_FLAG — indicates whether the service request type is designated for maintenance-related processing. This flag is central to the reported maintenance_flag query.
  • CMRO_FLAG — identifies types configured for CMRO (Configure-to-Order / Maintenance, Repair and Overhaul) scenarios.

Common Use Cases and Queries

Typical uses include populating LOVs, validating service request type assignments in interfaces, and extracting type-to-workflow mappings for reporting. The maintenance_flag column is frequently filtered to isolate maintenance-capable request types.

  • Listing all active maintenance service request types:
    SELECT incident_type_id, name, description, maintenance_flag FROM cs_incident_types_rg_v_sec WHERE maintenance_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
  • Retrieving workflow display names for a given type:
    SELECT name, display_name, task_workflow_display_name, web_display_name FROM cs_incident_types_rg_v_sec WHERE incident_type_id = :p_id;
  • Auditing CMRO-flagged types:
    SELECT name, cmro_flag, status_group_id FROM cs_incident_types_rg_v_sec WHERE cmro_flag = 'Y';

Because row-level security is applied, results reflect only the service request types visible to the connecting responsibility or user.