Search Results budgeted_cost




Overview
Explore in AI Chat

Overview

PA_PA_VIEW is a reporting view in the Oracle EBS Projects (PA) module, documented in ETRM as spanning releases 12.1.1 and 12.2.2. Its purpose, per the metadata description, is to present "Actual cost and revenue totals for projects and tasks by PA Period." The view aggregates transactional and budgetary amounts at the project, task, and PA Period grain, making it suitable for period-based reporting, reconciliation, and downstream integration where summarized project financials are required rather than individual expenditure or event lines.

The description carries the qualifier "10SC Only." This indicates that the view is not a standard, generally available Oracle Projects object but rather one associated with a specific deployment context (a "10SC" localization or custom/solution bundle). The implementation note states "Not implemented in this database," reinforcing that the object may not exist in every 12.1.1 or 12.2.2 environment and its presence should be verified before use. The document is marked Oracle Proprietary, Confidential Information.

The user's search term, budgeted_revenue, maps directly to a column exposed by this view, which is the primary reason it surfaces for that keyword. PA_PA_VIEW is therefore most relevant to anyone seeking period-level budgeted revenue figures stored alongside actual revenue and cost totals.

Underlying Base Objects

The view text selects exclusively from a single source: PA_ACCUM_VIEW. It performs no joins; instead it aggregates (SUM) the accumulated amounts and groups them by PROJECT_ID, TASK_ID, PA_PERIOD, PA_START_DATE, and PA_END_DATE. PA_ACCUM_VIEW is the Projects accumulation view that consolidates project cost, revenue, billing, and budget data across the subledger and budget structures.

The ETRM metadata lists the referenced base objects as "none documented" and the owner field as blank, which is consistent with the "Not implemented in this database" note. In practice, the true lineage passes through PA_ACCUM_VIEW to the underlying Projects accumulation tables and, ultimately, to the project/task definition and period tables. Because the view only ever reads from PA_ACCUM_VIEW, any change to that object's definition propagates to PA_PA_VIEW.

Key Columns

The view exposes seventeen columns; the most operationally significant include:

All monetary, quantity, and hour totals are wrapped in ROUND with no decimal argument, so values are returned as whole numbers, which is important to note for reconciliation and precision-sensitive reporting.

Common Use Cases and Queries

Because the view delivers period-grouped actual versus budgeted figures, it supports budget-to-actual variance analysis, period-over-period revenue tracking, and integration extracts. A representative query retrieving budgeted and actual revenue by project and period is:

  • SELECT project_id, task_id, pa_period, pa_start_date, pa_end_date, total_revenue, budgeted_revenue FROM pa_pa_view WHERE project_id = :project_id ORDER BY pa_period;
  • Variance: SELECT project_id, pa_period, budgeted_revenue - total_revenue AS revenue_variance FROM pa_pa_view;
  • Labor utilization: SELECT project_id, pa_period, total_labor_hours, billable_labor_hours, budgeted_labor_hours FROM pa_pa_view WHERE task_id = :task_id;

Before relying on the view, confirm its existence in the target database, given the "Not implemented in this database" and "10SC Only" notes. Where PA_PA_VIEW is absent, equivalent results can be obtained by replicating its aggregation directly against PA_ACCUM_VIEW.