Results for “fnd_responsibility”

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

Overview

FND_RESPONSIBILITY is the core Application Object Library (FND) table that defines every responsibility available in an Oracle E-Business Suite instance. Owned by the APPLSYS schema, it is the central registry in which each responsibility is catalogued and bound to an application, a menu, a request group, and a data group. Because responsibilities are the mechanism through which users are granted access to forms, functions, concurrent programs, and organization-level data, this table sits at the heart of the EBS security and navigation model. It is present and structurally consistent in both release 12.1.1 and 12.2.2; the 12.2.2 documented schema adds the ZD_EDITION_NAME column that supports online patching editioning.

A data-modeling heuristic classifies FND_RESPONSIBILITY as a hub: it is the durable, centrally-referenced entity that many surrounding transactional and configuration objects point to by foreign key. Its primary key is the composite FND_RESPONSIBILITY_PK on (APPLICATION_ID, RESPONSIBILITY_ID). Two unique indexes act as business-key candidates: FND_RESPONSIBILITY_U1 on (APPLICATION_ID, RESPONSIBILITY_ID, ZD_EDITION_NAME) and FND_RESPONSIBILITY_U2 on (RESPONSIBILITY_KEY, APPLICATION_ID, ZD_EDITION_NAME). The 20-column physical definition is registered as VALID in the ETRM repository.

Key Information Stored

The table stores descriptive, navigational, and security-relevant attributes for each responsibility. The most significant columns are:

• APPLICATION_ID and RESPONSIBILITY_ID — the composite surrogate primary key (FND_RESPONSIBILITY_PK) identifying the owning application and the responsibility itself.
• RESPONSIBILITY_KEY — the developer-facing unique short name; part of the business-key candidate index FND_RESPONSIBILITY_U2.
• MENU_ID — foreign key to FND_MENUS, defining the navigation menu presented when the responsibility is selected.
• DATA_GROUP_APPLICATION_ID and DATA_GROUP_ID — identify the data group governing the Oracle IDs and application data visible to the responsibility; foreign key to FND_DATA_GROUP_UNITS.
• GROUP_APPLICATION_ID and REQUEST_GROUP_ID — bind the responsibility to a request group; foreign key to FND_REQUEST_GROUPS.
• TERM_SECURITY_ENABLED_FLAG — controls whether a terminal/network security check applies.
• START_DATE and END_DATE — the effective life of the responsibility, used to enable or disable it over time.
• VERSION, WEB_HOST_NAME, and WEB_AGENT_NAME — versioning and web-tier routing attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ZD_EDITION_NAME — the online-patching edition discriminator present in 12.2.2.

Translatable text (name and description) resides in the companion table FND_RESPONSIBILITY_TL, which shares the same composite key.

Common Use Cases and Queries

Typical uses include auditing responsibility definitions, resolving a responsibility to the menu and permissions it grants, and joining user-responsibility assignments to security analysis. Standard query patterns resolve the localized name through FND_RESPONSIBILITY_TL:

• List all responsibilities and their owning applications:
  • SELECT r.responsibility_id, r.responsibility_key, t.responsibility_name, r.application_id FROM fnd_responsibility r, fnd_responsibility_tl t WHERE r.application_id = t.application_id AND r.responsibility_id = t.responsibility_id AND t.language = USERENV('LANG');
• Determine the menu and request group attached to a responsibility using the MENU_ID and REQUEST_GROUP_ID keys.
• Identify users holding a given responsibility by joining to FND_USER_RESP_GROUPS (a typical extension of the FK graph toward users).
• Filter responsibilities valid as of a date using START_DATE and END_DATE.
• Analyze the security footprint of a responsibility through FND_RESP_FUNCTIONS and AK_RESP_SECURITY_ATTRIBUTES.

Because the table is editioned in 12.2.2, queries should generally filter or exclude rows where ZD_EDITION_NAME is not null, unless the intent is to inspect a specific patch edition.

Related Objects

FND_RESPONSIBILITY participates in a dense foreign-key network. The most significant related objects are:

• FND_RESPONSIBILITY_TL — translated name/description, joined on (APPLICATION_ID, RESPONSIBILITY_ID).
• FND_MENUS — menu definition referenced by FND_RESPONSIBILITY.MENU_ID.
• FND_REQUEST_GROUPS — request group bound via GROUP_APPLICATION_ID and REQUEST_GROUP_ID.
• FND_DATA_GROUP_UNITS — data group referenced by DATA_GROUP_APPLICATION_ID and DATA_GROUP_ID.
• FND_RESP_FUNCTIONS — functions granted to a responsibility (APPLICATION_ID, RESPONSIBILITY_ID).
• FND_LOGIN_RESPONSIBILITIES — login tracking via RESP_APPL_ID and RESPONSIBILITY_ID.
• FND_PROFILE_OPTION_VALUES — responsibility-level profile settings via LEVEL_VALUE_APPLICATION_ID and LEVEL_VALUE.
• SO_HOLD_AUTHORIZATIONS — sales-order hold release authority referenced by RESPONSIBILITY_ID.
• OE_HOLD_AUTHORIZATIONS — order-entry hold authority referenced by APPLICATION_ID.
• ORG_ACCESS — organization access records keyed by RESP_APPLICATION_ID.

Together, these relationships make FND_RESPONSIBILITY the principal hub through which EBS access control, navigation, and reporting authority are reconciled.