Results for “fnd_session_values”

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

Overview

FND_SESSION_VALUES is an Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store servlet session values, meaning it persists per-session state generated by the Oracle EBS web tier during authenticated user interactions with the applications. Because the table is maintained by the framework rather than by any functional module, it is transparent to end users but integral to how the EBS middle tier tracks and isolates concurrent web sessions. The ETRM metadata records the object status as VALID and lists ten documented columns in the 12.2.2 physical schema.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies FND_SESSION_VALUES as standalone. In practice, this suggests treating the table as its own hub-like entity keyed on the session identifier, without a parent dimension in the modeled FK graph. The classification is a modeling suggestion only, derived from the absence of outbound foreign-key relationships, and should not be interpreted as a formal Data Vault design assertion by Oracle.

Key Information Stored

The primary key of FND_SESSION_VALUES is FND_SESSION_VALUES_PK1, defined on the column ICX_SESSION_ID. A parallel unique index, FND_SESSION_VALUES_U1, is also documented on ICX_SESSION_ID, confirming that the session identifier is both the surrogate primary key and the single business-key candidate. There is no separate sequence-generated surrogate distinct from the session identifier, which makes the table unusual among EBS transactional objects.

• ICX_SESSION_ID — the session identifier; primary key and sole unique business key.
• SESSION_VALUE — the payload holding the persisted session attribute or value associated with the session identifier.
• DISABLED_FLAG — indicates whether the stored session value is inactive or suppressed from use.
• TIMESTAMP — the point in time associated with the session value, used for staleness and expiry evaluation.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic locking column governing concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns recording creation and last modification context.

The presence of the WHO columns and OBJECT_VERSION_NUMBER indicates the table is maintained through standard EBS DML conventions and is subject to the same auditing and concurrency controls as other APPLSYS objects.

Common Use Cases and Queries

Typical usage centers on session diagnostics, cleanup of stale sessions, and support investigations into authentication or framework errors. A representative diagnostic query identifies recently active sessions:

• SELECT ICX_SESSION_ID, SESSION_VALUE, TIMESTAMP FROM APPLSYS.FND_SESSION_VALUES WHERE TIMESTAMP > SYSDATE - 1 ORDER BY TIMESTAMP DESC; — surfaces session activity within the last day.
• SELECT COUNT(*) FROM APPLSYS.FND_SESSION_VALUES WHERE DISABLED_FLAG = 'Y'; — measures disabled or suppressed session values.
• SELECT * FROM APPLSYS.FND_SESSION_VALUES WHERE ICX_SESSION_ID = :session_id; — retrieves all attributes for a specific session during support triage.

Reporting use cases are limited because the table is framework-internal; most value comes from joins to BSC_CURRENT_SESSIONS for operational monitoring of active users and from correlation with ZX_TRX_HEADERS_GT during concurrent tax and transaction processing. Because session rows accumulate over time, DBAs commonly purge obsolete entries rather than report on them historically.

Related Objects

The documented relationship data identifies two tables with foreign keys referencing FND_SESSION_VALUES on ICX_SESSION_ID:

• BSC_CURRENT_SESSIONS — references FND_SESSION_VALUES via ICX_SESSION_ID; tracks currently active sessions and is the primary downstream consumer.
• ZX_TRX_HEADERS_GT — references FND_SESSION_VALUES via ICX_SESSION_ID from the E-Business Tax module, linking tax transaction header processing to the originating session.

Both relationships join on the ICX_SESSION_ID column, the sole documented key. The referenced objects belong to Application Object Library and E-Business Tax respectively, indicating the session store is consumed across module boundaries. No other referencing tables are documented in the ETRM metadata, consistent with the standalone classification.