Results for “ieu_uwq_task_to_ref_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IEU_UWQ_TASK_TO_REF_V view is an Oracle E-Business Suite database object owned by the APPS schema and registered as VALID in the ETRM catalog for releases 12.1.1 and 12.2.2. It belongs to the IEU product family — Universal Work Queue — which provides the unified task-routing and assignment infrastructure used by CRM modules such as TeleSales, Service, and Collections. The view is documented as a Refresh View for team owned tasks, meaning it projects the subset of task records that have been assigned to a team (resource group) rather than to an individual resource, and it exists primarily to support the refresh and reassignment logic within the work queue engine.

Because it exposes a simplified, filtered projection of the base task table with renamed owner attributes, it is useful as a reporting and integration surface. External applications, custom dashboards, and interface programs can consume it to retrieve currently open team-owned tasks without traversing the full JTF_TASKS_B table or re-implementing the team-ownership filter. The user search term task_type_id maps directly to a column exposed by this view, indicating that the object is commonly queried when segmenting work queue tasks by task type.

Underlying Base Objects

The view is defined exclusively over the synonym JTF_TASKS_B, the foundational task entity table in the Oracle CRM task model. JTF_TASKS_B stores all task records regardless of source application, including tasks created by TeleSales, Service Requests, and territory-based routing. The view applies four documented predicates against that table:

• NVL(TASKS.DELETED_FLAG, 'N') <> 'Y' — excludes soft-deleted tasks.
• TASKS.ENTITY = 'TASK' — restricts to records whose entity discriminator is a task.
• TASKS.OPEN_FLAG = 'Y' — restricts to tasks that remain open.
• TASKS.OWNER_TYPE_CODE = 'RS_TEAM' — restricts to tasks owned by a team (resource team), which is the defining characteristic of the refresh set.

No joins to secondary tables are present; the view is a single-table filtered projection, which makes it inexpensive to query and straightforward to reason about in integration design.

Key Columns

The documented column list comprises six attributes:

• TASK_ID — primary identifier of the task, sourced from JTF_TASKS_B.TASK_ID. Used for joins to task detail and history tables.
• TASK_NUMBER — the user-visible task number, useful for display and reference in reporting.
• TASK_STATUS_ID — foreign key to the task status lookup, indicating the workflow state of the task.
• TASK_TYPE_ID — foreign key identifying the task type; the attribute most frequently used to categorize and filter work queue tasks.
• RESOURCE_ID — an alias of TASKS.OWNER_ID, exposing the owning team as a resource identifier. Note that the underlying owner type remains RS_TEAM.
• OWNER_ID — the raw owner identifier, retained so that consumers can reference the team by its native owner value as well as via the RESOURCE_ID alias.

The duplication of the owner into both RESOURCE_ID and OWNER_ID is intentional: it allows the work queue refresh logic to treat team-owned tasks as resources in the standard assignment model while preserving the original ownership key.

Common Use Cases and Queries

The primary use case is the Universal Work Queue refresh process, which reassigns or re-evaluates tasks held by a team so that they can be redistributed to individual resources. Reporting scenarios include open-task dashboards by team, backlog analysis per task type, and workload balancing across resource teams.

A representative query retrieving open team-owned tasks by type is:

SELECT task_id, task_number, task_status_id, task_type_id, resource_id
FROM   apps.ieu_uwq_task_to_ref_v
WHERE  task_type_id = :p_task_type_id
ORDER  BY task_number;

To count the open team backlog grouped by task type:

SELECT t.task_type_id, COUNT(*) open_cnt
FROM   apps.ieu_uwq_task_to_ref_v t
GROUP  BY t.task_type_id;

Because the view filters to OPEN_FLAG = 'Y' and excludes deleted rows, queries against it never require additional status hygiene. Consumers needing closed or deleted task history must query JTF_TASKS_B directly instead.