Search Results fnd_appl_sessions




Overview
Explore in AI Chat

Overview

FND_APPL_SESSIONS is an Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores auditing information for non-Forms based application sessions, such as those initiated through self-service HTML pages, Oracle Application Framework (OAF) pages, and other web-delivered components. Where Forms-based activity is captured through FND_LOGINS and related session tables, FND_APPL_SESSIONS complements that coverage by recording session-level audit detail for the web tier. The table carries a documented physical schema of seven columns and is catalogued as VALID in the ETRM repository.

Under the heuristic Data Vault classification mined from its foreign key structure, FND_APPL_SESSIONS is assessed as standalone. This suggests a modeling approach in which the table is treated as its own entity rather than as a strict hub, link, or satellite, though its dependency on FND_LOGINS via LOGIN_ID means it can also be interpreted as an extension satellite to the login hub where session enrichment is required.

Key Information Stored

The seven documented columns capture session identity, timing, and responsibility context:

  • LOGIN_ID — Foreign key to FND_LOGINS. This is the principal join column and the most reliable business-key candidate linking the session record to the originating login event.
  • LOGIN_TYPE — Classifies the session type, distinguishing the non-Forms application context being audited.
  • AUDSID — The Oracle database audit session identifier, useful for correlating the record to database-level auditing views such as V$SESSION or FND_LOGINS.
  • START_TIME — Timestamp marking when the application session began.
  • END_TIME — Timestamp marking when the session terminated; a null value typically indicates an active or abnormally terminated session.
  • LOGIN_RESP_ID — The responsibility identifier under which the session operated, supporting responsibility-level audit reporting.
  • RESOURCE_CONSUMER_GROUP — The database Resource Manager consumer group assigned to the session, relevant to workload and concurrency analysis.

The metadata does not document a separate surrogate primary key column; LOGIN_ID functions as the practical key and is the documented foreign key path.

Common Use Cases and Queries

The table is used primarily for security auditing, concurrent-user analysis, and session duration reporting. A typical join correlates sessions with their originating login:

  • Identifying long-running or still-open sessions by querying records where END_TIME is null.
  • Reporting session counts grouped by LOGIN_TYPE or LOGIN_RESP_ID to profile responsibility usage.
  • Correlating AUDSID with database session auditing to trace a specific web session.
  • Reviewing RESOURCE_CONSUMER_GROUP assignments to validate Resource Manager configuration.

A representative pattern joins on the documented key: SELECT s.LOGIN_ID, s.START_TIME, s.END_TIME FROM FND_APPL_SESSIONS s JOIN FND_LOGINS l ON s.LOGIN_ID = l.LOGIN_ID. Session duration is commonly derived as the interval between START_TIME and END_TIME.

Related Objects

The most significant related object is the table referenced by the documented foreign key:

  • FND_LOGINS — joined via FND_APPL_SESSIONS.LOGIN_ID to FND_LOGINS.LOGIN_ID; the parent audit record for the login event.
  • FND_LOGIN_RESPONSIBILITIES — tracks responsibilities associated with a login, complementing LOGIN_RESP_ID.
  • FND_LOGIN_RESP_FORMS — records Forms activity for the same login context.
  • FND_USER — resolves the user identity behind the login.
  • FND_RESPONSIBILITY — resolves the responsibility named by LOGIN_RESP_ID.

Together these objects provide a complete audit picture spanning both Forms and non-Forms sessions.