Search Results g_res_hrs_c




Overview
Explore in AI Chat

Overview

APPS.PA_REP_UTIL_ACT_RUCR_PA_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that supports the Project Resource Utilization reporting feature within Oracle Projects (PA). The view surfaces actual utilization metrics for resource categories used in utilization reporting. Specifically, it aggregates period balances for "resource" objects that belong to utilization categories, producing a per-person, per-utilization-category summary of worked hours and a computed utilization percentage.

The view's name encodes its role: "REP_UTIL" indicates the Resource Utilization reporting framework, "ACT" indicates it draws on actual (period) balances, and "RUCR" refers to the Resource Utilization Category Resource object type. The view is part of the internal machinery that supports the Resource Utilization screen and drill-down reports accessed through the PA_REP_UTIL_SCREEN and PA_REP_UTIL_GLOB packages. Because it depends on session-level global package variables, the view is intended for use within the Resource Utilization reporting context rather than as a general-purpose data source.

Underlying Base Objects

The view is defined over three principal data sources, all documented in the ETRM metadata:

  • PA_SUMM_BALANCES (accessed via synonym) — the summary balances table holding period balances by amount type. The view joins on OBJECT_ID and restricts rows to period balances matching the Resource Utilization framework's selected period type, period set, period name, and a dummy global expiration date.
  • PA_OBJECTS (accessed via synonym) — the object registry that identifies resource objects. Rows are filtered to the resource utilization category object type (GetObjectTypeResUcr) and constrained to a specific expenditure organization with project, task, assignment, work type, organization utilization category, and project organization all set to -1.
  • PA_UTIL_CATEGORIES_V (view) — provides the utilization category name and reporting order, joined on RES_UTIL_CATEGORY_ID = UTIL_CATEGORY_ID.

The view also calls three packaged program units: PA_REP_UTIL_GLOB (supplying organization, balance type, period type, period set, period name, object type, and calculation method context), PA_REP_UTIL_SCREEN (providing the CALCULATE_CAPACITY function used in the utilization computation), and indirectly PA_UTIL_CATEGORIES_V. These packages supply the runtime parameters that make the view context-sensitive.

Key Columns

  • UTILIZATION_CATEGORY_NAME — the descriptive name of the utilization category (from PA_UTIL_CATEGORIES_V).
  • UTILIZATION_CATEGORY_ID — the resource utilization category identifier from PA_OBJECTS.
  • PERSON_ID — the person (resource) for whom utilization is reported.
  • WORKED_HOURS — the sum of period balances where amount type is 1 (G_RES_HRS_C, the resource hours amount type). This is the aggregate of actual hours worked.
  • UTILIZATION — a numeric percentage computed as the sum of amount type 3 (G_RES_WTDHRS_PEOPLE_C) balances multiplied by 100 and divided by the capacity returned by PA_REP_UTIL_SCREEN.CALCULATE_CAPACITY. The result is rounded, and an NVL wraps the expression with a default of -9999 to signal a missing or invalid result.
  • REPORTING_ORDER — the display sequence for the utilization category, taken from PA_UTIL_CATEGORIES_V.REPORTING_ORDER and also used in the GROUP BY clause.

Common Use Cases and Queries

The view is primarily consumed by the Resource Utilization reporting screen and its underlying reports, where it provides the actual (as-run) utilization figures for persons within a selected expenditure organization and period. Typical scenarios include utilization trend analysis, capacity-versus-worked-hours reporting, and drill-down from a utilization summary to individual resources.

A representative query filters on the utilization category and orders results as the screen would display them:

  • SELECT utilization_category_name, person_id, worked_hours, utilization, reporting_order FROM apps.pa_rep_util_act_rucr_pa_v ORDER BY reporting_order, person_id;
  • Because the view relies on PA_REP_UTIL_GLOB package globals, callers should invoke it only after the Resource Utilization context (organization, period, balance type, and calculation method) has been initialized by the reporting framework. Querying the view outside that context may return no rows or an incomplete result set.
  • The -9999 sentinel value in UTILIZATION indicates that the capacity calculation could not be resolved; report logic typically treats this as an exception case.

Given its dependence on session globals and package functions, the view is best treated as an internal reporting artifact rather than a public interface, and any custom integration should replicate the initialization performed by PA_REP_UTIL_GLOB before selecting from it.