Search Results ies_transactions_pk

Overview

The IES.IES_TRANSACTIONS table is a core transactional object within the IES (Internet Expense and Scripting) module of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. Its documented purpose is to hold all interactions for a session, making it the central log of scripted agent activity executed through the IES Scripting framework. Each row captures a discrete unit of agent-script interaction, anchored to the deployed script that was invoked and the agent that executed it.

The object is classified as VALID and resides in the IES schema. From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. This suggests the table functions primarily as a descriptive record attached to parent hubs such as the deployed script, the executing agent, and the security group — rather than as a pure hub or a pure link. Modelers designing a vault layer should treat IES_TRANSACTIONS as a satellite capturing the state, timing, and outcomes of each scripting session.

Key Information Stored

The documented physical schema for 12.2.2 contains 30 columns. The most significant are:

• TRANSACTION_ID — the surrogate primary key, defined by the constraint IES_TRANSACTIONS_PK. This is a system-generated identifier that uniquely distinguishes each session interaction.
• DSCRIPT_ID — foreign key to IES_DEPLOYED_SCRIPTS, identifying which deployed script the transaction executed.
• AGENT_ID — foreign key to IES_AGENTS, identifying the agent that performed the interaction.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org data security partitioning.
• START_TIME and END_TIME — the interval boundaries of the interaction, supporting duration and performance analysis.
• STATUS — the current disposition of the transaction (for example completed, failed, or in progress).
• RESTART_DATA — persisted state permitting a session to resume following interruption.
• OBJECT_VERSION_NUMBER — optimistic locking control for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO-column audit set.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard oracle APPLSYS descriptive flexfield (DFF) columns, available for customer-defined extensions.

The documented unique index entry, SYS_IL0000083963C00030$$, is a LOB index rather than a business-key unique index; there are therefore no documented business-key candidates beyond the surrogate TRANSACTION_ID. Because the table carries an OBJECT_VERSION_NUMBER and the full attribute set, it is a DFF-enabled transactional entity.

Common Use Cases and Queries

Operational and reporting scenarios typically center on tracing script execution history by agent, by deployed script, or by time window. A representative query to enumerate transactions for a given agent within a period is:

• SELECT transaction_id, dscript_id, start_time, end_time, status FROM ies.ies_transactions WHERE agent_id = :agent_id AND start_time BETWEEN :from_date AND :to_date;

To measure script performance, join to IES_DEPLOYED_SCRIPTS and aggregate duration:

• SELECT d.dscript_name, t.status, COUNT(*) txn_count, AVG(t.end_time - t.start_time) avg_duration FROM ies.ies_transactions t JOIN ies.ies_deployed_scripts d ON t.dscript_id = d.dscript_id GROUP BY d.dscript_name, t.status;

Diagnostic use cases include locating failed or stalled sessions by filtering on STATUS and looking for null END_TIME values, and examining RESTART_DATA to resume interrupted sessions. Security-conscious reporting should always constrain queries with SECURITY_GROUP_ID to respect multi-org access policies.

Related Objects

• IES_DEPLOYED_SCRIPTS — referenced via IES_TRANSACTIONS.DSCRIPT_ID; supplies the script definition for each interaction.
• IES_AGENTS — referenced via IES_TRANSACTIONS.AGENT_ID; identifies the executing agent.
• FND_SECURITY_GROUPS — referenced via IES_TRANSACTIONS.SECURITY_GROUP_ID; governs data access partitioning.
• IES_PANEL_DATA — child table referencing IES_TRANSACTIONS.TRANSACTION_ID; holds captured panel field values.
• IES_QUESTION_DATA — child table referencing IES_TRANSACTIONS.TRANSACTION_ID; holds responses captured during the session.

Together these relationships establish IES_TRANSACTIONS as the central interaction record linking deployed scripting logic to captured response data.