Search Results pa_rep_res_cap_gl_v




Overview
Explore in AI Chat

Overview

PA_REP_RES_CAP_GL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PA (Projects) product family. The view exposes resource capacity hours aligned to a specific GL period. Its name reflects its purpose: it is a "rep" (reporting) view that joins resource-level information to General Ledger period definitions and returns the calculated capacity of each resource for that period.

The view's defining characteristic is that capacity is not stored; it is computed at query time by calling PA_RESOURCE_UTILS.GET_RES_CAPACITY for each resource and period combination, using the period start and end dates as inputs. This makes the view a convenience layer for reporting and integration scenarios where capacity must be compared against actual or scheduled effort within a GL calendar period. Typical consumers include project resource management reports, utilization dashboards, and any downstream extract that reconciles resource availability to a GL period set.

The view is available in both EBS 12.1.1 and 12.2.2, is marked VALID, and is documented in ETRM 12.2.2 with owner APPS and no public synonym detail beyond standard APPS schema conventions.

Underlying Base Objects

Per documented metadata, PA_REP_RES_CAP_GL_V is defined over the following objects:

  • PA_RESOURCES_DENORM (synonym) — supplies the denormalized resource attributes: resource ID and name, manager ID and name, resource organization ID, job ID, resource effective start and end dates, schedulable flag, job level, and person type.
  • GL_PERIODS (synonym) — supplies the period dimension: period year, quarter number, period name, period set name, period number, period type, and start and end dates.
  • GL_SETS_OF_BOOKS (view) — restricts GL periods to the period set and accounted period type of the implementation's set of books.
  • PA_IMPLEMENTATIONS (synonym) — provides the implementation's SET_OF_BOOKS_ID used to bridge to GL_SETS_OF_BOOKS.
  • PER_JOBS (synonym) — supplies the job name (PJ.NAME) associated with the resource's JOB_ID.
  • PA_RESOURCE_UTILS (package) — provides the GET_RES_CAPACITY function invoked in the SELECT list to derive capacity hours.

The joins constrain the result set so that each GL period falls within the resource's effective date range, the resource is flagged schedulable, and the period belongs to the period set and accounted period type of the implemented set of books.

Key Columns

Common Use Cases and Queries

Typical uses include capacity-versus-actual reporting, resource availability extracts, and feeding capacity figures into planning or BI models. Because CAPACITY_HOURS is computed per call, queries should filter on period and resource attributes before selection to limit execution cost.

Example capacity by period for a given period set:

  • SELECT resource_id, resource_name, gl_period_name, capacity_hours FROM pa_rep_res_cap_gl_v WHERE gl_period_set_name = :period_set AND year = :year ORDER BY resource_name, gl_period_number;

Example aggregated capacity by job and period:

  • SELECT job_name, gl_period_name, SUM(capacity_hours) total_capacity FROM pa_rep_res_cap_gl_v WHERE gl_period_name BETWEEN :from_period AND :to_period GROUP BY job_name, gl_period_name;

Example filter to schedulable resources of a given person type:

  • SELECT resource_id, resource_name, person_type, capacity_hours FROM pa_rep_res_cap_gl_v WHERE person_type = 'EMPLOYEE' AND org_id = :org_id;

When joining the view to actual effort, restrict both sides to the same PERIOD_SET_NAME and period range to avoid fan-out across period sets. Because ORG_ID is obtained through PA_IMPLEMENTATIONS, the view returns a single implementation's organization context; multi-organization filters should therefore be applied explicitly when the deployment supports more than one operating unit.