Results for “res_mgr”

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

Overview

PA_REP_ALL_RES_MGR_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered with the Projects (PA) product family. It is documented as VALID in ETRM for releases 12.1.1 and 12.2.2 and is classified as a VIEW object. Its stated purpose is to expose the set of "starting resource managers" to which the current user has access, derived from that user's security profile and grants. In practice the view is a security-filtered lookup of manager identifiers and manager names, used by Oracle Projects reporting and by integration points that must present a manager selection list without exposing managers the signed-in user is not entitled to see. The view name reflects its three functional parts: PA (Projects), REP (reporting), ALL (all applicable managers across the security boundary), and RES_MGR (resource manager).

Underlying Base Objects

The documented base objects referenced by the view are FND_GLOBAL (package), FND_GRANTS, FND_OBJECTS, FND_PROFILE, FND_USER, PA_REP_RES_MGR_V (view), PA_RESOURCES_DENORM, PA_RESOURCE_UTILS (package), PA_SECURITY_PVT (package), and DUAL. The view definition is a compound query with UNION, UNION ALL, and inline subqueries. The first branch joins PA_REP_RES_MGR_V to PA_RESOURCES_DENORM and includes a profile check on PA_SUPER_RESOURCE. The second branch selects distinct MANAGER_ID and MANAGER_NAME values from PA_RESOURCES_DENORM where SYSDATE falls between RESOURCE_EFFECTIVE_START_DATE and RESOURCE_EFFECTIVE_END_DATE, restricted by organization-level grants joined through FND_GRANTS, FND_OBJECTS, and FND_USER. The third branch, using UNION ALL, returns all dated managers when the PA_SUPER_RESOURCE profile is set to 'Y'. The menu identifier for resource authorization is obtained through PA_SECURITY_PVT.GET_MENU_ID('PA_PRM_RES_AUTH'), while PA_RESOURCE_UTILS and FND_GLOBAL supply supporting security and session context.

Key Columns

According to the documented column list, the view exposes two columns: STARTING_MANAGER_ID and STARTING_MANAGER_NAME. Both originate from the underlying PA_RESOURCES_DENORM records, where MANAGER_ID identifies the manager and MANAGER_NAME holds the display name. The view text aliases these as RES_MGR.MANAGER_ID and RES_MGR.MANAGER_NAME in the first and second branches, and equivalently in the final UNION ALL branch. The search term "manager_name" therefore maps directly to STARTING_MANAGER_NAME, which is the column consumers typically project for display and filter on for name-based searching. Records are only eligible when MANAGER_NAME IS NOT NULL and the manager record is effective on the current system date.

Common Use Cases and Queries

Typical usage is to populate a manager list-of-values in a Projects form or concurrent report, or to constrain reporting output to the managers a user is authorized to view. A basic lookup follows:

• SELECT starting_manager_id, starting_manager_name FROM apps.pa_rep_all_res_mgr_v ORDER BY starting_manager_name;
• SELECT starting_manager_id, starting_manager_name FROM apps.pa_rep_all_res_mgr_v WHERE UPPER(starting_manager_name) LIKE UPPER(:p_name)||'%';
• SELECT starting_manager_id, COUNT(*) FROM apps.pa_rep_all_res_mgr_v GROUP BY starting_manager_id;

Because the view applies profile and grant logic internally, callers do not need to add organization security predicates. Note that the returned set is user-dependent and date-sensitive: results vary with the FND_GLOBAL.USER_ID session value, active FND_GRANTS rows, and the PA_SUPER_RESOURCE profile setting. For performance-sensitive reporting, materialize or cache the result rather than invoking the view repeatedly, as it exercises several security joins and inline subqueries.