Search Results fnd_login_responsibilities




Overview
Explore in AI Chat

Overview

The FND_LOGIN_RESPONSIBILITIES table is a core audit table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS). It functions as a detailed log, recording each instance where a user activates or switches to a specific responsibility during an application session. This table is integral to the Sign-On Audit functionality, providing a granular, responsibility-level audit trail that complements the higher-level session data stored in FND_LOGINS. Its primary role is to support security monitoring, compliance reporting, and forensic analysis of user activity within the EBS environment by tracking precisely which responsibilities users access and when.

Key Information Stored

The table's structure is designed to link a user session to a specific responsibility and capture the timing of its use. The primary key is a composite of LOGIN_ID and LOGIN_RESP_ID, ensuring a unique record for each responsibility activation within a session. Key columns include LOGIN_ID, which foreign-key references FND_LOGINS to tie the record to a user's sign-on session; LOGIN_RESP_ID, a sequential identifier for responsibility changes within that session; and the responsibility identifiers RESP_APPL_ID and RESPONSIBILITY_ID, which foreign-key reference FND_RESPONSIBILITY to specify the exact responsibility accessed. Critical audit columns such as START_TIME and END_TIME record the duration the responsibility was active, providing essential data for usage analysis.

Common Use Cases and Queries

A primary use case is generating audit reports for compliance, detailing which users accessed sensitive responsibilities and for how long. System administrators often query this table to investigate specific user activity or to analyze responsibility usage patterns. Common SQL patterns include joining to FND_LOGINS and FND_USER for user details, and to FND_RESPONSIBILITY_TL for the responsibility name. A typical query to list responsibility usage for a user would be:

  • SELECT fu.USER_NAME, frt.RESPONSIBILITY_NAME, flr.START_TIME, flr.END_TIME FROM APPLSYS.FND_LOGIN_RESPONSIBILITIES flr JOIN APPLSYS.FND_LOGINS fl ON flr.LOGIN_ID = fl.LOGIN_ID JOIN APPLSYS.FND_USER fu ON fl.USER_ID = fu.USER_ID JOIN APPLSYS.FND_RESPONSIBILITY fr ON (flr.RESP_APPL_ID = fr.APPLICATION_ID AND flr.RESPONSIBILITY_ID = fr.RESPONSIBILITY_ID) JOIN APPLSYS.FND_RESPONSIBILITY_TL frt ON (fr.APPLICATION_ID = frt.APPLICATION_ID AND fr.RESPONSIBILITY_ID = frt.RESPONSIBILITY_ID AND frt.LANGUAGE = 'US') WHERE fu.USER_NAME = '&USERNAME' ORDER BY flr.START_TIME DESC;

This data is also foundational for custom security dashboards or integration with broader Security Information and Event Management (SIEM) systems.

Related Objects

FND_LOGIN_RESPONSIBILITIES is centrally connected to several key FND audit tables. It has a direct foreign key dependency on FND_LOGINS (via LOGIN_ID), which stores the master session record. It also references the FND_RESPONSIBILITY table (via RESP_APPL_ID and RESPONSIBILITY_ID) to resolve the responsibility key. Furthermore, it serves as a parent table to FND_LOGIN_RESP_FORMS, which provides an even deeper audit trail by logging individual forms accessed within each responsibility session. This hierarchy creates a comprehensive audit chain: from user login (FND_LOGINS), to responsibility activation (FND_LOGIN_RESPONSIBILITIES), down to form navigation (FND_LOGIN_RESP_FORMS).