Results for “icx_sessions”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ICX_SESSIONS is the session context table owned by the ICX schema, the database account underpinning Oracle iProcurement and the broader Oracle E-Business Suite Self-Service Framework. In Oracle EBS 12.1.1 and 12.2.2, the table functions as the authoritative runtime registry for active and historical user sessions. Each row captures the state of a single authenticated interaction between a user and the EBS application tier, including navigation context, responsibility and security group assignment, menu and function positioning, NLS environment settings, and connection accounting attributes. Because iProcurement, iSupplier, and numerous self-service modules rely on the ICX framework to persist session state across stateless HTTP requests, ICX_SESSIONS is a foundational object for troubleshooting login failures, session timeouts, and concurrent-user capacity issues.

From a heuristic Data Vault modeling perspective, the metadata classifies ICX_SESSIONS as satellite-leaning. The table is not a pure reference or link entity; it holds descriptive, time-stamped session attributes keyed to a single surrogate identifier, while also carrying foreign key references outward to user, menu, function, security group, and login hub entities. This classification is a modeling suggestion rather than an architectural directive.

Key Information Stored

The primary key is ICX_SESSIONS_PK, defined on SESSION_ID, the surrogate identifier for the session. Two unique indexes are documented: ICX_SESSIONS_U1 on SESSION_ID and ICX_SESSIONS_U2 on XSID, both of which serve as business-key candidates for external lookup. The most significant columns include:

• SESSION_ID — surrogate primary key and join anchor for dependent tables.
• USER_ID — foreign key to FND_USER, identifying the authenticated user.
• RESPONSIBILITY_ID and RESPONSIBILITY_APPLICATION_ID — the active responsibility context for the session.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, defining the data access boundary.
• MENU_ID and FUNCTION_ID — foreign keys to FND_MENUS and FND_FORM_FUNCTIONS, recording navigation position.
• LOGIN_ID — foreign key to FND_LOGINS, linking the session to its authentication event.
• ORG_ID — the operating unit context in a multi-org environment.
• NLS_LANGUAGE, NLS_TERRITORY, NLS_SORT, NLS_DATE_LANGUAGE, NLS_NUMERIC_CHARACTERS, and DATE_FORMAT_MASK — localized environment settings.
• FIRST_CONNECT, LAST_CONNECT, LIMIT_TIME, and TIME_OUT — session lifespan and inactivity controls.
• DISABLED_FLAG, GUEST, PSEUDO_FLAG, DISTRIBUTED, and PROXY_USER_ID — session state and proxy indicators.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

A frequent operational need is identifying who is currently logged in and under which responsibility, typically joined to FND_USER and FND_LOGINS:

• SELECT s.SESSION_ID, u.USER_NAME, s.RESPONSIBILITY_ID, s.LAST_CONNECT FROM ICX_SESSIONS s, FND_USER u WHERE s.USER_ID = u.USER_ID AND s.LAST_CONNECT > SYSDATE - 1;
• Counting concurrent sessions by responsibility or operating unit for capacity planning.
• Diagnosing session timeouts by inspecting LAST_CONNECT, TIME_OUT, and LIMIT_TIME.
• Auditing guest and proxy access through GUEST and PROXY_USER_ID filters.
• Tracing session activity via ICX_AUDIT and ICX_TEXT using SESSION_ID.

Because ICX_SESSIONS is highly volatile, reports should constrain queries by LAST_CONNECT or SESSION_ID ranges to avoid full scans on production instances.

Related Objects

The following objects are most significant in relation to ICX_SESSIONS:

• FND_USER — joined on ICX_SESSIONS.USER_ID = FND_USER.USER_ID.
• FND_LOGINS — joined on ICX_SESSIONS.LOGIN_ID = FND_LOGINS.LOGIN_ID.
• FND_MENUS — joined on ICX_SESSIONS.MENU_ID = FND_MENUS.MENU_ID.
• FND_FORM_FUNCTIONS — joined on ICX_SESSIONS.FUNCTION_ID = FND_FORM_FUNCTIONS.FUNCTION_ID.
• FND_SECURITY_GROUPS — joined on ICX_SESSIONS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• ICX_AUDIT — references ICX_SESSIONS.SESSION_ID, capturing session audit events.
• ICX_TEXT — references ICX_SESSIONS.SESSION_ID, storing session-associated text.
• PON_SUPPLIER_ACTIVITIES — references ICX_SESSIONS.SESSION_ID, tracking supplier-side activity.