Search Results fnd_logins_pk

Overview

FND_LOGINS is the sign-on audit table in the Oracle E-Business Suite Application Object Library (FND) product family, owned by the APPLSYS schema. It records information about who signs on to an application and when, functioning as the authoritative repository for authentication session history across the EBS instance. Each row represents a discrete sign-on event, capturing the user identity, the session start and end timestamps, and the low-level operating system and database session identifiers associated with that connection. Because both concurrent managers and online users authenticate through the same FND security infrastructure, FND_LOGINS serves as the common audit backbone for interactive and batch activity alike.

From a dimensional modeling perspective, the mined foreign-key structure classifies FND_LOGINS as hub-leaning. This suggests treating LOGIN_ID as a durable business hub key, with user and session attributes modeled as satellites and the self-referencing submitted-login relationship as a recursive or hierarchical link. This classification is a heuristic recommendation rather than a documented physical constraint.

Key Information Stored

The table is defined with 13 documented columns. The primary key is FND_LOGINS_PK on LOGIN_ID, and a unique index FND_LOGINS_U1 also exists on LOGIN_ID, making it the sole documented business-key candidate. The most significant columns include:

• LOGIN_ID — Surrogate primary key uniquely identifying each sign-on event.
• USER_ID — Foreign key to FND_USER identifying the authenticated user.
• START_TIME — Timestamp at which the session began.
• END_TIME — Timestamp at which the session terminated; null for active sessions.
• LOGIN_NAME — The login name captured at authentication time.
• SESSION_NUMBER — Database session identifier associated with the connection.
• SERIAL# — Database session serial number, paired with SESSION_NUMBER for unique session identification.
• PID — Operating system process identifier of the client or server process.
• SPID — Operating system session process identifier.
• PROCESS_SPID — Additional process identifier used for concurrent processing diagnostics.
• TERMINAL_ID — Identifier of the terminal or workstation from which the login originated.
• SUBMITTED_LOGIN_ID — Self-referencing foreign key to FND_LOGINS, linking a derived session to its originating login.
• LOGIN_TYPE — Classification of the sign-on, distinguishing interactive from non-interactive access.

Common Use Cases and Queries

FND_LOGINS is the primary source for sign-on auditing, security forensics, and concurrency analysis. Typical reporting includes identifying users with multiple concurrent sessions, detecting logins outside business hours, and reconciling concurrent request activity to the initiating session.

A representative query joins the login audit to user details:

• SELECT l.login_id, u.user_name, l.start_time, l.end_time, l.terminal_id FROM fnd_logins l, fnd_user u WHERE l.user_id = u.user_id AND l.start_time >= :from_date;
• SELECT user_id, COUNT(*) FROM fnd_logins WHERE end_time IS NULL GROUP BY user_id; — identifies potentially orphaned or still-active sessions.
• SELECT * FROM fnd_logins WHERE submitted_login_id IS NOT NULL; — traces derived sessions back to their parent login.

Related Objects

FND_LOGINS participates in extensive referential relationships across the APPLSYS and application schemas. The most significant dependent objects include:

• FND_USER — Referenced via FND_LOGINS.USER_ID; supplies the authenticated user identity.
• FND_LOGIN_RESPONSIBILITIES — References FND_LOGINS.LOGIN_ID, recording the responsibilities active during each login.
• FND_CONCURRENT_REQUESTS — References FND_LOGINS via CONC_LOGIN_ID, tying concurrent requests to their initiating session.
• ICX_SESSIONS and FND_APPL_SESSIONS — Both reference FND_LOGINS.LOGIN_ID, linking web and application sessions to the audit record.
• FND_SELAUDIT_LOG — References FND_LOGINS.LOGIN_ID for self-service audit tracking.
• FND_OAM_GCS_JOBS — References FND_LOGINS.LOGIN_ID in the Oracle Applications Manager framework.
• MTL_PER_CLOSE_DTLS — References FND_LOGINS.LOGIN_ID, associating inventory period-close activity with a login.
• Multiple FND_CONC_* tables — Numerous concurrent-processing configuration tables carry LAST_UPDATE_LOGIN foreign keys to FND_LOGINS, providing update attribution.

Applications outside FND, such as JAI (India Localization) and JG (Global Taxation) tables, also reference FND_LOGINS via PROGRAM_LOGIN_ID, demonstrating its role as the instance-wide login audit anchor.