Search Results task_workflow_display_name




Overview
Explore in AI Chat

Overview

The APPS.CS_INCIDENT_TYPES_RG_V view is a reporting-oriented database view within the Oracle E-Business Suite (EBS) Service / TeleService (CS) module. It exposes incident type (Service Request type) definition data together with several derived display and count attributes that are resolved at query time through PL/SQL packaged functions. Rather than storing denormalized display values, the view computes human-readable workflow labels and counts "on the fly," which makes it a convenient single source for reporting, concurrent programs, OAF/extensibility lookups, and integration extracts that need presentable incident-type metadata.

The view is owned by the APPS schema and is available in both EBS 12.1.1 and 12.2.2. The presence of the TASK_WORKFLOW_DISPLAY_NAME column — which resolves the user-facing name of a task workflow — is directly relevant to the user's search term task_workflow_display_name. This is the specific projection that surfaces the friendly name for the task workflow assigned to an incident type.

Underlying Base Objects

The view is defined over the following documented base objects, all owned by APPS:

Because three of the projected columns are function calls against packaged code, the view is not a simple relational join; each row retrieval triggers the packaged functions for the specific incident type. This has performance implications for large extracts or repeated queries.

Key Columns

  • INCIDENT_TYPE_ID, NAME, DESCRIPTION — Identity and descriptive attributes of the incident type.
  • INCIDENT_SUBTYPE — Distinguishes subtype classification; it also drives the DECODE logic for DISPLAY_NAME.
  • PARENT_INCIDENT_TYPE_ID, START_DATE_ACTIVE, END_DATE_ACTIVE — Hierarchy and date-effective activation controls.
  • WORKFLOW, TASK_WORKFLOW, WEB_WORKFLOW — Internal workflow codes for the main, task, and web flows.
  • TASK_WORKFLOW_DISPLAY_NAME — The display name resolved for the task workflow via CS_WORKFLOW_PKG.GET_WORKFLOW_DISP_NAME('CSTASK', TASK_WORKFLOW). This is the column users search for under the term task_workflow_display_name.
  • DISPLAY_NAME — Display name for the primary workflow; the context code is derived via DECODE(INCIDENT_SUBTYPE,'ACT','SRACTION','SERVEREQ').
  • WEB_DISPLAY_NAME — Display name for the web workflow (context SERVEREQ).
  • RELATED_STATUSES_CNT — Count of statuses associated with the type, computed by CS_SR_UTIL_PKG.GET_RELATED_STATUSES_CNT.
  • STATUS_GROUP_ID, MAINTENANCE_FLAG, CMRO_FLAG — Status grouping and maintenance/CMRO indicators.

Common Use Cases and Queries

Typical scenarios include reporting on configured incident types, validating task workflow assignments, and populating LOVs in custom extensions.

  • Listing types with their task workflow display names (the searched term):
SELECT INCIDENT_TYPE_ID, NAME, TASK_WORKFLOW, TASK_WORKFLOW_DISPLAY_NAME
FROM   APPS.CS_INCIDENT_TYPES_RG_V
WHERE  END_DATE_ACTIVE IS NULL
ORDER BY NAME;
  • Auditing all three workflow display names and status counts:
SELECT INCIDENT_TYPE_ID, NAME, DISPLAY_NAME,
       TASK_WORKFLOW_DISPLAY_NAME, WEB_DISPLAY_NAME, RELATED_STATUSES_CNT
FROM   APPS.CS_INCIDENT_TYPES_RG_V;
  • Identifying maintenance or CMRO-related types for operational reports:
SELECT INCIDENT_TYPE_ID, NAME, TASK_WORKFLOW_DISPLAY_NAME
FROM   APPS.CS_INCIDENT_TYPES_RG_V
WHERE  MAINTENANCE_FLAG = 'Y' OR CMRO_FLAG = 'Y';

Because workflow display resolution is invoked per row, queries should be bounded by selective predicates (for example, by INCIDENT_TYPE_ID or active dates) rather than applied to the full set indiscriminately.