Search Results pa_prm_res_auth




Overview
Explore in AI Chat

Overview

APPS.PA_RES_SCH_TIMELINE_ROWLBL_V is a security-filtered reporting view within the Oracle E-Business Suite Projects (PA) module. It exposes the resource row labels used by the Program Management / Resource Scheduling timeline feature, joining each row label to its denormalized resource record, and further restricting the returned rows to the resources that the currently authenticated user is authorized to view. The authorization model is delegated to Oracle's standard function-security framework (FND_GRANTS) scoped to the menu PA_PRM_RES_AUTH, which is the exact token the user searched for ("pa_prm_res_auth"). The view therefore acts as the data source for UI and reporting components that must present only those organizations (and their resources) for which the user holds an explicit grant, rather than exposing the full resource population. Because it depends on WF_ROLES and PER_ALL_PEOPLE_F, the grantee resolution is performed at the party/person level, consistent with Oracle's role-based access architecture.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PA_TIMELINE_ROW_LABEL — the driving table, supplying row label identity and type; the view filters on ROW_LABEL_TYPE = 'RESOURCE'.
  • PA_RESOURCES_DENORM — the denormalized resource record, joined by RESOURCE_ID and further constrained so that the current date falls between the resource's effective start and end dates.
  • FND_GRANTS — the function-security grant table. Outer-joined on the organization ID (FG.INSTANCE_PK1_VALUE(+) = TO_CHAR(RES.RESOURCE_ORGANIZATION_ID)), instance type 'INSTANCE', grantee type 'USER', and menu ID derived from PA_SECURITY_PVT.GET_MENU_ID('PA_PRM_RES_AUTH').
  • FND_OBJECTS — outer-joined to resolve the object name 'ORGANIZATION'.
  • WF_ROLES — connects the grantee key (user name) to the underlying HZ_PARTY role, restricted to ORIG_SYSTEM = 'HZ_PARTY'.
  • PER_ALL_PEOPLE_F — resolves the party to a person, yielding the resource analyst ID; the join is date-effective (sysdate between effective_start_date and effective_end_date).
  • PA_EXPENDITURES_UTILS and PA_SECURITY_PVT — PL/SQL packages invoked within the view for organization name translation and menu ID lookup respectively.

Key Columns

  • ROW_LABEL_ID / ROW_LABEL_TYPE — identity and category of the timeline row label; type is fixed to 'RESOURCE'.
  • RESOURCE_ID / RESOURCE_NAME — the underlying resource identifier and display name.
  • SCH_UPD_PENDING_FLAG — indicates whether a scheduling update is pending for the row.
  • RESOURCE_ANALYST_ID — person ID of the resource analyst (alias of PER.PERSON_ID).
  • PERSON_ID — person ID from the denormalized resource record.
  • RESOURCE_ORGANIZATION_ID and ORGANIZATION_NAME — the owning organization and its translated (TL) name via PA_EXPENDITURES_UTILS.GETORGTLNAME.
  • MANAGER_ID / MANAGER_NAME — the resource's manager.
  • RESOURCE_JOB_LEVEL — job level classification of the resource.

Common Use Cases and Queries

The view is typically queried to drive resource-timeline pickers and access-controlled reports. A straightforward listing:

  • SELECT row_label_id, resource_id, resource_name, organization_name, manager_name FROM pa_res_sch_timeline_rowlbl_v WHERE resource_organization_id = :org_id;
  • Filtering by analyst: SELECT resource_name FROM pa_res_sch_timeline_rowlbl_v WHERE resource_analyst_id = :person_id;
  • Checking pending scheduling updates: SELECT row_label_id, resource_name FROM pa_res_sch_timeline_rowlbl_v WHERE sch_upd_pending_flag = 'Y';

Because the FND_GRANTS join is an outer join on the single-row instance PK, organizations without a matching grant for the current user still appear only if the outer join and the WF_ROLES/PER_ALL_PEOPLE_F path resolve; in practice the effective result set is governed by the security menu PA_PRM_RES_AUTH, so consumers should not treat this view as an unrestricted resource master. New custom queries should preserve the date-effective filters by relying on the view rather than re-deriving joins against PA_RESOURCES_DENORM directly.