Search Results refs_b

Overview

APPS.JTF_ESC_UWQ_V is a reporting view in the Oracle E-Business Suite CRM Task Manager (JTF) schema. Its name indicates its purpose: it exposes the escalation "Universal Work Queue" (UWQ) records for tasks. In release 12.1.1 and 12.2.2, the Universal Work Queue is the framework that routes work items — including escalations — to the appropriate resource or agent. This view flattens the join between the task, its status, its escalation level, its owner, and any associated reference document into a single queryable rowset suitable for reporting and integration.

The view is deliberately filtered. It selects only tasks whose task_type_id = 22 (the escalation task type), excludes deleted, closed, cancelled, completed, and rejected tasks, and restricts references to those with reference_code = 'ESC'. In practice, therefore, the view presents the population of currently open escalations and their linkage to the document or object that triggered them.

Underlying Base Objects

The view is defined over the following documented base objects:

• JTF_TASKS_B / JTF_TASKS_TL — the task header and its translated description.
• JTF_TASK_STATUSES_B / JTF_TASK_STATUSES_TL — status codes and their translated names.
• JTF_TASK_REFERENCES_B — the alias refs_b in the view text, supplying the referenced document (object number and ID). This is the object the user's search term "refs_b" points to.
• JTF_OBJECTS_B / JTF_OBJECTS_TL — the object registry, providing the object code, translated name, parameters, and function.
• FND_LOOKUPS — the lookup view supplying the escalation level meaning from lookup type JTF_TASK_ESC_LEVEL.
• JTF_TASK_UTL, JTF_EC_UTIL, FND_GLOBAL — PL/SQL packages invoked in the select list to resolve owner, customer name, requester, and session language.

The joins to refs_b and o are outer joins ((+)), so a task without an associated reference or object is still returned.

Key Columns

• TASK_ID, TASK_NUMBER — primary key and user-facing task identifier.
• DESCRIPTION, TASK_STATUS — translated task text and status name.
• ACTUAL_START_DATE, PLANNED_END_DATE, ACTUAL_END_DATE — task scheduling timestamps.
• OWNER_TYPE_CODE, OWNER_ID, OWNER, CUSTOMER_NAME — the party responsible for the escalation.
• ESCALATION_LEVEL, ESCALATION_LEVEL_NAME — numeric escalation level and its lookup meaning.
• RESOURCE_ID, RESOURCE_TYPE — the resource to which the escalation is routed.
• REF_DOC_NUMBER, REF_DOC_ID — the referenced document, sourced from refs_b.
• OBJECT_CODE, NAME, OBJECT_PARAMETERS, OBJECT_FUNCTION — the registered object metadata describing what the escalation refers to.

Common Use Cases and Queries

Typical uses include escalation dashboards, workload analysis by owner or resource, and integration feeds into external workflow or notification engines. A representative query lists open escalations with their level and owner:

• SELECT task_number, description, task_status, escalation_level_name, owner, customer_name FROM apps.jtf_esc_uwq_v ORDER BY actual_start_date DESC;
• SELECT owner, COUNT(*) FROM apps.jtf_esc_uwq_v GROUP BY owner;
• SELECT task_number, ref_doc_number, object_code FROM apps.jtf_esc_uwq_v WHERE ref_doc_number IS NOT NULL;

Because the view filters by USERENV('lang') for translated columns, results are returned in the session language. Reports should therefore set the language consistently where multilingual output is required.