Results for “responsibility”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The FND_LOGIN_RESPONSIBILITIES table is a core Sign-On Audit object within the Oracle E-Business Suite Application Object Library (FND). Owned by the APPLSYS schema, it records the responsibilities that a user selects during each authenticated session. Every time a user signs on to Oracle EBS and switches into a responsibility, a corresponding row is written to this table to capture the identity of the responsibility, the underlying application, and the timing of the session segment.

This table forms part of the broader sign-on auditing framework that supports security monitoring, session tracing, and compliance reporting. It captures the operational linkage between an authenticated login session (FND_LOGINS) and the responsibility that was active within that session. Because a single login can select multiple responsibilities across its lifetime, the table records multiple rows per login, with each row preceding the forms-level audit records in FND_LOGIN_RESP_FORMS.

Under the heuristic Data Vault classification derived from its foreign key structure, this object is satellite-leaning. It functions as an observational record attached to the FND_LOGINS hub, describing attributes and timing of responsibility selection rather than defining a new business entity or a clean many-to-many link between independent hubs.

Key Information Stored

The table contains eight documented columns. The most important ones are:

  • LOGIN_ID — Identifies the parent sign-on session in FND_LOGINS. Part of the composite primary key.
  • LOGIN_RESP_ID — A sequence-generated identifier unique per responsibility selection within a login. Part of the composite primary key.
  • RESP_APPL_ID — The application identifier owning the responsibility. Participates in the foreign key to FND_RESPONSIBILITY.
  • RESPONSIBILITY_ID — The responsibility itself. Together with RESP_APPL_ID, resolves to a specific FND_RESPONSIBILITY row.
  • START_TIME — Timestamp when the user entered the responsibility.
  • END_TIME — Timestamp when the user exited or switched away from the responsibility.
  • AUDSID — The Oracle session audit identifier, useful for correlating to database-level auditing.
  • RESOURCE_CONSUMER_GROUP — The database resource consumer group applied to the session, relevant for workload management and performance tuning.

The surrogate/business primary key is defined by FND_LOGIN_RESPONSIBILITIES_PK over (LOGIN_ID, LOGIN_RESP_ID). A parallel unique index, FND_LOGIN_RESPONSIBILITIES_U1, covers the same two columns and serves as the documented business-key candidate.

Common Use Cases and Queries

Typical uses center on audit, security, and performance analysis. Security teams query the table to determine which responsibilities a user exercised during a session, while auditors reconstruct sign-on history for compliance evidence.

A representative query joining login and responsibility metadata is:

  • SELECT l.USER_ID, r.RESPONSIBILITY_ID, r.RESP_APPL_ID, r.START_TIME, r.END_TIME FROM FND_LOGIN_RESPONSIBILITIES r JOIN FND_LOGINS l ON r.LOGIN_ID = l.LOGIN_ID WHERE l.USER_ID = :user_id ORDER BY r.START_TIME;

For session-duration and workload reporting, the START_TIME and END_TIME columns support elapsed-time calculations per responsibility, while AUDSID and RESOURCE_CONSUMER_GROUP support correlation with database activity and resource plans.

Related Objects

  • FND_LOGINS — Parent session table; joined on LOGIN_ID.
  • FND_RESPONSIBILITY — Responsibility definition table; joined via RESP_APPL_ID and RESPONSIBILITY_ID.
  • FND_LOGIN_RESP_FORMS — Child table capturing form-level audit detail, joined on LOGIN_ID and LOGIN_RESP_ID.

These three objects together form the primary audit trail supporting responsibility-level tracking in Oracle EBS 12.1.1 and 12.2.2.