Results for “resource_country_code”

36 results




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

Overview

PA_RES_APRVL_ROLES_V is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 views owned by the APPS schema and validated under the Projects (PA) product family. It is a denormalized reporting view that exposes the resources eligible to appear as approval-role performers within the Projects staffing and assignment approval workflow. Specifically, the view joins resource records from PA_RESOURCES_DENORM to assignments in PA_PROJECT_ASSIGNMENTS and to notification performers in PA_WF_NTF_PERFORMERS, returning only performers with ROUTING_ORDER = 1 (i.e., the primary/lead approver in the notification chain). The view is addressed by callers searching on the column "no_of_active_candidates," which reports the count of candidates currently active against an assignment.

The view is a UNION ALL of two branches. The first branch returns role rows for schedulable resources whose assignment falls within the resource's effective date range. The second branch expands the result set to include individual persons who have been granted the primary-contact menu through FND_GRANTS, resolved through PER_ALL_PEOPLE_F and WF_ROLES. Together the two branches provide a consolidated security-filtered list of resources and persons that Oracle Projects presents as approval-role candidates.

Underlying Base Objects

The view is defined over the following documented objects:

Relationships are enforced through equality joins on ASSIGNMENT_ID, RESOURCE_ID, and ORGANIZATION_ID, with a BETWEEN predicate restricting assignment start dates to the resource effective window.

Key Columns

  • RESOURCE_ID / RESOURCE_NAME / RESOURCE_JOB_LEVEL — identity and grade of the candidate resource.
  • NAME, RESOURCE_ORGANIZATION_ID, RESOURCE_CITY, RESOURCE_COUNTRY_CODE, RESOURCE_REGION — organization and geographic context.
  • ASSIGNMENT_ID, ASSIGNMENT_NAME, ASSIGNMENT_TYPE, START_DATE, END_DATE — the assignment under approval.
  • APPRVL_STATUS_CODE — current approval state of the assignment.
  • MANAGER_NAME / MANAGER_ID — reporting manager, used both as a role (first branch) and to surface the person ID (second branch).
  • GROUP_ID — notification group from PA_WF_NTF_PERFORMERS.
  • NO_OF_ACTIVE_CANDIDATES — NVL(ASGN.NO_OF_ACTIVE_CANDIDATES, 0); the requested metric reporting currently active candidates on the assignment.

Common Use Cases and Queries

The view is typically used to drive approval-role selection pages and staffing reports, and to audit the volume of active candidates per assignment.

  • Active-candidate load per approval role:
    SELECT ASSIGNMENT_ID, ASSIGNMENT_NAME, RESOURCE_NAME, NO_OF_ACTIVE_CANDIDATES
    FROM   APPS.PA_RES_APRVL_ROLES_V
    WHERE  NO_OF_ACTIVE_CANDIDATES > 0
    ORDER  BY NO_OF_ACTIVE_CANDIDATES DESC;
  • Pending assignments awaiting approval:
    SELECT ASSIGNMENT_ID, RESOURCE_NAME, APPRVL_STATUS_CODE
    FROM   APPS.PA_RES_APRVL_ROLES_V
    WHERE  APPRVL_STATUS_CODE = 'PENDING_APPROVAL';
  • Candidate sourcing by organization and region:
    SELECT NAME, RESOURCE_REGION, COUNT(*) CANDIDATES
    FROM   APPS.PA_RES_APRVL_ROLES_V
    GROUP  BY NAME, RESOURCE_REGION;

Because the second branch draws on FND_GRANTS and WF_ROLES, results are security-filtered to users with the appropriate menu grant, making the view suitable for both inquiry screens and entitlement-aware reporting.