Search Results confirmed_hours




Overview
Explore in AI Chat

Overview

PA_REP_UTIL_FCT_RUCR_GL_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It supplies Forecast Capacity and Total Forecast Hours values for Person Resources, aggregated by utilization category and reported across General Ledger periods. The object is consumed by Oracle Application (OA) framework screens rather than being exposed as a standalone concurrent program or public interface. Its designation "RUCR" reflects its role in the Resource Utilization Category Reporting family of views, while the "GL" suffix indicates that the period dimension is driven by GL period type, period set, and period name.

The view is a presentation and calculation layer. It does not store data itself; it derives forecast utilization metrics on the fly by reading summarized project balances and applying capacity calculations through PL/SQL packaged functions. Its principal value is that it delivers a ready-to-consume result set of per-person utilization figures for a single GL period, already resolved against the caller's operating unit and calculation method.

Underlying Base Objects

The view is defined over three primary sources joined together:

  • PA_SUMM_BALANCES (synonym) — the summarized project balance table, aliased SUMMBAL. This is the fact source, filtered to VERSION_ID = -1, the forecast version, and constrained to the current GL period type, period set, period name, and period end date supplied by the PA_REP_UTIL_GLOB package.
  • PA_OBJECTS (synonym) — aliased PAOBJ, supplying the PERSON_ID and RES_UTIL_CATEGORY_ID that map each balance row to a person and a utilization category.
  • PA_UTIL_CATEGORIES_V — aliased PAUTL, the utilization category descriptive view that provides the category name and reporting order used for presentation sequencing.

Two packages are referenced in the projection: PA_REP_UTIL_GLOB, which returns session context values such as organization ID, forecast balance type, GL period type and set, current period name, dummy date, and the utilization calculation method; and PA_REP_UTIL_SCREEN, whose CALCULATE_CAPACITY function computes the denominator used to derive the utilization percentage. These dependencies make the view context-sensitive: its output depends on global variable state initialized by the calling OA screen.

Key Columns

  • UTILIZATION_CATEGORY_NAME / UTILIZATION_CATEGORY_ID — the name and identifier of the person's resource utilization category, sourced from PA_UTIL_CATEGORIES_V and PA_OBJECTS respectively.
  • PERSON_ID — the person resource whose forecast figures are being reported.
  • PROVISIONAL_HOURS — the sum of period balances where AMOUNT_TYPE_ID equals 4, representing forecast hours not yet confirmed.
  • CONFIRMED_HOURS — the sum of AMOUNT_TYPE_ID 1 balances minus the provisional (type 4) balances, yielding confirmed forecast hours.
  • UTILIZATION — a rounded percentage calculated as (type 3 balances minus type 6 balances) multiplied by 100 and divided by the capacity returned from PA_REP_UTIL_SCREEN.CALCULATE_CAPACITY. A NVL guard of -9999 protects against absent or non-computable capacity values.
  • REPORTING_ORDER — the display sequence of the utilization category, carried from PA_UTIL_CATEGORIES_V.

Common Use Cases and Queries

The view is primarily invoked from within OA-based Resource Utilization screens, where the PA_REP_UTIL_GLOB package variables have already been set for the target organization and period. Typical interactive usage includes reviewing forecast capacity consumption for person resources by utilization category, comparing provisional against confirmed forecast hours, and displaying utilization percentages for the current GL period.

Because the view depends on global package state, ad hoc queries should first initialize the relevant PA_REP_UTIL_GLOB globals; otherwise null or unexpected results will be returned. A representative query is:

  • SELECT person_id, utilization_category_name, provisional_hours, confirmed_hours, utilization, reporting_order FROM apps.pa_rep_util_fct_rucr_gl_v ORDER BY reporting_order, person_id;
  • Filtering variants such as WHERE utilization > 0 or WHERE person_id = :person_id are commonly applied to isolate a single resource or flag over-utilized resources within the period.

Custom reporting extracts generally wrap the view in an inline or materialized construct to preserve the calculated columns, since the underlying aggregation and capacity logic cannot be reproduced simply from base tables without the packaged functions.