Results for “planned_start_date”

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

Overview

The APPS.IEU_UWQ_TASKS_IA_V view is a reporting and integration component of the Oracle E-Business Suite Universal Work Queue (IEU) module. Its documented description states that it "contains details of Individual Assigned tasks," meaning it exposes task records that have been routed to (assigned to) a specific resource — a user, group, or other assignee — rather than the full population of tasks. In the Universal Work Queue, IEU surfaces work items from multiple sources into a single agent-facing queue; assignments determine which item appears for which agent. This view is the query-friendly projection of that assignment relationship.

The view is owned by the APPS schema and carries a VALID status on both Oracle EBS 12.1.1 and 12.2.2. It is typically consumed as a data source for UWQ region definitions, custom dashboards, workflows, and third-party integrations that need to render a row-per-assignment task list with localized display values.

Underlying Base Objects

The view is defined over eleven referenced objects, nearly all of which are synonyms resolving to the JTF (Java Task Framework) and HZ (Trading Community/Receivables) table families:

• JTF_TASKS_B / JTF_TASKS_TL — the task base table and its translation table; supply task identity, numbering, dates, status, priority, duration, and source object linkage. JTF_TASKS_B is the driving table.
• JTF_TASK_ALL_ASSIGNMENTS — the assignment table; joins on TASK_ID to yield RESOURCE_ID and RESOURCE_TYPE_CODE, which is the defining characteristic of this "Individual Assigned" view.
• JTF_TASK_STATUSES_B / JTF_TASK_STATUSES_TL — status code and its translated display name.
• JTF_TASK_TYPES_TL and JTF_TASK_PRIORITIES_TL — translated task type and priority names (priority joined with the outer-join (+) operator so a null priority does not drop the row).
• JTF_OBJECTS_B / JTF_OBJECTS_TL — resolve the source object type code into functional metadata, translation name, and the IEU_OBJECT_FUNCTION / IEU_OBJECT_PARAMETERS used by UWQ navigation.
• HZ_TIMEZONES — provides GLOBAL_TIMEZONE_NAME and GMT_DEVIATION_HOURS for date normalization.
• JTF_TASK_UTL — a package supplying the GET_OWNER and GET_CUSTOMER_NAME functions used to resolve owner and customer display values.

Key Columns

The projection renames several columns to IEU-prefixed names to satisfy UWQ's expected interface. Notable columns include IEU_OBJECT_FUNCTION and IEU_OBJECT_PARAMETERS (from JTF_OBJECTS_B) which drive the drill-down action in the work queue; IEU_PARAM_PK_COL and IEU_PARAM_PK_VALUE, which expose the primary key of the source object as a parameter pair; and IEU_ACTION_OBJECT_CODE, which mirrors SOURCE_OBJECT_TYPE_CODE. TASK_ID, TASK_NUMBER, TASK_NAME, DESCRIPTION, TASK_TYPE, TASK_STATUS, and TASK_PRIORITY identify and describe the work item. RESOURCE_ID and RESOURCE_TYPE (from the assignment join) identify the assigned party, while OWNER and CUSTOMER_NAME are derived values computed through JTF_TASK_UTL. Scheduling columns — PLANNED, SCHEDULED, and ACTUAL start/end dates alongside DURATION, DURATION_UOM, and timezone columns — support queue prioritization and SLA monitoring. OBJECT_VERSION_NUMBER enables optimistic-locking update flows.

Common Use Cases and Queries

The view is most often queried to populate a work queue listing for a given resource, or to audit outstanding assignments. A representative query:

• SELECT TASK_ID, TASK_NUMBER, TASK_NAME, TASK_STATUS, TASK_PRIORITY, OWNER, CUSTOMER_NAME, PLANNED_END_DATE FROM APPS.IEU_UWQ_TASKS_IA_V WHERE RESOURCE_ID = :resource_id ORDER BY PLANNED_END_DATE;
• Filtering by TASK_STATUS and RESOURCE_TYPE to build agent-scoped or team-scoped queue regions.
• Joining on IEU_PARAM_PK_VALUE or SOURCE_OBJECT_ID to reconcile queue items with their originating source documents (for example, service requests or orders).
• Joining on GLOBAL_TIMEZONE_NAME and GMT_DEVIATION_HOURS to present due dates in the agent's local time.

Because the view encapsulates the complex multi-table joins, translated lookups, and derived function calls, custom reporting should select from IEU_UWQ_TASKS_IA_V rather than re-implementing the underlying JTF joins.