Search Results fnd_logins_u1

Overview

APPLSYS.FND_LOGINS is a core Oracle E-Business Suite table that stores Sign-On Audit information. Each row records a discrete sign-on event, capturing who signed on to an application, when the session began and ended, and the underlying database and operating system process context. The table is owned by the APPLSYS schema and is designated as FND Design Data (FND.FND_LOGINS), confirming it as a seeded Oracle Application Object Library object rather than a customer extension. Its status is VALID across Oracle EBS 12.1.1 and 12.2.2.

FND_LOGINS underpins several foundational features within EBS: Sign-On Audit, the Help > About and Help > View My Account diagnostics, and the session-to-responsibility tracking used by FND_LOGIN_RESPONSIBILITIES. Concurrent processing also depends on it, since FND_CONCURRENT_REQUESTS records the originating session. From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as hub-leaning, reflected in its role as an anchor for login events with dependent references to FND_USER and self-referencing submitted logins.

Key Information Stored

The table carries 13 documented columns. The most significant are:

• LOGIN_ID — Surrogate primary key sourced from the FND_LOGINS_PK constraint and enforced uniquely by the FND_LOGINS_U1 index. Every dependent object references this identifier.
• USER_ID — Foreign key to FND_USER identifying the application user whose session this is.
• START_TIME / END_TIME — The beginning and end of the login session, used for duration and activity reporting.
• PID / SPID / PROCESS_SPID — Oracle process identifier, operating system process identifier, and the process-level SPID used to correlate concurrent manager and form sessions.
• SERIAL# — The database session serial number, useful for V$SESSION correlation.
• TERMINAL_ID / LOGIN_NAME — The originating terminal and the operating system login name used at sign-on.
• SESSION_NUMBER — The count of sign-ons for that user since the upgrade to Release 7, reflecting cumulative session usage.
• SUBMITTED_LOGIN_ID — Self-referencing foreign key identifying the login that submitted a concurrent request, distinguishing interactive logins from concurrent-driven ones.
• LOGIN_TYPE — Distinguishes the class of login recorded.

The unique index FND_LOGINS_U1 (LOGIN_ID) is the documented business-key candidate; FND_LOGINS_N1 (SPID) and FND_LOGINS_N2 (USER_ID) provide non-unique access paths used by diagnostics and auditing queries.

Common Use Cases and Queries

Typical use cases include sign-on auditing, active-session identification, concurrent request lineage, and troubleshooting orphaned or long-running sessions.

• Identify currently active sessions where END_TIME is null, joined to FND_USER for the username.
• Report sign-on frequency per user within a date range using START_TIME and SESSION_NUMBER.
• Trace which login submitted a specific concurrent request by joining FND_CONCURRENT_REQUESTS.CONC_LOGIN_ID to FND_LOGINS.LOGIN_ID.
• Reconcile an Oracle process by matching PID or SPID back to V$PROCESS or V$SESSION during performance investigations.
• Audit terminal and OS-level access patterns via TERMINAL_ID and LOGIN_NAME.

A sample pattern: SELECT l.login_id, u.user_name, l.start_time, l.end_time, l.spid FROM fnd_logins l, fnd_user u WHERE l.user_id = u.user_id AND l.end_time IS NULL;

Related Objects

FND_LOGINS sits at the center of a broad dependency graph. The most significant related objects and their join columns are:

• FND_USER — via FND_LOGINS.USER_ID; the primary user dimension.
• FND_LOGIN_RESPONSIBILITIES — via LOGIN_ID; records the responsibilities assumed during each session.
• FND_CONCURRENT_REQUESTS — via CONC_LOGIN_ID; ties concurrent programs to their originating login.
• ICX_SESSIONS — via LOGIN_ID; links Self-Service web sessions to the underlying login.
• FND_APPL_SESSIONS — via LOGIN_ID; tracks application server sessions.
• FND_SELAUDIT_LOG — via LOGIN_ID; provides self-service audit trail linkage.
• FND_LOGINS (self) — via SUBMITTED_LOGIN_ID; resolves concurrent-submitted logins.
• FND_OPS_INSTANCES, FND_REQUEST_SETS, FND_CONC_PP_ACTIONS — numerous FND objects reference LAST_UPDATE_LOGIN to capture the login that last modified configuration data.
• Multiple JAI_* tables (e.g., JAI_CMN_RG_ROUND_HDRS, JAI_RCV_TP_BATCHES) — via PROGRAM_LOGIN_ID for program-level audit.