Results for “fnd_login_resp_forms”

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

Overview

FND_LOGIN_RESP_FORMS is a core Sign-On Audit table residing in the APPLSYS schema of the Oracle E-Business Suite Application Object Library (FND). It records which forms were opened by a user, under which responsibility, and at what time, forming the detailed activity layer beneath the session-level audit trail maintained in FND_LOGIN_RESPONSIBILITIES. In both EBS 12.1.1 and 12.2.2, the table underpins the Sign-On Audit feature and is populated automatically by the Forms runtime when audit logging is enabled via profile options (for example, Sign-On:Audit Level). Because the row grain is one form invocation within a responsibility session, the table answers the operational question of "who ran which form, under which responsibility, and when."

From a Data Vault modeling perspective, the metadata's heuristic classification places this object as a link: it connects the responsibility-session context (via LOGIN_ID and LOGIN_RESP_ID) to the specific form executed (via FORM_APPL_ID and FORM_ID), and its foreign keys confirm these relationships against FND_LOGIN_RESPONSIBILITIES and FND_FORM. The presence of START_TIME, END_TIME, and AUDSID also gives the table satellite-like descriptive attributes describing each form usage event.

Key Information Stored

The documented physical schema contains nine columns. The composite primary key FND_LOGIN_RESP_FORMS_PK spans LOGIN_ID, LOGIN_RESP_ID, FORM_APPL_ID, FORM_ID, and START_TIME. These columns function as the primary identifier and also serve as the business-key candidates establishing "one form usage event per responsibility session at a point in time."

• LOGIN_ID — surrogate/business reference to the parent login session in FND_LOGIN_RESPONSIBILITIES.
• LOGIN_RESP_ID — reference to the specific responsibility chosen within that login session.
• FORM_APPL_ID — identifies the application to which the executed form belongs (joins to FND_FORM).
• FORM_ID — identifies the specific Oracle Forms screen or function invoked.
• START_TIME — timestamp when the form was opened; part of the primary key.
• END_TIME — timestamp when the form session terminated, used for duration analysis.
• AUDSID — Oracle session identifier at time of execution, useful for correlating with other auditing views such as FND_LOG or ASH-style diagnostics.
• ZOOM_LEVEL — drill-down or navigation depth indicator.
• RESOURCE_CONSUMER_GROUP — the database Resource Manager group active during the form session.

Columns such as START_TIME, END_TIME, ZOOM_LEVEL, AUDSID, and RESOURCE_CONSUMER_GROUP describe the event, while the remaining columns carry the foreign-key linkage.

Common Use Cases and Queries

Typical use cases include user activity reporting, form-level usage analytics, audit compliance, and performance or troubleshooting investigations. A standard query joins to the parent responsibility-session table and the form definition to render readable activity:

• Enumerate forms accessed in the last 24 hours, combining START_TIME filters with joins to FND_LOGIN_RESPONSIBILITIES (via LOGIN_ID, LOGIN_RESP_ID) and FND_FORM (via FORM_APPL_ID, FORM_ID).
• Compute average session duration using END_TIME - START_TIME to identify slow or long-running forms.
• Drill from a responsibility-level audit report into the exact forms a user opened, using LOGIN_ID and LOGIN_RESP_ID as the linkage.
• Correlate form executions with database sessions by matching AUDSID against diagnostics data.

A representative pattern: select the login identifiers, form identifiers, and timestamps from FND_LOGIN_RESP_FORMS, then join FND_LOGIN_RESPONSIBILITIES on LOGIN_ID and LOGIN_RESP_ID and FND_FORM on FORM_APPL_ID and FORM_ID, filtering on a START_TIME range. This yields form, responsibility, user, and duration in a single result set.

Related Objects

The following objects are the most significant references or dependencies:

• FND_LOGIN_RESPONSIBILITIES — parent session/responsibility table; joined on LOGIN_ID and LOGIN_RESP_ID.
• FND_FORM — form definition; joined on FORM_APPL_ID and FORM_ID.
• FND_LOGIN_RESP_FORMS_PK — the primary key constraint enforcing uniqueness of form usage events.
• FND_LOGINS — parent login table (via LOGIN_ID) supplying user and session context.
• FND_USER — identifies the user behind the login session.
• FND_APPLICATION — resolves FORM_APPL_ID to an application name for reporting.
• Sign-On Audit concurrent programs and reports in FND that read this table for audit output.
• Audit purge programs that remove historical rows based on retention policy.

Because the table is populated automatically by the runtime rather than through public APIs, direct query access is the normal integration path for reporting and compliance analysis.