Results for “pa_resource_authority_v”

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

Overview

PA_RESOURCE_AUTHORITY_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the set of people who hold authority over project resources, resolving each resource to its designated resource manager and to staffing managers derived from Oracle Grants/security assignments. In effect, the view answers the question: "Who is authorized to act on behalf of this resource?"

The view is a UNION of three branches. The first branch returns the resource manager recorded directly on the denormalized resource row. The second returns staffing managers assigned the "Primary Contact" role. The third returns staffing managers assigned the general resource authority role. Each branch emits a person identifier, a description of the authority type, and the underlying resource attributes, so that reports, workflow routing, and security lookups can obtain an authority list for a resource without navigating the individual source tables.

Because the view relies on the current system date and on active grant windows, its result set is time-sensitive: authority relationships appear only while the corresponding FND_GRANTS records are in effect.

Underlying Base Objects

The documented base objects are PA_RESOURCES_DENORM, FND_GRANTS, FND_OBJECTS, PER_PEOPLE_X, PA_SECURITY_PVT, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and DUAL. The view is driven primarily by PA_RESOURCES_DENORM, the denormalized resource repository that supplies PERSON_ID, RESOURCE_ID, RESOURCE_NAME, effective dates, MANAGER_ID, and MANAGER_NAME. The first UNION branch reads MANAGER_ID and MANAGER_NAME directly from this table.

The second and third branches join PA_RESOURCES_DENORM to FND_GRANTS and FND_OBJECTS to identify users granted authority over the resource's organization. The join matches FG.INSTANCE_PK1_VALUE to the resource organization and restricts to grantee type USER, object name ORGANIZATION, and instance type INSTANCE. Person resolution is completed through PER_PEOPLE_X. The menu identifier that distinguishes the two staffing-manager roles is computed by a scalar subquery calling PA_SECURITY_PVT.GET_MENU_ID with the parameters 'PA_PRM_RES_PRMRY_CONTACT' and 'PA_PRM_RES_AUTH'. HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY supply the person-name and security utilities used by the underlying objects.

This is the central relevance of the user's search term "menu_id": the view filters FND_GRANTS.MENU_ID against the value returned by PA_SECURITY_PVT.GET_MENU_ID, which is what separates a primary contact from a general resource authority holder.

Key Columns

• PERSON_ID — identifier of the resource person from PA_RESOURCES_DENORM.
• RESOURCE_ID — surrogate key of the resource record.
• RESOURCE_NAME — display name of the resource.
• RESOURCE_EFFECTIVE_START_DATE / RESOURCE_EFFECTIVE_END_DATE — validity window of the resource record.
• MANAGER_ID — person identifier in the authority role; for the resource manager branch this is MANAGER_ID, and for staffing branches it is the granted user's PER.PERSON_ID.
• RESOURCE_AUTHORITY_PERSON_NAME — name of the authority holder, aliased from MANAGER_NAME or PER.FULL_NAME.
• Authority type literal — the final projected column is a text label: 'RESOURCE MANAGER', 'STAFFING MANAGER (PRIMARY CONTACT)', or 'STAFFING MANAGER'. This label is the primary discriminator consumers use to interpret each row.

Common Use Cases and Queries

The view is typically used for authority and notification lookups, security reviews, and data validation during implementations. A representative query lists all authority holders for a given resource:

• SELECT resource_id, resource_name, manager_id, resource_authority_person_name, authority_type FROM pa_resource_authority_v WHERE resource_id = :resource_id;
• SELECT manager_id, resource_authority_person_name FROM pa_resource_authority_v WHERE person_id = :person_id AND resource_authority_person_name = 'STAFFING MANAGER';
• SELECT resource_id, resource_name FROM pa_resource_authority_v WHERE manager_id = :manager_id AND authority_type = 'RESOURCE MANAGER';

Because the authority labels are string literals, they can be used directly in WHERE and CASE expressions. Note that the documented view text shows the third branch joined on the 'PA_PRM_RES_AUTH' menu identifier and that the effective-date predicate is applied in both staffing branches; queries should therefore not assume that authorities persist after grant end dates. Where the definition is truncated in the metadata, the full text should be obtained from ALL_VIEWS in the APPS schema.