Results for “fnd_user_resp_groups”

50+ results




Overview
Explore in AI Chat

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

Overview

FND_USER_RESP_GROUPS is an APPS-owned reporting view in Oracle E-Business Suite, defined within the FND – Application Object Library product. Although its name suggests a direct projection of the legacy FND_USER_RESP_GROUPS base table that exists in earlier releases, the ETRM definition for 12.2.2 describes a compatibility or migration-oriented view constructed from the Workflow role-assignment model rather than from the base user-responsibility table itself. Its documented status is VALID, and it is owned by the APPS schema.

The view presents a user-to-responsibility association in which each row links an FND_USER record to a responsibility identified through the WF_USER_ROLES and WF_USER_ROLE_ASSIGNMENTS_V views. Because responsibility assignments in Release 12 are increasingly represented as role assignments in the Workflow directory, this view provides a SQL-accessible projection of those assignments in a shape resembling the historical FND_USER_RESP_GROUPS columns. It is therefore useful for reporting, migration validation, and integration queries that expect the legacy column layout while reading the Role-Based Access Control (RBAC) model.

Underlying Base Objects

The ETRM metadata documents the following referenced objects: FND_APPLICATION (synonym), FND_DATE (package), FND_SECURITY_GROUPS (synonym), FND_USER (synonym), WF_USER_ROLES (view), and WF_USER_ROLE_ASSIGNMENTS_V (view). The view text joins FND_USER to WF_USER_ROLE_ASSIGNMENTS_V on USER_NAME, and to WF_USER_ROLES on USER_NAME and ROLE_NAME, filtering WF_USER_ROLES to ROLE_ORIG_SYSTEM = 'FND_RESP' and PARTITION_ID = 2 so that only FND responsibility roles are returned.

The FND_APPLICATION and FND_SECURITY_GROUPS objects are resolved by parsing the responsibility role name: the segment between the first and second vertical-bar separators yields the application short name, and the segment after the third separator yields the security group key. FND_DATE.CANONICAL_TO_DATE is called to supply a fixed START_DATE of 1000/01/01. END_DATE, DESCRIPTION, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN are all returned as NULL, reflecting that the Workflow assignment model does not carry these historical audit attributes.

Key Columns

  • USER_ID – Surrogate identifier of the user, taken from FND_USER.
  • RESPONSIBILITY_ID – Responsibility identifier, mapped from WF_USER_ROLES.ROLE_ORIG_SYSTEM_ID.
  • RESPONSIBILITY_APPLICATION_ID – Application identifier of the responsibility, resolved via FND_APPLICATION.APPLICATION_ID.
  • SECURITY_GROUP_ID – Security group identifier resolved from FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
  • START_DATE – Constant date derived from FND_DATE.CANONICAL_TO_DATE('1000/01/01'), representing an open-ended effective start.
  • END_DATE – Returned as NULL, indicating the assignment is not closed.
  • DESCRIPTION, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Placeholder columns returned as NULL for structural compatibility with the legacy view.

Common Use Cases and Queries

Typical scenarios include auditing which responsibilities a user holds, reconciling legacy FND_USER_RESP_GROUPS queries against the RBAC model, and feeding downstream integrations that expect the classic column layout. Because audit columns are NULL, the view is suited to current-state reporting rather than change history.

A representative query lists responsibilities for a given user:

  • SELECT user_id, responsibility_id, responsibility_application_id, security_group_id FROM apps.fnd_user_resp_groups WHERE user_id = :p_user_id;
  • SELECT furg.user_id, fu.user_name, fa.application_short_name FROM apps.fnd_user_resp_groups furg, apps.fnd_user fu, apps.fnd_application fa WHERE furg.user_id = fu.user_id AND furg.responsibility_application_id = fa.application_id;

Joining to FND_RESPONSIBILITY on RESPONSIBILITY_ID and RESPONSIBILITY_APPLICATION_ID yields responsibility names, while joins to FND_USER provide user names and related attributes.