Search Results raw_cost_ptd_base




Overview
Explore in AI Chat

Overview

The APPS.PA_TODATE_BASE_BUDGET_V view is a Projects (PA) module reporting object that exposes current, baselined budget lines for projects and tasks on a PA-period basis. It is a business intelligence style view designed to present budget amounts in a manner consistent with how project and award reporting tools consume revenue and cost data. For the widely searched term revenue_ptd_base, this view is the canonical source in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model.

The view serves an important role within Oracle EBS reporting and integration. Rather than requiring report authors to derive period-to-date, prior-period, and year-to-date figures manually from transaction tables, the view calls the PA_ACCUM_UTILS package to spread baselined budget amounts across time. This is essential because project budgets are stored as lump sums against date ranges rather than as discrete periodic rows, and reporting consumers need those amounts normalized to project accounting periods for comparison against actuals.

The view is read-only, has no data of its own, and exists purely to project and transform data held in the PA budget and resource assignment tables. It is delivered with a status of VALID and is owned by the APPS schema.

Underlying Base Objects

The view is defined over several base objects in the PA schema. The primary source of budget values is PA_BUDGET_LINES (via its synonym), which holds the raw cost, burdened cost, revenue, and quantity values within a baselined budget version's date range. PA_BUDGET_VERSIONS provides the version context, ensuring only the current or baselined version is reflected. PA_RESOURCE_ASSIGNMENTS links the budgeted tasks to resources and determines whether a resource is tracked as labor. PA_RESOURCE_LIST_MEMBERS and the resource list alias provide the resource identity and grouping. Finally, PA_ACCUM_UTILS is the PL/SQL package invoked through the GET_SPREAD_AMOUNT_VAL function to generate the period-spread amounts.

Key Columns

Common Use Cases and Queries

Typical consumers include custom project budget reports, ETL feeds to data warehouses, and reconciliation queries comparing budgeted revenue to actual revenue at a project-period grain. A sample query retrieving period-to-date baselined revenue for a project is shown below.

SELECT project_id,
       task_id,
       budget_type_code,
       resource_id,
       start_date,
       end_date,
       revenue_ptd_base
FROM   apps.pa_todate_base_budget_v
WHERE  project_id = :p_project_id
AND    budget_type_code = 'REV'
ORDER BY start_date;

To compare period-to-date, prior-period, and year-to-date revenue side by side, all three columns can be selected in one query, which is the most efficient pattern since the spreading function is invoked only once per row.

SELECT project_id, task_id, resource_id,
       revenue_ptd_base, revenue_pp_base, revenue_ytd_base
FROM   apps.pa_todate_base_budget_v
WHERE  project_id = :p_project_id;

Because the view relies on PA_ACCUM_UTILS to compute spreads, performance can be sensitive to the number of budget lines and date ranges returned. Restricting queries by PROJECT_ID, budget type, and date range is recommended, and a covering index strategy on the PA budget tables benefits high-volume reporting extracts.