Results for “wbsc_wbsc_id”

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

Overview

IEB_SVC_VIRTUAL_QUEUES is an Oracle E-Business Suite table owned by the IEB schema, which supports the Interaction Blending (IEB) module. The table stores summary information about virtual queues, which function as dynamic agent groups defined for internal use by the IEB server. Unlike static agent groups configured directly against a supervisor or service category, virtual queues are fluid groupings whose membership is resolved at runtime and used by the interaction blending engine to route and distribute work items across eligible agents.

From a Data Vault modeling perspective, the mined relationship data classifies this object as hub-leaning. This suggests treating SVCVQ_ID as a durable business key anchored in a hub, with descriptive or state-bearing attributes optionally modeled as a satellite. The classification is heuristic and should be treated as a modeling suggestion rather than a prescriptive design decision.

Key Information Stored

The table contains 10 documented columns in the 12.2.2 physical schema. The primary key is IEB_SVC_VIRTUAL_QUEUES_PK, defined on the surrogate identifier SVCVQ_ID. A unique index, IEB_SVC_VIRTUAL_QUEUES_PK_U, also exists on SVCVQ_ID, making it the sole documented business-key candidate for the row.

• SVCVQ_ID — Surrogate primary key and unique business-key candidate uniquely identifying each virtual queue.
• WBSC_WBSC_ID — Foreign key to IEB_WB_SVC_CATS, associating the virtual queue with a service category in the work blending configuration.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, driving row-level security and data access partitioning.
• SEQUENCE_NUMBER — Ordering or prioritization value used when resolving or presenting virtual queues.
• EXPIRATION_DATE — Effective end date controlling the lifecycle and active validity of the virtual queue.
• CREATED_BY, CREATION_DATE — Standard WHO-column audit attributes recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit attributes capturing the most recent modification and its source login.

Common Use Cases and Queries

Typical usage centers on reviewing virtual queue definitions, tracing which work items are mapped to a queue, and reporting on agent coverage. A common pattern joins the queue to its service category to produce a labeled listing:

• Queue lookup by surrogate key: SELECT * FROM IEB.IEB_SVC_VIRTUAL_QUEUES WHERE SVCVQ_ID = :p_id;
• Queue-to-category reporting: joining on WBSC_WBSC_ID to IEB_WB_SVC_CATS for descriptive naming.
• Active queue listing: filtering on EXPIRATION_DATE and ordering by SEQUENCE_NUMBER.
• Work item volume per queue: aggregating IEB_WB_WORK_ITEMS by SVCVQ_SVCVQ_ID.
• Security-scoped reporting: restricting rows by SECURITY_GROUP_ID for multi-org or data security compliance.

Because the table is described as being for IEB server internal use, direct DML is generally discouraged. Reporting should query in read-only fashion, and any configuration should flow through supported IEB setup screens or APIs.

Related Objects

The table participates in a small but well-defined set of relationships. The two inbound foreign keys are the most operationally significant because they tie queues to actual workloads and agent mappings.

• IEB_AGENT_MAPS — References this table via SVCVQ_SVCVQ_ID, linking agents to their virtual queue assignments.
• IEB_WB_WORK_ITEMS — References this table via SVCVQ_SVCVQ_ID, associating individual work items with a virtual queue.
• IEB_WB_SVC_CATS — Parent of WBSC_WBSC_ID, providing the service category context for the queue.
• FND_SECURITY_GROUPS — Parent of SECURITY_GROUP_ID, enforcing row-level security.

Together these relationships establish IEB_SVC_VIRTUAL_QUEUES as a connecting definition table between service categorization, agent membership, and work item routing within the Interaction Blending engine.