Search Results detail_region_switch

Overview

UMX_ROLE_ASSIGNMENTS_V is a private APPS-owned view within the FND – Application Object Library product, delivered as part of the User Management (UMX) infrastructure in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to display the roles and registration requests associated with a given user, presenting both currently assigned roles and pending, errored, or unassigned access requests in a single consolidated result set. The view is described in the ETRM repository as private, meaning it is intended primarily for internal consumption by the UMX self-service role management and user registration flows rather than as a general-purpose reporting interface. Nevertheless, because it exposes descriptive role attributes, request status codes, request justification text, and effective date boundaries, it is frequently used by technical consultants investigating the state of user-role provisioning, particularly when diagnosing why an access request appears stalled or is showing an unexpected status.

Underlying Base Objects

The view is defined by a UNION ALL of two logical blocks, and the documented base objects reflect this composite nature.

• UMX_REG_REQUESTS (synonym) – supplies the registration request rows, including REG_REQUEST_ID, STATUS_CODE, requested start and end dates, justification, and the requested-for user identifier.
• UMX_REG_REQUESTS_PVT (package) – supplies IS_PEND_REQUEST_ERROR, used to distinguish pending requests that have actually failed from those that remain genuinely pending.
• WF_ALL_ROLES_VL (view) – provides the role name, display name, and description from the workflow role model.
• FND_LOOKUP_VALUES_VL (view) – supplies the lookup meaning that surfaces as STATUS_TEXT, drawn from the lookup type UMX_ACCESS_ROLE_STATUS.
• WF_ALL_USER_ROLE_ASSIGNMENTS (view) and WF_LOCAL_ROLES (synonym) – support the second UNION branch that reports already-assigned roles with computed status values of APPROVED or INACTIVE.
• FND_GLOBAL (package) and FND_USER (synonym) – provide session context through FND_GLOBAL.USER_ID and tie assignments back to the user.

Key Columns

• STATUS_TEXT – the translated display meaning of the request status, resolved through the UMX_ACCESS_ROLE_STATUS lookup. This column is commonly targeted by searches and reporting queries.
• STATUS_CODE – the internal status value, including PENDING, ERROR, UNASSIGNED, APPROVED, and INACTIVE.
• STATUS_TEXT_SWITCH, DETAIL_REGION_SWITCH, REMOVEIMG, HIDE_SHOW – presentation control columns consumed by the UMX UI to select the appropriate display region and control state.
• ROLE_NAME, DISPLAY_NAME, DESCRIPTION – role identification attributes.
• ACTIVE_FROM, ACTIVE_TO – requested effective date range for the assignment.
• JUSTIFICATION, REG_REQUEST_ID, REG_SERVICE_CODE, USER_ID, USER_NAME – request and ownership context.

Common Use Cases and Queries

The principal use case is auditing access requests for the current session user, since the view is filtered by FND_GLOBAL.USER_ID for pending records. A typical query retrieving all visible role assignments and request states is:

SELECT role_name, status_code, status_text, reg_request_id,
       active_from, active_to, justification
  FROM apps.umx_role_assignments_v
 ORDER BY role_name;

To isolate only those requests requiring attention, filter on the status text after the lookup resolution:

SELECT role_name, status_code, status_text
  FROM apps.umx_role_assignments_v
 WHERE status_text IN ('Pending', 'Error');

Because the view is private and enforces session-based filtering, direct use in custom concurrent programs or integration extracts should be approached cautiously; the value returned depends on the effective FND_GLOBAL.USER_ID of the executing session. For cross-user administrative reporting, joining to WF_USER_ROLES and UMX_REG_REQUESTS directly is generally preferred over relying on this view.