Search Results sys_il0000083963c00030

Overview

IES.IES_TRANSACTIONS is the central transaction table within the Oracle EBS Interaction and Scripting (IES) module, the technology stack underlying the iStore and TeleSales/TeleService interactive script engine. Each row in this table records a single interaction: a complete session in which an agent executes the flow of a deployed script while engaging a customer. The table therefore functions as the operational log of scripting activity, capturing who ran a script, which script was executed, when the interaction began and ended, and a broad set of descriptive flexfield attributes used by the application or by customer extensions.

From a dimensional modeling perspective, the table is a satellite-leaning entity. Its grain is one row per interaction, with a surrogate primary key (TRANSACTION_ID) and foreign keys to IES_DEPLOYED_SCRIPTS, IES_AGENTS, and FND_SECURITY_GROUPS. Because the surrounding dependent tables (IES_PANEL_DATA and IES_QUESTION_DATA) capture the detailed answers gathered during an interaction, IES_TRANSACTIONS behaves as the parent satellite of an interaction event, joined upward to the agents and deployed-scripts dimensions. Note that the storage attributes list a LOB index (SYS_IL0000083963C00030$$) which is a system-generated index for a LOB segment rather than a true business-key candidate; the primary-key index IES_TRANSACTIONS_PK remains the authoritative unique identifier.

Key Information Stored

The primary key is TRANSACTION_ID (NUMBER), the unique identifier of each interaction and the column referenced by dependent tables. The principal business references are DSCRIPT_ID, a foreign key to IES_DEPLOYED_SCRIPTS identifying the specific deployed script being run, and AGENT_ID, a foreign key to IES_AGENTS identifying the agent conducting the interaction. Together these represent the two dimensions of an interaction — the script and the agent.

The keyed evidence columns are:

• START_TIME and END_TIME (DATE) — the interaction's start and end timestamps, used for duration, throughput, and agent-utilization analysis.
• STATUS — the current state of the interaction.
• SECURITY_GROUP_ID — the responsibility/security group under which the interaction was executed.
• OBJECT_VERSION_NUMBER — standard optimistic locking column.
• RESTART_DATA — state data allowing an interrupted interaction to be resumed.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns present on nearly every EBS table.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2, 150) — the descriptive flexfield (DFF) columns used by the application or customer to store additional interaction context beyond the seeded columns.

The primary key TRANSACTION_ID is distinct from the LOB index; developers should treat TRANSACTION_ID as the only documented unique key on the table.

Common Use Cases and Queries

The table is the natural starting point for agent activity reporting, script-execution auditing, and interaction analytics. A typical join to resolve an interaction to its agent and script:

• SELECT t.transaction_id, a.agent_name, s.script_name, t.start_time, t.end_time, t.status FROM ies.ies_transactions t, ies.ies_agents a, ies.ies_deployed_scripts s WHERE t.agent_id = a.agent_id AND t.dscript_id = s.dscript_id AND t.start_time >= :start_date;

A verification query to confirm a specific transaction and its dependent data would resolve the interaction through TRANSACTION_ID:

• SELECT t.transaction_id, t.agent_id, t.dscript_id, q.question_id, q.response_value FROM ies.ies_transactions t, ies.ies_question_data q WHERE t.transaction_id = q.transaction_id AND t.transaction_id = :p_transaction_id;

Common reporting scenarios include: counting interactions per agent per day; measuring average interaction duration as (END_TIME − START_TIME); listing all interactions for a given deployed script; and auditing incomplete interactions where END_TIME is null. Because the table carries SECURITY_GROUP_ID, queries should be filtered by the operating responsibility to respect EBS security group behavior.

Related Objects

The table is bound to the following objects within IES, via documented foreign keys:

• IES_AGENTS — referenced through TRANSACTION_ID. AGENT_ID; the agent dimension of an interaction.
• IES_DEPLOYED_SCRIPTS — referenced through TRANSACTION_ID. DSCRIPT_ID; the script instance executed.
• FND_SECURITY_GROUPS — referenced through TRANSACTION_ID. SECURITY_GROUP_ID; the security context governing the row.
• IES_PANEL_DATA — child table; references IES_TRANSACTIONS.TRANSACTION_ID. Holds the responses captured for each panel in the script.
• IES_QUESTION_DATA — child table; references IES_TRANSACTIONS.TRANSACTION_ID. Holds the individual question-level answers collected during the interaction.

Where the metadata is exhausted, the IES schema also provides the interactive scripting engine itself: the deployed scripts referenced here are defined in IES_SCRIPTS and deployed into IES_DEPLOYED_SCRIPTS, which is the parent of IES_QUESTIONS, IES_PANELS, and related configuration tables. Because IES_TRANSACTIONS sits at the head of the interaction data model, any purge, archiving, or growth-management strategy for the IES schema must account for it as the reconciling parent of IES_PANEL_DATA and IES_QUESTION_DATA.