Search Results icx_session_attributes




Overview
Explore in AI Chat

Overview

ICX_SESSION_ATTRIBUTES is a session context table owned by the ICX schema in Oracle E-Business Suite. It is shipped with Oracle iProcurement and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. The table stores name/value pairs that describe the runtime state of a user's ICX session, allowing applications in the iProcurement and related self-service stack to persist context information such as preferred operating unit, shopping configuration, security group, and localization settings for the duration of a session.

Functionally, the table acts as a normalized attribute store keyed at the granularity of a single session plus an attribute name. Each row captures one attribute of one session, so a single session is represented by many rows rather than one wide record. The documented physical schema contains three columns — SESSION_ID, NAME, and VALUE — and the documented primary key is ICX_SESSION_ATTRIBUTES_PK on (SESSION_ID, NAME). A unique index, ICX_SESSION_ATTRIBUTES_U1, also exists on (SESSION_ID, NAME), confirming the composite business key.

From a Data Vault modeling perspective, the heuristic mined from the foreign-key structure classifies this object as standalone. In Data Vault terms this suggests treating it as an independent structure rather than a dependent child of another hub or link. If a vault model were derived, the composite (SESSION_ID, NAME) would most naturally serve as a business key for a hub or as the key of a satellite attached to a session hub; the VALUE column would populate the descriptive satellite payload.

Key Information Stored

The documented metadata exposes three columns, which together carry the complete semantic content of the table:

  • SESSION_ID — Identifier of the ICX session to which the attribute belongs. It forms the first component of the composite primary key and of the unique index, linking each attribute row back to a specific session record.
  • NAME — Name of the session attribute. It is the second component of the composite primary key and unique index, and it distinguishes the individual attributes recorded within a session.
  • VALUE — Value assigned to the named attribute for that session. This column holds the actual context payload, such as a profile-derived setting, an operating unit identifier, or a display preference.

The surrogate primary key is ICX_SESSION_ATTRIBUTES_PK, defined on the composite of SESSION_ID and NAME. Because no separate single-column surrogate is documented, the business key and the primary key coincide; ICX_SESSION_ATTRIBUTES_U1 provides a redundant unique constraint over the same two columns. The grain of the table is therefore one row per session per attribute name, and queries must always supply both key components to retrieve a unique row.

Common Use Cases and Queries

Typical usage centers on reading or maintaining session context during iProcurement and self-service transactions. Reporting and support scenarios include retrieving all attributes for a session, resolving a single attribute value, and auditing sessions that carry a particular setting.

  • Retrieve every attribute for a given session:

    SELECT name, value FROM icx.icx_session_attributes WHERE session_id = :p_session_id;

  • Resolve a single attribute:

    SELECT value FROM icx.icx_session_attributes WHERE session_id = :p_session_id AND name = :p_name;

  • Find all sessions carrying a specific attribute value:

    SELECT session_id FROM icx.icx_session_attributes WHERE name = :p_name AND value = :p_value;

  • Pivot attributes into a wide, per-session report using conditional aggregation for the attributes of interest.
  • Diagnose stale or orphaned context rows by comparing SESSION_ID values against the parent session table, and purge rows for sessions that no longer exist.

Because the table is narrow and keyed by two columns, index-driven access on (SESSION_ID, NAME) is efficient, while full-table scans are best avoided in high-volume reporting.

Related Objects

The documented relationship data classifies ICX_SESSION_ATTRIBUTES as standalone, meaning no foreign keys to or from other tables are recorded in the ETRM metadata. Its principal relationships are therefore logical rather than enforced:

  • ICX_SESSION_ATTRIBUTES_PK — primary key constraint on (SESSION_ID, NAME).
  • ICX_SESSION_ATTRIBUTES_U1 — unique index on (SESSION_ID, NAME), reinforcing the business key.
  • ICX session tables — the parent session record identified by SESSION_ID; joined logically on SESSION_ID because no enforced FK is documented.
  • ICX schema objects — sibling tables in the ICX schema that consume the same session context during iProcurement processing.
  • Oracle iProcurement application logic — reads and writes the name/value attributes at runtime to persist session context.

When integrating or reporting, join to the session parent on SESSION_ID and filter on NAME to isolate the required context attribute.