Search Results icx_transactions




Overview
Explore in AI Chat

Overview

ICX_TRANSACTIONS is a table owned by the ICX schema, the database account associated with Oracle iProcurement. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model, the object is documented as not being used in the Exchange Catalog, which means its role is confined to internal iProcurement session and menu-tracking activity rather than to catalog content exchange. The table records user session context, responsibility and menu access history, and connection timestamps, functioning as a lightweight audit and navigation-log store for iProcurement pages.

The ETRM metadata classifies ICX_TRANSACTIONS as standalone under the heuristic Data Vault classification mined from its foreign-key structure. In Data Vault modeling terms, this suggests treating the object as neither a classic hub nor a pure link, but as a self-contained record whose business identity is carried by its own transaction and XTID identifiers. Modelers who wish to integrate iProcurement navigation data into an enterprise warehouse may therefore treat ICX_TRANSACTIONS as a standalone satellite-style entity, with FND_SECURITY_GROUPS and FND_MENUS acting as referenced dimension tables.

Key Information Stored

The table contains 17 columns in the documented 12.2.2 schema. The most significant are:

Common Use Cases and Queries

Typical reporting scenarios include reconstructing user navigation history, identifying which responsibilities and functions generate the most iProcurement activity, and auditing menu-driven access patterns. A basic query joining the two foreign keys is illustrative:

  • SELECT t.transaction_id, t.xtid, t.session_id, m.user_menu_name, t.last_connect FROM icx.icx_transactions t, fnd_menus m WHERE t.menu_id = m.menu_id AND t.disabled_flag = 'N';
  • Session tracing: filter on SESSION_ID and order by LAST_CONNECT to reproduce a user's sequence of page visits.
  • Responsibility activity analysis: group by RESPONSIBILITY_ID and RESPONSIBILITY_APPLICATION_ID to quantify usage per responsibility.
  • Stale-record cleanup: identify rows where DISABLED_FLAG is set or where LAST_CONNECT is older than a defined retention threshold.

Because the object is not used in the Exchange Catalog, it should not be relied upon for catalog content queries; reporting should focus on access and navigation metrics.

Related Objects

The documented foreign keys and primary-key relationships connect ICX_TRANSACTIONS to the following significant objects:

  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; governs security-group scoping of transaction rows.
  • FND_MENUS — joined via MENU_ID; supplies the menu name and hierarchy behind each recorded transaction.
  • ICX_TRANSACTIONS_PK — the primary-key constraint on TRANSACTION_ID.
  • ICX_TRANSACTIONS_U1 — unique index on TRANSACTION_ID.
  • ICX_TRANSACTIONS_U2 — unique index on XTID, the alternate business key.

Additional iProcurement session and function tables in the ICX schema are commonly queried alongside this object, but the documented relationships above are the authoritative join paths for ETRM-compliant reporting.