Search Results provisional_hours




Overview
Explore in AI Chat

Overview

PA_REP_UTIL_FCT_RUCR_PA_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered within the Projects (PA) product family. Its documented purpose is to provide Forecast Capacity and Total Forecast Hours values for Person Resources, organized by utilization category and aggregated across PA Periods. The view exists primarily to feed Oracle Application (OA) screens — in practice the Project Resource Utilization and forecast reporting pages — rather than to serve as a general-purpose transactional object.

The name suffix "RUCR" reflects its role in the Resource Utilization and Capacity Reporting flow, and the view is registered as VALID in the ETRM metadata for both 12.1.1 and 12.2.2. For users searching on the term provisional_hours, this view is the primary definition point: the column is explicitly annotated in the view text with the comment banner "FIELD BELOW IS FOR PROVISIONAL_HOURS".

Underlying Base Objects

The view is defined over the following documented base objects:

  • PA_SUMM_BALANCES (SYNONYM) — the underlying summary balance table supplying period balances. The join restricts rows to VERSION_ID = -1, the forecast version, and filters by the PA period type, period set name, period name, and global expenditure period end date supplied via package globals.
  • PA_OBJECTS (SYNONYM) — supplies the resource object identity, including PERSON_ID, OBJECT_ID, and RES_UTIL_CATEGORY_ID.
  • PA_UTIL_CATEGORIES_V (VIEW) — provides the utilization category name and reporting order used to group and sequence the output.
  • PA_REP_UTIL_GLOB (PACKAGE) — a global package exposing session-level accessors such as GETORGID, GETBALTYPEFORECAST, GETPERIODTYPEPA, GETPERIODSETNAME, GETU3PERIODNAME, GETDUMMYDATE, and GETUTILCALCMETHOD.
  • PA_REP_UTIL_SCREEN (PACKAGE) — supplies CALCULATE_CAPACITY, the function invoked to derive the denominator used in the utilization percentage.

Join predicates link PA_UTIL_CATEGORIES_V.UTIL_CATEGORY_ID to PA_OBJECTS.RES_UTIL_CATEGORY_ID, and PA_SUMM_BALANCES.OBJECT_ID to PA_OBJECTS.OBJECT_ID.

Key Columns

  • UTILIZATION_CATEGORY_NAME / UTILIZATION_CATEGORY_ID — the utilization category label and its identifier, sourced from PA_UTIL_CATEGORIES_V and PA_OBJECTS respectively.
  • PERSON_ID — the person resource for whom forecast hours are reported.
  • PROVISIONAL_HOURS — the sum of PERIOD_BALANCE where AMOUNT_TYPE_ID = 4. These represent forecast hours not yet confirmed.
  • CONFIRMED_HOURS — the sum of balances where AMOUNT_TYPE_ID = 1, less the provisional amount. In effect, confirmed hours are derived by netting provisional hours out of the type-1 total.
  • UTILIZATION — a rounded percentage calculated as (type-3 balance minus type-6 balance) multiplied by 100 and divided by the capacity returned by PA_REP_UTIL_SCREEN.CALCULATE_CAPACITY, with a NVL fallback of -9999 to signal unavailable capacity.
  • REPORTING_ORDER — the display sequence for the utilization category.

Common Use Cases and Queries

The view is typically queried behind an OA page, where PA_REP_UTIL_GLOB has already been initialized with the organization, period type, period set, period name, and calculation method for the session. Direct ad hoc queries outside that context may return no rows or inaccurate figures because the package globals drive the WHERE clause.

A representative query to inspect forecast versus provisional hours for a person is:

  • SELECT person_id, utilization_category_name, provisional_hours, confirmed_hours, utilization
  • FROM apps.pa_rep_util_fct_rucr_pa_v
  • WHERE person_id = :person_id
  • ORDER BY reporting_order;

Typical applications include reconciling provisional forecast hours against confirmed timecard hours for a resource, validating utilization percentages displayed on the Resource Utilization screen, and diagnosing discrepancies where PA_SUMM_BALANCES holds amount type 4 rows that are not reflected as expected in the confirmed total. Because the object is a view rather than a table, it holds no data of its own and must be queried in the context of an initialized PA_REP_UTIL_GLOB session.