Results for “fnd_resp”

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

Overview

APPS.FND_RESP_SEC_UR is a reporting view in the Oracle E-Business Suite that presents a unified, de-normalized listing of user-to-responsibility assignments together with the security group that governs each assignment. In the context of EBS 12.1.1 and 12.2.2, this view is significant because the runtime responsibility assignment data that historically lived in FND_USER_RESP_GROUPS was migrated to the FND_USER_RESP_GROUPS_OLD table during the transition to the newer role-based security model (the "UMX"/RBAC model introduced with 12.1.3 and refined in 12.2). The view name itself — _UR for "User Role" — reflects this: it exposes legacy user/responsibility/security-group rows in a shape compatible with Oracle's user-role reporting conventions.

Practically, the view answers the question "which responsibilities has each user been granted, under which security group, and when?" It is therefore used for access reviews, segregation-of-duties audits, and migration diagnostics when comparing pre- and post-upgrade responsibility assignments.

Underlying Base Objects

The ETRM metadata documents the view as owned by APPS and defined over five objects, all referenced through synonyms:

• FND_USER_RESP_GROUPS_OLD — the legacy junction table holding one row per user/responsibility/security-group assignment, including its validity dates.
• FND_USER — the user account master, supplying the user name, employee association, and user-level start/end dates.
• FND_RESPONSIBILITY — the responsibility definition master, supplying the responsibility key, application, and role-level dates.
• FND_APPLICATION — the application registry, supplying the application short name used to build the canonical role name.
• FND_SECURITY_GROUPS — the security group definitions that scope each responsibility assignment.

The view body is a UNION of two equivalent queries that differ only in how the role_name and role_orig_system identifiers are constructed — one using the application short name and responsibility key, the other using the numeric application and responsibility IDs. Both branches read from FND_USER_RESP_GROUPS_OLD, confirming that this view is explicitly a legacy-compatibility construct.

Key Columns

• USER_NAME — the login name from FND_USER.
• USER_ORIG_SYSTEM / USER_ORIG_SYSTEM_ID — indicates whether the user maps to a person (PER) or a pure FND user (FND_USR), derived by decoding EMPLOYEE_ID. This supports integration with Oracle User Management.
• ROLE_NAME — a composite key of the form FND_RESP|<APP_SHORT_NAME>|<RESP_KEY>, used to align responsibility grants with RBAC role identifiers.
• ROLE_ORIG_SYSTEM / ROLE_ORIG_SYSTEM_ID — identifies the role's origin, typically FND_RESP, with the numeric responsibility ID.
• START_DATE / EXPIRATION_DATE — the assignment's effective window, taken from FND_USER_RESP_GROUPS_OLD.END_DATE.
• SECURITY_GROUP_ID — the security group scoping the grant.
• USER_START_DATE / USER_END_DATE, ROLE_START_DATE / ROLE_END_DATE — the validity windows of the user account and the responsibility definition respectively.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns carried through for traceability.

Common Use Cases and Queries

A typical audit query retrieves current responsibility grants for a named user:

• SELECT user_name, role_name, security_group_id, start_date, expiration_date FROM apps.fnd_resp_sec_ur WHERE user_name = 'OPERATIONS' AND (expiration_date IS NULL OR expiration_date > SYSDATE);

To identify expired but un-purged assignments:

• SELECT user_name, role_name FROM apps.fnd_resp_sec_ur WHERE expiration_date IS NOT NULL AND expiration_date < SYSDATE;

For security-group impact analysis, grouping by SECURITY_GROUP_ID reveals how many users hold each responsibility under each group. Because the view consolidates FND_USER_RESP_GROUPS_OLD with its parent masters, it is a convenient single source for responsibility-access extracts, upgrade reconciliation reports, and SoD rule checks, without requiring callers to rejoin the five base objects themselves. Note that rows reflect the legacy assignment table, so post-migration grants made purely through the new UMX role model may not appear here.