Search Results jai_cmn_rg_round_hdrs




Overview
Explore in AI Chat

Overview

The FND_LOGINS table is a core audit and security table within the Oracle E-Business Suite (EBS) Application Object Library (FND). It serves as the central repository for tracking user sign-on sessions to the application. Its primary role is to maintain a historical and current record of who accessed the system, when the session began, and its status. This data is fundamental for security auditing, monitoring user activity, and supporting various concurrent processing and application functions that require a reference to a specific user login context. The table is owned by the APPLSYS schema and is valid across major EBS releases, including 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to capture essential login session metadata. The primary key is LOGIN_ID, a unique identifier for each login session record. A critical foreign key is USER_ID, which links to the FND_USER table to identify the specific application user. Another significant column is SUBMITTED_LOGIN_ID, which creates a self-referential foreign key, potentially used to link related login sessions or track session inheritance. While the provided metadata does not list all columns, typical and important columns in FND_LOGINS include START_TIME (the session commencement timestamp), END_TIME (for terminated sessions), and STATUS (indicating whether the session is active or ended). These columns collectively provide a complete audit trail of user access.

Common Use Cases and Queries

The primary use case for FND_LOGINS is security and access reporting. System administrators frequently query this table to generate reports on user activity, identify concurrent user counts, or investigate access patterns. It is also integral to the system's internal mechanics, as evidenced by its numerous foreign key relationships with concurrent processing tables. Common analytical queries include identifying active sessions or auditing a specific user's login history.

  • Finding currently active sessions: SELECT USER_ID, START_TIME FROM APPLSYS.FND_LOGINS WHERE END_TIME IS NULL;
  • Auditing login history for a user: SELECT LOGIN_ID, START_TIME, END_TIME FROM APPLSYS.FND_LOGINS WHERE USER_ID = (SELECT USER_ID FROM FND_USER WHERE USER_NAME = '&USERNAME');
  • Investigating session details for a concurrent request: SELECT fl.* FROM FND_CONCURRENT_REQUESTS fcr, FND_LOGINS fl WHERE fcr.CONC_LOGIN_ID = fl.LOGIN_ID AND fcr.REQUEST_ID = &REQUEST_ID;

Related Objects

As indicated by the extensive foreign key metadata, FND_LOGINS is a foundational table referenced by many components within EBS. Its most direct relationship is with the FND_USER table for user identification. Crucially, it is heavily referenced by the concurrent processing subsystem. The CONC_LOGIN_ID column in FND_CONCURRENT_REQUESTS ties every submitted job to a specific login session. Furthermore, numerous configuration and setup tables for concurrent processing, such as FND_CONC_PP_ACTIONS, FND_CONC_RELEASE_CLASSES, and FND_CONC_RELEASE_PERIODS, use a LAST_UPDATE_LOGIN foreign key to FND_LOGINS to audit changes. This wide network of dependencies underscores its role in maintaining audit integrity across both user interactions and background processing.