Results for “owner_type_actual”

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

Overview

The IEU.IEU_UWQM_ITEMS table is a core transactional object within the IEU – Universal Work Queue (UWQ) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It is described in ETRM documentation as the "UWQ Metaphor items table," meaning it stores the individual work items surfaced to agents through the various UWQ user interface metaphors (such as the task list, worklist, or dashboard tiles). Each row represents a discrete unit of assignable work — a task, lead, opportunity follow-up, service request, or similar agent-facing activity — together with its owner, assignee, priority, status, and due date. The table therefore acts as the central operational backbone of the agent's work queue, enabling routing, prioritisation, assignment, and status tracking across heterogeneous source applications.

The heuristic Data Vault classification mined from the foreign-key structure is link. This is appropriate because IEU_UWQM_ITEMS associates several independent entities — the work item's originating object, an owning resource, an assignee resource, an owning party, and a work source — rather than being a pure descriptive satellite or a standalone hub.

Key Information Stored

The table contains 31 documented columns. The most important are:

• WORK_ITEM_ID — the surrogate primary key, enforced by IEU_UWQM_ITEMS_PK and reinforced by the unique index IEU_UWQM_ITEMS_U1.
• WORKITEM_OBJ_CODE and WORKITEM_PK_ID — together the documented business-key candidate (IEU_UWQM_ITEMS_U2), identifying the source object code and its primary key.
• WORK_ITEM_NUMBER — the user-facing work item reference.
• STATUS_ID and DISTRIBUTION_STATUS_ID — the current lifecycle and routing state.
• PRIORITY_ID and PRIORITY_LEVEL — priority assignment and calculated ranking.
• OWNER_ID / OWNER_TYPE and ASSIGNEE_ID / ASSIGNEE_TYPE — resource assignment, with ACTUAL variants recording resolved values.
• PARTY_ID — the customer or trading partner associated with the item.
• DUE_DATE and RESCHEDULE_TIME — scheduling and SLA tracking.
• WS_ID — the originating work source.
• Standard EBS audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and SECURITY_GROUP_ID.

Common Use Cases and Queries

Reporting on UWQ typically filters work items by assignee, status, and due date. For example, to list open items for a specific resource:

• SELECT WORK_ITEM_ID, TITLE, DUE_DATE, PRIORITY_LEVEL FROM IEU.UWQM_ITEMS WHERE ASSIGNEE_ID = :resource_id AND STATUS_ID = :open_status ORDER BY DUE_DATE;
• To reproduce the business key lookup: SELECT WORK_ITEM_ID FROM IEU.UWQM_ITEMS WHERE WORKITEM_OBJ_CODE = :obj AND WORKITEM_PK_ID = :pkid;

Other common scenarios include workload balancing (grouping by ASSIGNEE_ID), overdue item alerts (DUE_DATE < SYSDATE), and tracing a work item back to its source object through WORKITEM_OBJ_CODE and WORKITEM_PK_ID.

Related Objects

The documented foreign keys identify the primary related objects:

• JTF_RS_RESOURCE_EXTNS — referenced via ASSIGNEE_ID and OWNER_ID; the object returned when searching for jtf_rs_resource_extns, representing the resource (agent) dimension.
• JTF_OBJECTS_B — via WORKITEM_OBJ_CODE, defining the source object registry.
• IEU_UWQM_PRIORITIES_B — via PRIORITY_ID.
• HZ_PARTIES — via PARTY_ID.
• FND_SECURITY_GROUPS — via SECURITY_GROUP_ID, supporting multi-org data security.
• IEU_UWQM_WORK_SOURCES_B — via WS_ID.
• PER_COMPETENCE_ELEMENTS and IEB_WB_WORK_ITEMS — dependent tables that reference WORK_ITEM_ID.