Results for “ieu_uwqm_items_gtt”

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

Overview

IEU_UWQM_ITEMS_GTT is an Oracle Application Object Library (FND) table residing in the APPS schema. The _GTT suffix indicates it is a Global Temporary Table, meaning its rows are session- or transaction-scoped and are retained only for the duration of a session or transaction, or until explicitly purged. Functionally, it serves as a staging and worklist buffer within the Universal Work Queue (UWQ) and Interaction/Event Utility (IEU) framework, temporarily holding work items that are routed, prioritized, distributed, and dispatched to assignees such as agents, resources, or queues.

From a heuristic Data Vault modeling perspective, and based on the mined foreign key structure, this object is best classified as a standalone staging structure rather than a conformed hub, link, or satellite. Its transient nature and absence of incoming FK dependencies reinforce that it is a runtime processing table rather than a persistent master or transactional entity.

Key Information Stored

The table is documented with 49 columns. The most business-significant columns include:

• PROCESSING_SET_ID — groups a batch of work items sharing a common processing run.
• WORKITEM_OBJ_CODE, WORKITEM_PK_ID, WORK_ITEM_NUMBER — identify the source work item object and its primary key.
• STATUS_ID, WORKITEM_STATUS, DISTRIBUTION_STATUS_ID — track lifecycle and routing state.
• PRIORITY_ID, PRIORITY_LEVEL, PRIORITY_CODE — define ranking for assignment ordering.
• OWNER_TYPE, OWNER_ID, ASSIGNEE_TYPE, ASSIGNEE_ID — capture intended and actual ownership (with OWNER_TYPE_ACTUAL and ASSIGNEE_TYPE_ACTUAL).
• PARTY_ID — links the work item to a customer or party.
• WS_ID (plus WS_ID1, WS_ID2, ASSOCIATION_WS_ID) — foreign key to IEU_UWQM_WORK_SOURCES_B, identifying the work source.
• TASK_TYPE_ID, TASK_PRIORITY_ID — foreign key to JTF_TASK_PRIORITIES_B, aligning with task management.
• Date columns (DUE_DATE, PLANNED_START_DATE, SCHEDULED_START_DATE, ACTUAL_START_DATE) support SLA and scheduling logic.

No documented primary key or unique index is specified in the metadata, so WORKITEM_PK_ID and PROCESSING_SET_ID serve as de facto business identifiers within a processing set. Documented FKs include WS_ID → IEU_UWQM_WORK_SOURCES_B and TASK_PRIORITY_ID → JTF_TASK_PRIORITIES_B.

Common Use Cases and Queries

Typical uses include building agent worklists, auditing distribution routing, and monitoring SLA compliance. A representative query joins the work source:

• SELECT g.WORK_ITEM_NUMBER, g.STATUS_ID, g.PRIORITY_LEVEL, s.NAME FROM IEU_UWQM_ITEMS_GTT g JOIN IEU_UWQM_WORK_SOURCES_B s ON g.WS_ID = s.WS_ID WHERE g.PROCESSING_SET_ID = :p_set;
• Priority-driven worklists: filter on PRIORITY_LEVEL and DUE_DATE to surface overdue items.
• Distribution audits: aggregate by DISTRIBUTION_STATUS_ID and ASSIGNEE_ID.

Related Objects

• IEU_UWQM_WORK_SOURCES_B — joined via WS_ID; defines the source of work items.
• JTF_TASK_PRIORITIES_B — joined via TASK_PRIORITY_ID; supplies priority definitions.
• IEU_UWQM_* work queue configuration tables that parameterize distribution rules.
• JTF_TASKS_B — task master referenced through WORKITEM_OBJ_CODE/WORKITEM_PK_ID.
• UWQ dispatch and routing APIs that consume rows staged in this GTT.