FND User Login History
Description:
Audit history of application user logins.
EBS user logon audit is controlled by profile ‘Sign-On:Audit Level’. The most detailed audit level setting is ‘FORM’. Unfortunately, this audit tracks access to individual forms only, but not to different JSPs (HTML / OAF / ADF Pages). As a workaround, the report SQL also joins to icx_sessions, which contains a record for each login (in fact, it also stores a record for each access to the login page before login. These records are marked with guest=’Y’). The function retrieved from icx_session however, just shows the latest OAF function accessed by the user, not all individual JSP functions accessed within that session.
Parameters
Responsibility Name, Form Name, User Name, Logged in within Days, Date From, Date To, Restrict to incremental data, Incremental Alert Mode, Exclude User Name, Include Geolocation
Used tables
per_security_profiles, hr_operating_units, per_organization_list, hr_all_organization_units_vl, per_all_assignments_f, fnd_profile_option_values, fnd_logins, fnd_login_responsibilities, fnd_login_resp_forms, fnd_form_vl, fnd_appl_sessions, icx_sessions, fnd_nodes, fnd_form_functions_vl, fnd_user, fnd_responsibility_vl, prof, gv$session
Categories
Dependencies
If you would like to try one of these Oracle EBS SQLs without having Blitz Report installed, note that some of the reports require functions from utility package xxen_util.
Example Report
FND User Login History 24-Jul-2021 233519.xlsx
Report SQL
www.enginatics.com/reports/fnd-user-login-history/
Blitz Report™ import options
FND User Login History - Case Study
Executive Summary
The FND User Login History report is an essential security and auditing tool for Oracle E-Business Suite. It provides a detailed historical record of user access to the system, including login times, logout times, and the specific responsibilities accessed. This report is vital for IT security teams, auditors, and system administrators to ensure compliance with regulatory standards (such as SOX or GDPR), monitor user adoption, and investigate potential security breaches.
Business Challenge
Tracking “who did what and when” is a fundamental requirement for enterprise systems. However, Oracle EBS login data is often scattered across multiple tables depending on the access method (Forms vs. Self-Service Web Applications).
- Compliance Gaps: Auditors require proof of access controls and review of user activity.
- Security Monitoring: Detecting unauthorized access attempts or unusual login patterns (e.g., logins during non-business hours) is difficult without consolidated data.
- License Management: Organizations need to know which users are active to optimize license usage.
Solution
The FND User Login History report bridges the gap between Forms-based and Web-based login auditing. It consolidates data from the underlying FND (Foundation) and ICX (Inter-Cartridge Exchange) tables to provide a unified view of user sessions.
Key Features:
- Unified Audit Trail: Combines data for both Forms (Java Applet) and OAF (HTML) sessions.
- Detailed Metrics: Includes User Name, Responsibility, Login Time, Logout Time, and IP Address (if captured).
- Flexible Filtering: Allows searching by User, Date Range, Responsibility, or specific time windows.
- Session Context: Can identify if a session was terminated normally or timed out.
Technical Architecture
The report’s logic handles the complexity of Oracle’s dual-layer architecture (Forms vs. Web).
Primary Tables:
fnd_logins: Stores information about Forms-based logins. Populated based on the “Sign-On:Audit Level” profile option.icx_sessions: Stores information about web-based sessions (OAF, HTML).fnd_user: Master table for user definitions.fnd_responsibility_vl: Master table for responsibility definitions.fnd_login_responsibilities: Links logins to the specific responsibilities accessed during that session.
Key Logic:
- Audit Levels: The report output depends heavily on the
Sign-On:Audit Levelprofile option.- NONE: No auditing.
- USER: Tracks logins only.
- RESPONSIBILITY: Tracks logins and responsibility selection.
- FORM: Tracks logins, responsibilities, and forms opened.
- Join Logic: The query attempts to correlate
icx_sessionswithfnd_loginsto present a complete picture of the user’s journey from the web login page to the Forms interface.
Frequently Asked Questions
Q: Why are some logout times missing? A: If a user closes their browser without clicking “Logout,” or if the session crashes, the logout time may not be recorded properly. The system eventually marks these as timed out, but the timestamp might be null or delayed.
Q: Does this report show which specific records a user modified? A: No. This report tracks access (logins and responsibilities). To track record-level changes (inserts, updates), you need to use FND Audit Trail or Database Auditing features.
Q: Why do I see records for the ‘GUEST’ user?
A: The ‘GUEST’ user is used internally by Oracle EBS for anonymous access (like the initial login page). The report typically filters these out or identifies them separately, but they are a normal part of icx_sessions.
Q: How far back does the history go? A: It depends on your system’s purge policies. The “Purge Signon Audit Data” concurrent program is usually scheduled to remove old records to save space. The report can only show data that hasn’t been purged.
Oracle E-Business Suite Reporting Library
We provide an open source Oracle EBS SQLs as a part of operational and project implementation support toolkits for rapid Excel reports generation.
Blitz Report™ is based on Oracle EBS forms technology, and hence requires minimal training. There are no data or performance limitations since the output files are created directly from the database without going through intermediate file formats such as XML.
Blitz Report can be used as BI Publisher and Oracle Discoverer replacement tool. Standard Oracle BI Publisher and Discoverer reports can also be imported into Blitz Report for immediate output to Excel. Typically, reports can be created and version tracked within hours instead of days. The concurrent request output automatically opens upon completion without the need for re-formatting.
The Filters, Columns, Rows and Values fields are used to create and deliver the data in pivot table format with full drill down to details.

The Excel template upload functionality in Blitz Report allows users to create their own layouts by uploading an Excel template with additional sheets and charts, automatically refreshed when the report runs again. This allows to create custom dashboards and more advanced visualizations of report data.

You can download and use Blitz Report free of charge for your first 30 reports.
The installation and implementation process usually takes less than 1 hour; you can refer to our installation and user guides for specific details.
If you would like to optimize your Oracle EBS implementation and or operational reporting you can visit www.enginatics.com to review great ideas and example usage in blog. Or why not try for yourself in our demo environment.
Useful Links
Blitz Report™ – World’s fastest data upload and reporting for Oracle EBS
Oracle Discoverer replacement – importing worksheets into Blitz Report™
Blitz Report™ Questions & Answers
Supply Chain Hub by Blitz Report™
© 2025 Enginatics