Results for “fnd_resp_functions”

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

Overview

FND_RESP_FUNCTIONS is a core function security table in the Oracle E-Business Suite Application Object Library (product FND), owned by the APPLSYS schema. It records the rules that bind a responsibility to specific form functions or menus, allowing administrators to include or exclude accessed functionality for users assigned to a given responsibility. In practical terms, it is the exclusion/inclusion layer that sits beneath menu-driven navigation, determining which executable functions and submenus a responsibility may invoke.

The table participates in the function security model alongside FND_RESPONSIBILITY and FND_FORM_FUNCTIONS. The ETRM metadata classifies this object heuristically as a link in Data Vault terms, which is an appropriate modeling suggestion: it resolves a many-to-many relationship between responsibilities and the functions/menus they are permitted to reference, with the RULE_TYPE column carrying the discriminating context (for example, granting or excluding an action).

Key Information Stored

The documented physical schema contains 10 columns. The most significant include:

• APPLICATION_ID — Identifies the application context; part of the primary key and the foreign key to FND_RESPONSIBILITY.
• RESPONSIBILITY_ID — The responsibility to which the rule applies; the second component of the primary key.
• ACTION_ID — The function or menu being governed; foreign key to both FND_FORM_FUNCTIONS and FND_MENUS.
• RULE_TYPE — Qualifies the nature of the security rule (the discriminator between include/exclude semantics); part of the primary key.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing change history and session context.
• CREATION_DATE, CREATED_BY — WHO audit columns recording initial insertion.
• ZD_EDITION_NAME — The editioning column used by the Online Patching (ADOP) infrastructure in EBS 12.2.x to isolate runtime editions.

The surrogate primary key is FND_RESP_FUNCTIONS_PK, defined on (APPLICATION_ID, RESPONSIBILITY_ID, RULE_TYPE, ACTION_ID). The unique business-key candidate FND_RESP_FUNCTIONS_U1 extends this set with ZD_EDITION_NAME, reflecting the 12.2.x editioning model. Note that the PK set does not rely on a single generated column; the business identity is inherently composite.

Common Use Cases and Queries

Typical uses include auditing which functions a responsibility can access, validating security configuration during upgrades or implementations, and troubleshooting "function not available" issues reported by users.

To list all function rules for a responsibility:

• SELECT r.RESPONSIBILITY_NAME, rf.ACTION_ID, rf.RULE_TYPE FROM FND_RESP_FUNCTIONS rf JOIN FND_RESPONSIBILITY r ON rf.APPLICATION_ID = r.APPLICATION_ID AND rf.RESPONSIBILITY_ID = r.RESPONSIBILITY_ID WHERE r.RESPONSIBILITY_NAME = :name;

To resolve the governed function or menu:

• LEFT JOIN FND_FORM_FUNCTIONS ff ON rf.ACTION_ID = ff.FUNCTION_ID and LEFT JOIN FND_MENUS m ON rf.ACTION_ID = m.MENU_ID;

Reporting queries commonly join to FND_FORM_FUNCTIONS to translate ACTION_ID into a user-friendly function name, and to FND_MENUS to expand submenu grants. Security review scripts frequently filter by RULE_TYPE to separate inclusion rules from exclusion rules.

Related Objects

The most significant related objects, per documented foreign keys, are:

• FND_RESPONSIBILITY — joined on APPLICATION_ID and RESPONSIBILITY_ID; the parent entity defining the responsibility.
• FND_FORM_FUNCTIONS — joined on ACTION_ID; provides the function definition for executable actions.
• FND_MENUS — joined on ACTION_ID; provides the menu definition when the action is a submenu rather than a discrete function.

These three tables, together with FND_USER and the responsibility assignment tables (FND_USER_RESP_GROUPS), form the essential security graph. Administrators and DBAs use them jointly to reconstruct effective function security for any user.