Search Results baseline_raw_cost_ytd




Overview
Explore in AI Chat

Overview

APPS.PA_PROJECT_ACCUM_BUDGETS_V is a reporting view in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema and registered in FND Design Data as PA.PA_PROJECT_ACCUM_BUDGETS_V. The view exposes accumulated budget balances for projects at the project accumulation level, presenting both baseline and original budget figures across cost, burdened cost, labor hours, and revenue. It is defined as an internal view, and Oracle marks it with the standard "Oracle Internal Use Only" warning, indicating that it is not supported for direct customer access except through standard Oracle Applications programs. In practice, the view serves as a denormalized, reporting-friendly projection of budget accumulation data, allowing developers and report authors to retrieve period-to-date, year-to-date, inception-to-date, prior period, and total budget amounts for a given project and budget type without navigating the more granular base table. Its consistent column naming convention (BASELINE_*, ORIGINAL_*, and the time-suffix codes ITD, YTD, PP, PTD, TOT) makes it particularly convenient for period-comparison reporting and for feeding external extract or integration processes.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single referenced base object: the synonym PA_PROJECT_ACCUM_BUDGETS, which resolves to the underlying PA base table. This is a one-to-one structural relationship — the view does not join additional tables; instead it projects and possibly renames columns from the accumulation budget table. The driving key is PROJECT_ACCUM_ID, which links the accumulated budget row to the project's accumulation record, combined with BUDGET_TYPE_CODE to distinguish between budget categories such as baseline, original, and approved budgets. Because the view is a thin projection, changes committed to PA_PROJECT_ACCUM_BUDGETS are reflected immediately when the view is queried, making it suitable for near real-time reporting within the same transaction context.

Key Columns

The view returns an extensive set of numeric measures along with two identifying columns. PROJECT_ACCUM_ID (NUMBER) is the primary correlation key to the project accumulation record, and BUDGET_TYPE_CODE (VARCHAR2 30) identifies the budget type. The remaining columns fall into three families:

  • Baseline measures: BASELINE_RAW_COST_*, BASELINE_BURDENED_COST_*, BASELINE_LABOR_HOURS_*, and BASELINE_REVENUE_*, each with ITD, YTD, PP, PTD, and TOT variants. The specific column the user searched, BASELINE_BURDENED_COST_PTD, represents the baseline burdened (fully loaded) cost for the period to date.
  • Original measures: ORIGINAL_RAW_COST_*, ORIGINAL_BURDENED_COST_*, ORIGINAL_LABOR_HOURS_*, and ORIGINAL_REVENUE_*, following the same suffix pattern. These represent the originally approved budget values.
  • Time-suffix semantics: ITD = inception to date, YTD = year to date, PP = prior period, PTD = period to date, and TOT = total. These suffixes allow direct period-over-period comparisons within a single query.

Common Use Cases and Queries

Typical scenarios include project budget versus actual reporting, period-end budget variance analysis, and extraction of baseline cost and revenue amounts for interface or data warehouse loads. The view is well suited to retrieving both baseline and original figures side by side for the same project accumulation. A representative query referencing the searched column is:

SELECT project_accum_id, budget_type_code,
       baseline_burdened_cost_ptd,
       baseline_burdened_cost_itd,
       original_burdened_cost_ptd
FROM apps.pa_project_accum_budgets_v
WHERE budget_type_code = :budget_type_code;

Because Oracle classifies this object as internal, production code should prefer supported public APIs or documented views, and any direct query should be treated as a read-only reporting access against a schema the application owns.