Results for “ieu_uwq_task_ia_ref_v”

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

Overview

IEU_UWQ_TASK_IA_REF_V is a database view owned by the APPS schema within the IEU – Universal Work Queue product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as the refresh view for Individual Assigned tasks, a workload category used by the Universal Work Queue framework to present agent-facing task queues. In practical terms, the view materializes the set of tasks that have been assigned directly to an individual resource — as opposed to group or team queues — and that are still open and active. Because it filters aggressively on assignment semantics, it gives downstream consumers a pre-qualified list of "my tasks" rows without requiring each consumer to re-encode the assignment and status logic. It is typically referenced by UWQ refresh processing and by custom reporting or integration components that need to reconcile or extract the same task population the work queue surfaces to agents.

Underlying Base Objects

The view is defined over two documented synonym objects owned by APPS: JTF_TASKS_B and JTF_TASK_ALL_ASSIGNMENTS. JTF_TASKS_B holds the task header records, including identity, type, status, entity classification, deletion and open flags. JTF_TASK_ALL_ASSIGNMENTS holds the assignment rows linking tasks to resources, together with the assignee role and resource type. The two are joined on TASK_ID. A third object, JTF_TASK_STATUSES_B, is listed in the ETRM metadata as referenced, though it does not appear in the documented view text; it is the lookup underlying TASK_STATUS_ID. The join and the filter predicates together reduce the much larger assignment universe to one row per qualifying task/resource pairing.

Key Columns

• TASK_ID — Primary identifier of the task, inherited from JTF_TASKS_B; the join key to assignment rows.
• TASK_NUMBER — Externally recognizable task number, useful for user-facing reports and cross-referencing.
• TASK_STATUS_ID — Foreign key to JTF_TASK_STATUSES_B, indicating the current lifecycle status of the task.
• TASK_TYPE_ID — Identifier of the task type, which drives categorization and often routing behavior.
• RESOURCE_ID — Identifier of the assignee resource for whom the task qualifies as an individual assignment.
• RESOURCE_TYPE — Type code of that resource, derived from ASG.RESOURCE_TYPE_CODE.

The result set is constrained so that TASKS.ENTITY = 'TASK', TASKS.OPEN_FLAG = 'Y', and the deleted flag is neither 'Y' nor null. On the assignment side, the assignee role defaults to 'ASSIGNEE' when null, and resources typed as 'RS_GROUP' or 'RS_TEAM' are excluded. The net effect is that only genuinely individual, open, non-deleted assignments appear.

Common Use Cases and Queries

Typical uses include validating which tasks a given agent should see in a UWQ queue, reconciling queue contents against JTF_TASKS_B, and feeding external dashboards. The view is especially convenient when a query would otherwise need to repeat the assignee-role and resource-type exclusions. A representative query lists open individually assigned tasks for a specific resource:

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

A second pattern audits assignment counts by resource type:

SELECT resource_type, COUNT(*) task_count
FROM apps.ieu_uwq_task_ia_ref_v
GROUP BY resource_type;

Because the view already excludes group and team assignments, COUNT(*) yields individual assignment volume without additional filtering. Joins to JTF_TASK_STATUSES_B on TASK_STATUS_ID, or to task-type lookups on TASK_TYPE_ID, are commonly added for descriptive reporting.