Search Results fnd_form_sessions_v

Overview

FND_FORM_SESSIONS_V is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the FND — Application Object Library product and consolidates real-time session, user, responsibility, form, and database session information into a single queryable structure. The view answers the operational question of which users are currently signed in, which responsibility and form they are executing, and which database process and session back that activity.

Because it resolves active form sessions through join logic spanning the FND login tables and GV$SESSION, it is widely used by DBAs and technical consultants for monitoring, diagnostics, and the construction of concurrent programs or reports that surface live user activity without requiring direct inspection of the underlying tables. The view is defined with an "active only" filter — each of the login, responsibility, and form link records must have a null END_TIME — so the result set reflects sessions in progress at query time.

Underlying Base Objects

The view is defined over seven documented base objects, all referenced through APPS synonyms:

• FND_LOGINS (aliased L) — one row per login session, supplying USER_ID, TERMINAL_ID, LOGIN_NAME, PID, and PROCESS_SPID.
• FND_LOGIN_RESPONSIBILITIES (aliased R) — the responsibility chosen within that login, supplying RESP_APPL_ID, RESPONSIBILITY_ID, and START_TIME.
• FND_LOGIN_RESP_FORMS (aliased F) — the form opened under that responsibility, supplying FORM_ID, FORM_APPL_ID, AUDSID, and START_TIME.
• FND_USER (USR), FND_RESPONSIBILITY_TL (RSP), and FND_FORM_TL (FRM) — translation and descriptive tables resolving user name, responsibility name, and form name.
• GV$SESSION (S) — the database session view, joined on F.AUDSID = S.AUDSID, supplying SID, SERIAL#, and INST_ID.

The joins are chained through LOGIN_ID and LOGIN_RESP_ID, and the translation tables are restricted to the caller's language via USERENV('LANG').

Key Columns

• USER_ID, USER_NAME, LOGIN_NAME — identify the logged-in application user.
• TERMINAL_ID — the client terminal or machine from which the session originated.
• RESP_APPL_ID, RESPONSIBILITY_ID, RESPONSIBILITY_NAME — the active responsibility context.
• FORM_ID, FORM_APPL_ID, USER_FORM_NAME — the form currently open.
• PID, PROCESS_SPID — the Forms process identifier and its operating-system process ID.
• AUDSID — the audit session identifier, the principal join key to GV$SESSION.
• SID, SERIAL#, INST_ID — the database session identifiers, essential for session-level diagnostics and RAC-aware queries.
• TIME — derived via NVL(F.START_TIME, NVL(R.START_TIME, L.START_TIME)), providing the most granular available start timestamp.

Common Use Cases and Queries

Typical scenarios include monitoring concurrent user load, identifying who occupies a specific form, and locating the database session behind a hung Forms process.

• List all active form sessions with user, responsibility, and form:

  SELECT USER_NAME, RESPONSIBILITY_NAME, USER_FORM_NAME, SID, SERIAL#
  FROM   APPS.FND_FORM_SESSIONS_V
  ORDER  BY USER_NAME;

• Find the database session for a specific user:

  SELECT SID, SERIAL#, AUDSID, PROCESS_SPID, TIME
  FROM   APPS.FND_FORM_SESSIONS_V
  WHERE  USER_NAME = :user_name;

• Count active sessions per responsibility for load analysis:

  SELECT RESPONSIBILITY_NAME, COUNT(*)
  FROM   APPS.FND_FORM_SESSIONS_V
  GROUP  BY RESPONSIBILITY_NAME
  ORDER  BY 2 DESC;