Search Results pabv_prj_resource_act_summary




Overview
Explore in AI Chat

Overview

PABV_PRJ_RESOURCE_ACT_SUMMARY is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite, delivered with the Projects (PA) module. It consolidates summarized project actual cost, quantity, and revenue balances at the resource-list level, exposed through the Project Accumulation process (PA_PROJECT_ACCUM_ACTUALS and PA_PROJECT_ACCUM_HEADERS). The "PABV" prefix identifies it as a Projects reporting view intended primarily for Oracle Business Intelligence (OBI/XML) extract definitions and ad hoc reporting rather than for transactional data entry. The view presents period-to-date (PTD), year-to-date (YTD), inception-to-date (ITD), and prior-period (PP) figures side by side, enabling trend and comparative analysis without repeatedly querying the underlying accumulation tables.

Underlying Base Objects

The view is defined over four documented objects, joined on the project accumulation identifier and project identifier:

  • PA_PROJECT_ACCUM_ACTUALS (SYNONYM) — supplies the monetary, quantity, labor-hour, and revenue measures (aliased PAA).
  • PA_PROJECT_ACCUM_HEADERS (SYNONYM) — supplies the project, resource list, resource list assignment/member, and resource context (aliased PAH).
  • PA_PRJ_ACCUM_PERIODS_V (VIEW) — supplies the accumulation period (ACCUM_PERIOD) joined by project (aliased PAPS).
  • PA_PROJECTS_ALL (SYNONYM) — supplies the project master row and enforces operating-unit security (aliased PPA).

The view filters on PAH.TASK_ID = 0 (top-task level only) and PAH.RESOURCE_LIST_MEMBER_ID > 0 (resource detail only), and it applies virtual column substitutions for unit of measure (_LA lookups) and organization-level security (_SEC). Because it is declared WITH READ ONLY, no DML is permitted against it.

Key Columns

  • PROJECT_ACCUM_ID / PROJECT_ID — keys linking the summarized row back to the project and accumulation record.
  • ACCUM_PERIOD — the accumulation (GL) period the measures relate to.
  • RAW_COST_ITD / _YTD / _PP / _PTD — unbilled, unburdened actual costs by date range.
  • BURDENED_COST_* and BILLABLE_BURDENED_COST_* — burdened and billable burdened cost sets across ITD/YTD/PP/PTD.
  • QUANTITY_ITD / QUANTITY_YTD / QUANTITY_PP / QUANTITY_PTD — the summary quantity measures flagged by the search term "quantity_ptd," representing period-to-date resource quantity.
  • LABOR_HOURS_* and BILLABLE_QUANTITY_* / BILLABLE_LABOR_HOURS_* — labor-hour and billable counterparts.
  • REVENUE_ITD / _YTD / _PP / _PTD — recognized revenue by date range.
  • RESOURCE_LIST_ID / RESOURCE_LIST_MEMBER_ID / RESOURCE_ID — resource context for filtering and grouping.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — audit columns carried from the accumulation actuals.

Common Use Cases and Queries

Typical uses include project cost/quantity dashboards, month-end accumulation reconciliation, and BI extract definitions. A representative query returning period-to-date quantity alongside cost and revenue for a project is:

SELECT project_id, accum_period,
       quantity_ptd, billable_quantity_ptd,
       raw_cost_ptd, burdened_cost_ptd, revenue_ptd
  FROM apps.pabv_prj_resource_act_summary
 WHERE project_id = :p_project_id
   AND accum_period = :p_period;

For resource-level trending, filter by RESOURCE_LIST_MEMBER_ID and order by ACCUM_PERIOD to compare QUANTITY_PTD against QUANTITY_YTD and QUANTITY_ITD. Aggregate reporting should group by PROJECT_ID, ACCUM_PERIOD, and RESOURCE_ID, while respecting the built-in organization security predicate. Because the view suppresses task-level detail (TASK_ID = 0) and enforces read-only access, it is best suited to summary reporting rather than task-level transactional analysis.