Results for “ieb_agent_maps”

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

Overview

IEB_AGENT_MAPS is a table owned by the IEB schema within the Oracle E-Business Suite Interaction Blending (IEB) product. Its documented purpose is to store the indexes of member agents for virtual queues. In practical terms, the table functions as a mapping layer that associates individual agents with the virtual queues to which they belong, enabling the blending engine to resolve which agents are eligible to service interactions routed through a given virtual queue.

Because IEB governs how inbound and outbound interactions are distributed across communication channels in Oracle Advanced Inbound and related telephony integrations, IEB_AGENT_MAPS sits in the operational path between queue definition and agent assignment. The table exists in both Oracle EBS 12.1.1 and 12.2.2, with the documented physical schema (10 columns) confirmed for 12.2.2. Under the heuristic Data Vault classification mined from its foreign key structure, the object is described as satellite-leaning. This suggests that IEB_AGENT_MAPS is best modelled as a satellite attached to the virtual queue hub represented by IEB_SVC_VIRTUAL_QUEUES, capturing descriptive membership attributes that change over time rather than acting as an independent hub or a pure association link.

Key Information Stored

The table is defined with a surrogate primary key and a defined foreign key relationship to the virtual queue definition. The most significant documented columns are as follows:

• AGTMAP_ID — The surrogate primary key, enforced by the unique index IEB_AGENT_MAPS_PK_U and the constraint IEB_AGENT_MAPS_PK. This column uniquely identifies each agent-to-virtual-queue mapping row and is the only documented business-key candidate for the table.
• SVCVQ_SVCVQ_ID — Foreign key to IEB_SVC_VIRTUAL_QUEUES, identifying the virtual queue to which the mapping applies. This is the join column that anchors the table to the queue definition.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data partitioning and access control consistent with Oracle EBS security group conventions.
• ROW_INDEX and ROW_AGENT_BITMAP — These columns carry the agent index and bitmap payload implied by the object description. ROW_AGENT_BITMAP in particular is consistent with a compressed representation of member agent membership, allowing the blending engine to evaluate queue membership efficiently at runtime.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each row and when.

No other business-key unique index beyond AGTMAP_ID is documented. The pairing of SVCVQ_SVCVQ_ID with the bitmap and index columns indicates that the table stores membership state rather than a simple flat list of agent identifiers.

Common Use Cases and Queries

Typical usage centres on reporting and diagnostics for virtual queue configuration. Administrators and support analysts query this table to verify which agents are mapped to a given virtual queue, to reconcile queue membership against agent configuration, and to investigate interaction routing anomalies.

A common pattern joins the mapping to the queue definition:

• SELECT m.AGTMAP_ID, m.SVCVQ_SVCVQ_ID, m.ROW_INDEX, m.LAST_UPDATE_DATE FROM IEB.IEB_AGENT_MAPS m WHERE m.SVCVQ_SVCVQ_ID = :queue_id;

A second pattern aggregates membership counts by virtual queue for capacity reporting:

• SELECT SVCVQ_SVCVQ_ID, COUNT(*) AS member_rows FROM IEB.IEB_AGENT_MAPS GROUP BY SVCVQ_SVCVQ_ID;

Because ROW_AGENT_BITMAP is a bitmap, direct SQL interpretation of its contents is generally impractical; reporting typically relies on the IEB application tier or on the IEB_AGENT_MAPS_PK index for precise lookups by AGTMAP_ID. Audit-oriented queries filter on LAST_UPDATE_DATE to identify recently changed mappings.

Related Objects

The following objects are most significant in relation to IEB_AGENT_MAPS, based on the documented foreign key and primary key relationships:

• IEB_SVC_VIRTUAL_QUEUES — Referenced through IEB_AGENT_MAPS.SVCVQ_SVCVQ_ID. This is the parent object that defines virtual queues, and it is the primary join target for all membership queries.
• FND_SECURITY_GROUPS — Referenced through IEB_AGENT_MAPS.SECURITY_GROUP_ID. This standard Oracle Application Object Library table governs data partitioning and must be considered in any multi-organisation or multi-security-group reporting.
• IEB_AGENT_MAPS_PK / IEB_AGENT_MAPS_PK_U — The primary key constraint and its backing unique index on AGTMAP_ID, which determine lookup performance and enforce row uniqueness.

Interaction Blending functionality that consumes virtual queue membership — including agent routing and blending rule evaluation components — depends indirectly on this table through its relationship with IEB_SVC_VIRTUAL_QUEUES. When the virtual queue definition is purged or reconfigured, the corresponding mapping rows must be maintained in step to preserve routing integrity.