Results for “ieu_uwqm_items_u2”

16 results




Overview
Explore in AI Chat

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

Overview

IEU.IEU_UWQM_ITEMS is the core transaction table of the Universal Work Queue (UWQ) framework in Oracle E-Business Suite, owned by the Interaction Edge (IEU) schema. It stores one row for every work item presented to a user through the work queue infrastructure — the centralized mechanism by which Oracle applications such as TeleService, Service Requests, Collections, and iSupport route actionable tasks to agents, collections specialists, and other end users. Each record represents a discrete, assignable unit of work, carrying the identity of the source object, its owner and assignee, priority, status, and due date, so the queue manager can filter, sort, distribute, and escalate items consistently across heterogeneous source applications.

The object is classified as VALID and is flagged Oracle Internal Use Only; direct DML from custom code is not supported, and access should occur through standard Oracle Applications programs or supported public APIs.

From a Data Vault modeling perspective, the presence of surrogate-key and version columns suggests treating this table as a link (transaction/relationship) entity with satellite attributes — it asserts associations among resources (owners, assignees), source objects, and work sources, rather than functioning as a pure reference hub. This classification is heuristic and should be validated against local modeling standards.

Key Information Stored

The surrogate primary key is WORK_ITEM_ID, enforced by the unique index IEU_UWQM_ITEMS_U1 — the exact index referenced by the search term "ieu_uwqm_items_u1." A second unique index, IEU_UWQM_ITEMS_U2, covers the business-key candidate pair WORKITEM_OBJ_CODE and WORKITEM_PK_ID, which together identify the source object of the work item.

Five non-unique indexes (N1–N4, plus supporting structures) align to query patterns: owner-centric, assignee-centric, source-object, and work-source/status filtering.

Common Use Cases and Queries

Typical scenarios include: displaying an agent's open queue, aging analysis, workload balancing, and integration monitoring. Index IEU_UWQM_ITEMS_N1 (OWNER_TYPE, OWNER_ID, WS_ID, STATUS_ID, PRIORITY_LEVEL, DUE_DATE) supports the classic owner-and-status query:

  • SELECT WORK_ITEM_ID, TITLE, WORK_ITEM_NUMBER, PRIORITY_LEVEL, DUE_DATE FROM IEU.IEU_UWQM_ITEMS WHERE OWNER_ID = :resource_id AND STATUS_ID = 0 ORDER BY PRIORITY_LEVEL, DUE_DATE;
  • Aging report: SELECT WS_ID, COUNT(*) OVER (PARTITION BY WS_ID) FROM IEU.IEU_UWQM_ITEMS WHERE STATUS_ID = 0 AND DUE_DATE < SYSDATE;
  • Source traceability via N3: SELECT * FROM IEU.IEU_UWQM_ITEMS WHERE SOURCE_OBJECT_ID = :id AND SOURCE_OBJECT_TYPE_CODE = :code AND DISTRIBUTION_STATUS_ID = :ds;
  • Workload by assignee via N2: SELECT ASSIGNEE_ID, COUNT(*) FROM IEU.IEU_UWQM_ITEMS WHERE ASSIGNEE_TYPE = :t AND WS_ID = :ws AND STATUS_ID = 0 GROUP BY ASSIGNEE_ID;

Reporting frequently joins IEU_UWQM_WORK_SOURCES_B, JTF_RS_RESOURCE_EXTNS, and HZ_PARTIES to produce queue dashboards. Because the object is internal-use, custom read-only views or BI Publisher extracts should be preferred over direct writes.

Related Objects

  • JTF_OBJECTS_B — joined via WORKITEM_OBJ_CODE; defines the source object type.
  • IEU_UWQM_WORK_SOURCES_B — joined via WS_ID; defines the parent work queue.
  • IEU_UWQM_PRIORITIES_B — joined via PRIORITY_ID; supplies translated priority names.
  • JTF_RS_RESOURCE_EXTNS — joined via OWNER_ID and ASSIGNEE_ID for resource names.
  • HZ_PARTIES — joined via PARTY_ID for customer context.
  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for hosted/multi-org isolation.
  • IEB_WB_WORK_ITEMS — references WORK_ITEM_ID; extends work items into the interaction/Web workbench.
  • PER_COMPETENCE_ELEMENTS — references WORK_ITEM_ID, tying competency records to queue tasks.