Search Results ies_agents

Overview

The IES_AGENTS table is a core data object within the Oracle E-Business Suite IES (Scripting) module. Its documented purpose is to store Agent information used by the Scripting product. Within Oracle EBS 12.1.1 and 12.2.2, the IES Scripting module provides the infrastructure that supports interactive scripting, telephony, and agent-driven transaction flows, and IES_AGENTS acts as the master reference for the individual agents that participate in those workflows.

The table resides in the IES schema and is documented with a status of VALID. Its physical definition includes 26 columns. The primary key, IES_AGENTS_PK, is defined on the surrogate AGENT_ID column. Based on the foreign key structure mined from the metadata, the table is classified heuristically as hub-leaning in a Data Vault modeling sense. This suggests that IES_AGENTS functions primarily as a hub entity: a stable, uniquely identified business object (an agent) whose descriptive attributes and relationships can be modeled as satellites or links around it.

Key Information Stored

Not every one of the 26 documented columns carries equal analytical weight. The most significant columns are:

• AGENT_ID — The surrogate primary key defined by IES_AGENTS_PK. This is the unique identifier referenced by dependent tables.
• AGENT_LOGIN — The login identifier associated with the agent. This is the most probable business-key candidate for uniquely identifying an agent in operational terms.
• RESOURCE_ID — A reference to the underlying resource record associated with the agent, likely linking the agent to a resource in a related module.
• SECURITY_GROUP_ID — A foreign key to FND_SECURITY_GROUPS, controlling the security grouping under which the agent record is partitioned.
• OBJECT_VERSION_NUMBER — The standard EBS optimistic locking column used to detect concurrent updates.
• CREATED_BY, CREATION_DATE — Standard WHO columns capturing record creation audit information.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns capturing the most recent modification audit trail.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard EBS descriptive flexfield (DFF) columns, providing extensible storage for customer-specific agent attributes.

The presence of the WHO audit columns, the DFF block, and OBJECT_VERSION_NUMBER confirms that IES_AGENTS follows standard Oracle EBS table conventions and is maintained through the application's concurrent and form-based processing.

Common Use Cases and Queries

Typical uses of IES_AGENTS include agent lookup, agent-to-transaction reporting, and security-scoped access analysis. A common query retrieves active agents with their login and security grouping:

• SELECT AGENT_ID, AGENT_LOGIN, RESOURCE_ID, SECURITY_GROUP_ID FROM IES.AGENTS WHERE SECURITY_GROUP_ID = :p_group;
• Joining IES_AGENTS to IES_TRANSACTIONS on AGENT_ID to attribute transactions to the responsible agent.
• Auditing recent changes using LAST_UPDATED_BY and LAST_UPDATE_DATE to identify who modified agent records.
• Reporting on DFF values via ATTRIBUTE_CATEGORY and ATTRIBUTE1..15 for customer-specific agent classification.
• Resolving the associated security group by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Related Objects

The foreign key metadata establishes the following significant relationships:

• IES_TRANSACTIONS — References IES_AGENTS via IES_TRANSACTIONS.AGENT_ID → IES_AGENTS.AGENT_ID. This is the primary dependent relationship, linking transactions to the agent that handled them.
• FND_SECURITY_GROUPS — Referenced by IES_AGENTS.SECURITY_GROUP_ID, providing the security partitioning context for agent records.

Together, these relationships position IES_AGENTS as the agent hub at the center of the IES Scripting transaction and security model.