Search Results icx_transactions_u2

Overview

ICX.ICX_TRANSACTIONS is an Oracle E-Business Suite table owned by the ICX schema (Oracle iProcurement / Internet Computing Architecture components). It stores session-level transaction context records that map a user's runtime session to the responsibility, security group, menu, function, and page elements active at the moment of connection. In EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_TX_DATA tablespace and is designated Oracle Internal Use Only; Oracle does not support direct application data access except through standard Oracle Applications programs. The user search string "Tran NONTRACS For IC" corresponds to the transaction row associated with non-transactional (NONTRACS) activity within an ICX-based function context.

Under a heuristic Data Vault classification, this object is modelled as standalone — it contains no natural parent-child dependencies in reference to other tables and functions as an independent record set keyed by its own surrogate identifier. It therefore does not behave as a hub, link, or satellite in the strict Data Vault sense; it is best treated as a self-contained context or audit entity.

Key Information Stored

The table contains 17 documented columns. The most operationally significant are:

• TRANSACTION_ID — surrogate primary key (ICX_TRANSACTIONS_PK), a system-generated numeric identifier and the unique index ICX_TRANSACTIONS_U1.
• XTID — a 32-character transaction context string, also a unique key (ICX_TRANSACTIONS_U2), used by the ICX framework as a business-key candidate.
• SESSION_ID — links the transaction to an active user session; indexed non-uniquely via ICX_TRANSACTIONS_N1.
• RESPONSIBILITY_APPLICATION_ID and RESPONSIBILITY_ID — define the application and responsibility under which the session operated.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling organizational data visibility.
• MENU_ID — foreign key to FND_MENUS, identifying the menu navigation context.
• FUNCTION_ID and FUNCTION_TYPE — identify the specific EBS function invoked and its type (e.g., FORM, JSP, WWW).
• PAGE_ID — the page within a function context where the transaction occurred.
• LAST_CONNECT — timestamp of the most recent connection event.
• DISABLED_FLAG — status indicator (30-character string) for this transaction record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO-column audit trail.

Common Use Cases and Queries

Typical scenarios centre on diagnosing user access problems, auditing responsibility and menu usage, and tracing session context for iProcurement or self-service flows. A common pattern locates the transaction for a session and responsibility:

• Session tracing: SELECT TRANSACTION_ID, XTID, SESSION_ID, FUNCTION_ID, FUNCTION_TYPE FROM ICX.ICX_TRANSACTIONS WHERE SESSION_ID = :p_session_id;
• Responsibility usage reporting: aggregate by RESPONSIBILITY_ID and RESPONSIBILITY_APPLICATION_ID to see which responsibilities generated transactions.
• Security-group visibility checks: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to confirm organisational scope.
• Menu and function navigation audits: join MENU_ID to FND_MENUS and filter on FUNCTION_TYPE to distinguish form-based versus web-page activity.
• Stale-session cleanup: identify records where LAST_CONNECT exceeds a threshold and DISABLED_FLAG indicates an inactive state.

Reports should filter by LAST_CONNECT ranges rather than relying on CREATION_DATE alone, since transaction rows may be updated across the session lifetime.

Related Objects

The following objects are most significant in relation to ICX.ICX_TRANSACTIONS:

• APPS.ICX_TRANSACTIONS — the APPS-synonym view typically referenced in application code.
• FND_SECURITY_GROUPS — joined on ICX_TRANSACTIONS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• FND_MENUS — joined on ICX_TRANSACTIONS.MENU_ID = FND_MENUS.MENU_ID.
• FND_RESPONSIBILITY and FND_APPLICATION — resolve the responsibility and application identifiers into meaningful names.
• FND_USER — via the WHO columns (CREATED_BY, LAST_UPDATED_BY) for user attribution.
• FND_FORM_FUNCTIONS — resolves FUNCTION_ID into a function name and description.

Because the object is flagged Oracle Internal Use Only, any custom reporting should treat it as read-only and avoid DML beyond Oracle-supplied concurrent programs.