Search Results workflow_process_id




Overview
Explore in AI Chat

Overview

CSF_ESC_TASKS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It is delivered as part of the CSF – Field Service product family and presents field service escalated tasks in a denormalized, reporting-friendly form. Escalated tasks in EBS originate in the JTF task framework, where a task raised against a service request, customer, or territory reaches a designated escalation level. Rather than requiring report developers, integrators, and support analysts to join the underlying task tables manually, CSF_ESC_TASKS_V consolidates the task header, its translated descriptive attributes, the current status name, escalation level, task reason, and the source service object reference into one projection.

The view carries a status of VALID in the APPS schema and is intended primarily for inquiry, reporting, and integration scenarios rather than for direct DML. A notable column of interest to users searching this object with the term "private_flag" is T.PRIVATE_FLAG, exposed verbatim from the base task table. This flag indicates whether a task is private to its owner (typically visible only to the owning resource), which is a common filter in escalated-task reports so that private assignments are excluded from shared operational dashboards. The same applies to PUBLISH_FLAG, which governs whether the task is publishable to a broader audience.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects: FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), JTF_TASKS_B (SYNONYM), JTF_TASKS_TL (SYNONYM), JTF_TASK_REFERENCES_B (SYNONYM), JTF_TASK_STATUSES_B (SYNONYM), and JTF_TASK_STATUSES_TL (SYNONYM). These map directly to the view's SELECT text:

  • JTF_TASKS_B / JTF_TASKS_TL — the primary task entity and its translatable name/description columns (TASK_NAME, DESCRIPTION).
  • JTF_TASK_STATUSES_B / JTF_TASK_STATUSES_TL — supply the status identifier and the language-resolved STATUS_NAME scalar subquery.
  • JTF_TASK_REFERENCES_B — provides R.OBJECT_ID, the linkage to the source service object the escalated task applies to.
  • FND_LOOKUPS — resolves the ESC_LEVEL_NAME (lookup type JTF_TASK_ESC_LEVEL) and REASON_NAME (lookup type JTF_TASK_REASON_CODES).
  • FND_GLOBAL — supplies the session context (implicitly, via USERENV('LANG') for language resolution and user identity used by the task framework).

Because the view references JTF_TASKS_TL and JTF_TASK_STATUSES_TL with a LANGUAGE = USERENV('LANG') predicate, output is automatically localized to the session's language preference.

Key Columns

Common Use Cases and Queries

Typical uses include service-management dashboards listing open escalated tasks by escalation level, exception reports filtering out private tasks, and integration extracts that publish escalated tasks to external systems. A representative query excluding private tasks is:

SELECT task_number, task_name, status_name, esc_level_name, owner_id
  FROM apps.csf_esc_tasks_v
 WHERE private_flag = 'N'
   AND closed_flag = 'N'
   AND escalation_level IS NOT NULL
 ORDER BY creation_date DESC;

Analysts often group by escalation level or reason to identify recurring drivers:

SELECT esc_level_name, reason_name, COUNT(*) escalated_count
  FROM apps.csf_esc_tasks_v
 WHERE deleted_flag = 'N'
 GROUP BY esc_level_name, reason_name
 ORDER BY escalated_count DESC;

In all cases the view should be queried read-only and, where possible, joined to ownership or customer tables for full operational context.