Results for “work_item_id”

50+ results




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

Overview

The IEB.IEB_WB_WORK_ITEMS table is a core transactional table within the Oracle E-Business Suite Interaction Blending (IEB) module. Its documented purpose is to store media work items, meaning discrete units of routing or fulfillment work that must be processed by an interaction routing engine or a media-blending workbench. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the persistent record of queued work, capturing the item identity, the source system, queue assignment, and delivery parameters needed to route an inbound interaction to the correct resource.

The table is owned by the IEB schema and is classified as VALID. It resides in a multi-tenant aware data model, evidenced by the presence of the SECURITY_GROUP_ID column and its foreign key to FND_SECURITY_GROUPS. The documented heuristic Data Vault classification is satellite-leaning, which indicates that the table is best modeled as a descriptive satellite attached to a parent hub (such as a work-item hub), rather than as an independent hub or a pure link table. This classification is a modeling suggestion and should be validated against the actual ETL or integration design.

Key Information Stored

The table contains 16 documented columns. The most operationally significant are listed below:

  • WITM_ID — The surrogate primary key. It is defined by the constraint IEB_WB_WORK_ITEMS_PK and also appears in the unique index IEB_WB_WORK_ITEMS_PK_U.
  • WORK_ITEM_ID — The business-key candidate. It is referenced by the unique index IEB_WB_WORK_ITEM_UK and provides the functional identity of the work item.
  • SVCVQ_SVCVQ_ID — Foreign key to IEB_SVC_VIRTUAL_QUEUES, identifying the virtual service queue into which the work item is placed.
  • ORIGINAL_WORK_ID — Reference to the originating work item, supporting re-queuing or transfer tracking.
  • QUEUED_TIME — The timestamp at which the work item was queued; essential for aging, SLA, and wait-time analytics.
  • SOURCE — The originating channel or system that produced the work item.
  • PARAM1 / PARAM2 — Generic parameter columns holding context-specific routing attributes.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing data access isolation.
  • CACHED_Y_N — A flag indicating whether the work item is held in cache.
  • MMS_SERVER_ID — Identifier of the media server associated with the item.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns maintained automatically by the application.

Common Use Cases and Queries

Typical usage centers on monitoring queue depth, measuring wait time, and reconciling work items across the routing chain. A representative pattern joins the table to the virtual queue and the underlying work item master:

  • Queue workload reporting: aggregate COUNT(*) grouped by SVCVQ_SVCVQ_ID to size virtual queues.
  • Aging analysis: compare SYSDATE to QUEUED_TIME to identify stale items.
  • Channel tracing: group by SOURCE to quantify inbound volume per media channel.
  • Re-queue detection: query where ORIGINAL_WORK_ID IS NOT NULL to trace transferred work.

A sample query might select WITM_ID, WORK_ITEM_ID, SVCVQ_SVCVQ_ID, QUEUED_TIME, SOURCE from IEB.IEB_WB_WORK_ITEMS, filtered on SECURITY_GROUP_ID for the active operating unit.

Related Objects

  • IEB_SVC_VIRTUAL_QUEUES — joined via IEB_WB_WORK_ITEMS.SVCVQ_SVCVQ_ID = IEB_SVC_VIRTUAL_QUEUES.SVCVQ_ID; defines the queue receiving the item.
  • IEU_UWQM_ITEMS — joined via WORK_ITEM_ID; represents the universal work queue master record.
  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; enforces data security.
  • IEB_WB_WORK_ITEMS_PK / IEB_WB_WORK_ITEM_UK — the primary and unique constraints governing identity.
  • Interaction Blending routing APIs within the IEB module that consume these rows when blending media interactions.