Results for “fnd_user_resp_groups_direct”

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

Overview

FND_USER_RESP_GROUPS_DIRECT is a VALID view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the FND - Application Object Library product. It presents the direct (non-ANY) responsibility and responsibility group assignments granted to application users. In EBS 12.1.1 and 12.2.2, user-to-responsibility data is physically modeled through the Oracle Workflow role-assignment tables rather than through a dedicated security table, and this view abstracts that model into a familiar, report-friendly shape keyed by USER_ID and RESPONSIBILITY_ID.

The view is the workhorse behind the "User Responsibilities" and "Users by Responsibility" style reports and is frequently referenced by forms, concurrent programs, and custom SQL that need a clean listing of who has what access. Because it resolves the Workflow role name into a numeric responsibility application identifier and a security group identifier, it lets reporting tools join directly to FND_APPLICATION, FND_RESPONSIBILITY, and FND_SECURITY_GROUPS without parsing delimited role strings.

Underlying Base Objects

The documented referenced base objects are FND_APPLICATION (synonym), FND_SECURITY_GROUPS (synonym), FND_USER (synonym), WF_ALL_USER_ROLES (view), and WF_USER_ROLE_ASSIGNMENTS (synonym). The view's driving join is between FND_USER and WF_USER_ROLE_ASSIGNMENTS, matched on USER_NAME, filtered to RELATIONSHIP_ID = -1, which denotes the direct-assignment relationship. WF_ALL_USER_ROLES supplies the corresponding role metadata and is constrained to ROLE_ORIG_SYSTEM = 'FND_RESP'.

Responsibility role names in Workflow follow the delimited pattern FND_RESP|<Application Short Name>|<Responsibility Key>|<Security Group Key>. The view parses these segments with SUBSTR/INSTR and translates the application short name through a scalar subquery on FND_APPLICATION and the security group key through a subquery on FND_SECURITY_GROUPS. Assignments whose role name ends in |ANY are explicitly excluded, which is why the view is described as "direct." Because the role attribute is delimited text, the literal %COL is replaced with : to reconstruct any colon-containing keys.

Key Columns

• USER_ID — Numeric identifier of the assigned user, from FND_USER.
• RESPONSIBILITY_ID — The responsibility identifier, taken from WUR.ROLE_ORIG_SYSTEM_ID.
• RESPONSIBILITY_APPLICATION_ID — Application identifier resolved from the short name embedded in the role name; joins to FND_APPLICATION.
• SECURITY_GROUP_ID — Security group identifier resolved from the fourth role segment; null for assignments without a qualifying group.
• START_DATE / END_DATE — Effective dating of the assignment, sourced from WF_USER_ROLE_ASSIGNMENTS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns reflecting who granted or last modified the assignment.
• DESCRIPTION — Populated from ASSIGNMENT_REASON, capturing the reason recorded when the responsibility was assigned.

Common Use Cases and Queries

Typical uses include access certification, segregation-of-duties analysis, migration validation, and responsibility-usage reporting. A minimal listing of active assignments:

• SELECT user_id, responsibility_id, responsibility_application_id, security_group_id, start_date, end_date FROM apps.fnd_user_resp_groups_direct;

Joining to FND_USER and FND_RESPONSIBILITY to produce a readable access report:

• SELECT fu.user_name, fr.responsibility_name FROM apps.fnd_user_resp_groups_direct d, apps.fnd_user fu, apps.fnd_responsibility_vl fr WHERE d.user_id = fu.user_id AND d.responsibility_id = fr.responsibility_id AND d.responsibility_application_id = fr.application_id;

Because the view excludes ANY roles, it should be paired with the related FND_USER_RESP_GROUPS view when the complete assignment picture, including shared ANY grants, is required.