Results for “ieb_agent_indexes”

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

Overview

IEB_AGENT_INDEXES is a table in the IEB (Interaction Blending) product schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. Per the ETRM metadata, it provides a "mapping of Agent IDs with internal bit map indexes, for IEB server internal use only." The IEB module underpins Oracle's interaction blending and routing engine, and this table serves as a control structure that associates an agent with the workload balancing server (WBSVR) that has allocated a bitmap index to that agent. Consequently, the object is technical in nature rather than an end-user business entity; it is populated and consumed by the IEB server processes during routing and workload distribution.

The heuristic Data Vault classification supplied in the metadata is satellite-leaning. In Data Vault modelling terms this suggests the table behaves as a descriptive satellite hanging off one or more parent hubs or links — specifically the agent and server entities — capturing a changing set of descriptive attributes (the bit map index assignments) rather than defining new business keys of its own. Modellers should therefore treat AGENT_ID and WBSVR_WBSVR_ID as references to parent constructs and AGENT_INDEX as the descriptive payload.

Key Information Stored

The table is documented with nine columns. The most significant are:

• AGENT_ID — identifies the interaction/blending agent to which an internal index is assigned. Part of the primary key.
• WBSVR_WBSVR_ID — foreign key to IEB_WB_SERVERS, identifying the workload balancing server that owns the index. This column, named in the user's search, is the join path to the server registry. Part of the primary key.
• AGENT_INDEX — the internal bit map index value assigned to the agent; the core descriptive attribute of this satellite-like structure.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group partitioning, consistent with other IEB tables.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns capturing audit and concurrency information.

The surrogate/business primary key is documented as IEB_AGENT_INDEXES_PK, comprising (AGENT_ID, WBSVR_WBSVR_ID). A unique index, IEB_AGENT_INDEX_PK_U, mirrors the same two columns, confirming this composite as the business-key candidate. There is no separate single-column surrogate key; the identity of a row is the agent-plus-server pairing.

Common Use Cases and Queries

Because the table is designated for IEB server internal use, direct querying is rare and generally limited to diagnostics and reconciliation. Typical scenarios include:

• Diagnosing interaction blending failures by verifying that an agent is registered against the expected server.
• Auditing index allocations across workload balancing servers after a routing change or a server migration.
• Reconciling IEB configuration before or after cloning or patching.

A representative diagnostic query joins to the server registry:

SELECT ai.AGENT_ID,
       ai.AGENT_INDEX,
       ai.WBSVR_WBSVR_ID,
       s.WBSVR_NAME
FROM   IEB.IEB_AGENT_INDEXES ai,
       IEB.IEB_WB_SERVERS     s
WHERE  ai.WBSVR_WBSVR_ID = s.WBSVR_ID
AND    ai.SECURITY_GROUP_ID = :sg_id
ORDER BY ai.AGENT_ID;

Note that WBSVR_ID is the assumed referenced column on IEB_WB_SERVERS; verify the exact join column against the target release. Administrators should not insert, update, or delete rows manually, as the IEB server manages index allocation itself.

Related Objects

• IEB_WB_SERVERS — referenced through IEB_AGENT_INDEXES.WBSVR_WBSVR_ID; the parent registry of workload balancing servers.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; governs row-level security partitioning.
• IEB_AGENT_INDEXES_PK / IEB_AGENT_INDEX_PK_U — the primary key constraint and unique index enforcing agent-plus-server uniqueness.
• IEB agents and interaction-blending server APIs — the runtime components that populate and consume AGENT_INDEX values.
• FND standard WHO/audit views — used to trace who created or last modified an index assignment.

Together these objects define how IEB assigns and tracks internal bit map indexes across its workload balancing servers for each agent.