Search Results icx_sessions




Overview
Explore in AI Chat

Overview

The ICX_SESSIONS table is a core technical table within Oracle E-Business Suite, specifically under the iProcurement (ICX) product family. It functions as the session context table, responsible for storing and managing real-time state information for user sessions across the application. Its primary role is to track active user interactions, maintaining critical context such as user identity, current navigation state, and session-specific attributes. This data is essential for the application's session management framework, enabling features like session timeout enforcement, user activity auditing, and maintaining state across the stateless HTTP protocol. The table is central to the functionality of self-service applications, including iProcurement and other modules utilizing the Oracle Applications Framework (OAF).

Key Information Stored

The table's structure is designed to capture the lifecycle and context of a user session. The primary key, SESSION_ID, uniquely identifies each session. Key foreign key columns link the session to other fundamental application entities: USER_ID references FND_USER to identify the authenticated user; MENU_ID references FND_MENUS to track the user's current menu; and FUNCTION_ID references FND_FORM_FUNCTIONS to log the current form function being accessed. Other significant columns typically include SESSION_NUMBER for internal sequencing, START_TIME and LAST_UPDATE_DATE to track session duration and activity, TIMEOUT_VALUE for session management, and various columns for storing session-specific parameters, client information (like IP address or browser details), and state flags indicating whether the session is active or disabled.

Common Use Cases and Queries

This table is frequently queried for session monitoring, troubleshooting, and auditing purposes. Common scenarios include identifying active users, diagnosing session-related issues, and analyzing user concurrency. Sample SQL patterns include listing all active sessions for a specific user, identifying sessions that have exceeded a timeout threshold, or auditing the functions accessed during a session. For example, a basic query to find active sessions might be:

  • SELECT s.session_id, u.user_name, s.start_time, s.last_update_date FROM icx_sessions s, fnd_user u WHERE s.user_id = u.user_id AND s.disabled_flag != 'Y';

Reporting use cases often involve joining with FND_USER and related audit tables (like ICX_AUDIT) to generate user activity reports or investigate security and access patterns. Administrators may also run purge scripts against this table to clean up expired session data.

Related Objects

As indicated by the foreign key relationships in the provided metadata, ICX_SESSIONS is a pivotal table with several dependencies. It is referenced by child tables that log detailed activities within a session, such as ICX_AUDIT (for general session auditing) and ICX_TEXT (which may store session-specific textual data). The PON_SUPPLIER_ACTIVITIES table in iProcurement also references it, linking supplier portal activities to a user session. Furthermore, it depends on core application foundation tables: FND_USER for user details, FND_MENUS for navigation, and FND_FORM_FUNCTIONS for function security. This network of relationships underscores its role as a central hub connecting user identity to their transactional and navigational footprint within the system.