Search Results worked_hours




Overview
Explore in AI Chat

Overview

PA_REP_UTIL_ACT_RUCR_PA_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. It presents Total Actual Hours values for Person Resources, aggregated by utilization category and across PA Periods. The object is documented as VALID in ETRM metadata for both 12.1.1 and 12.2.2. Its primary consumer is Oracle Application (OA) framework screens, meaning the view functions as a reporting and integration layer that feeds utilization dashboards rather than as a transactional entity. A single row produced by the view corresponds to one person within one utilization category, carrying computed worked hours, a derived utilization percentage, and a reporting sequence number. The view does not store data; it derives all values at runtime by joining summary balances to person objects and utilization category definitions, and by invoking server-side PL/SQL functions to resolve period context and capacity.

Underlying Base Objects

The view is defined over five documented base objects. PA_SUMM_BALANCES is a synonym supplying the period-by-period balances that the aggregation draws upon. PA_OBJECTS, also accessed through a synonym, holds the person resource records and their assigned utilization categories. PA_UTIL_CATEGORIES_V is a view that supplies the utilization category name and the REPORTING_ORDER attribute. Two PL/SQL packages complete the definition: PA_REP_UTIL_GLOB, which exposes global session and period context values such as organization ID, period type, period set name, period name, balance type for actuals, object type for resources, utilization calculation method, and a dummy global expenditure period end date; and PA_REP_UTIL_SCREEN, which exposes the CALCULATE_CAPACITY function used to derive the denominator of the utilization percentage. Because the period and organization values are resolved through these globals rather than through literal predicates, the view returns data for the period currently selected in the OA screen context, not for an arbitrary caller-supplied period.

Key Columns

  • UTILIZATION_CATEGORY_NAME — the descriptive name of the utilization category, taken from PA_UTIL_CATEGORIES_V.
  • UTILIZATION_CATEGORY_ID — the identifier of the resource utilization category, sourced from PA_OBJECTS.RES_UTIL_CATEGORY_ID.
  • PERSON_ID — the person resource identifier from PA_OBJECTS.
  • WORKED_HOURS — the sum of PA_SUMM_BALANCES.PERIOD_BALANCE for AMOUNT_TYPE_ID 1 (G_RES_HRS_C), with nulls coerced to zero. This is the actual worked hours figure.
  • UTILIZATION — a rounded percentage computed as the sum of AMOUNT_TYPE_ID 3 (G_RES_WTDHRS_PEOPLE_C) balances multiplied by 100 and divided by the capacity returned by PA_REP_UTIL_SCREEN.CALCULATE_CAPACITY. Null results are replaced with −9999, revealing a sentinel for missing capacity.
  • REPORTING_ORDER — the display sequence attribute from PA_UTIL_CATEGORIES_V, exposed directly on the view and used to order categories in OA screens.

Common Use Cases and Queries

The view supports utilization reporting screens that show per-person actual hours and utilization percentages grouped by category. Because period context is injected by PA_REP_UTIL_GLOB, queries are typically executed from within the OA session; ad hoc SQL submissions outside that context may return no rows. A representative query that orders categories by the requested reporting sequence is:

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;

A typical roll-up aggregates worked hours and averages utilization per category, again preserving REPORTING_ORDER for presentation. The sentinel value of −9999 warrants explicit handling in reporting logic, since it denotes a capacity that could not be resolved rather than a genuine utilization figure. The view is read-only in practice; no DML should be issued against it.