Search Results original_labor_hours_pp




Overview

APPS.PA_STATUS_PROJ_BGT_REV_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as PA.PA_STATUS_PROJ_BGT_REV_V. It falls within the Oracle Projects (PA) module and is classified as a "supplementary view used to simplify forms coding," a designation Oracle applies to views whose primary purpose is to flatten or denormalize data so that Oracle Forms-based inquiry screens can retrieve project budget and revenue status information without complex inline SQL. The view has a status of VALID in the ETRM repository for both 12.1.1 and 12.2.2.

The view presents period-based summary amounts for a project's budgets and revenue, split between "baseline" and "original" versions of each budget type. Metrics are expressed in several time buckets — inception-to-date (ITD), year-to-date (YTD), prior period (PP), period-to-date (PTD), and total (TOT) — allowing forms to display comparative figures across time horizons for a given project and budget type. The user search term baseline_labor_hours_ytd corresponds directly to one of the exposed columns, indicating the view is commonly consulted when reporting baseline labor hours for the current fiscal year.

Underlying Base Objects

According to the ETRM dependency metadata, PA_STATUS_PROJ_BGT_REV_V is defined over the following objects:

  • PA_PROJECTS (SYNONYM) — the master project definition table supplying PROJECT_ID and project attributes.
  • PA_PROJECT_ACCUM_BUDGETS (SYNONYM) — the accumulation table that stores budget and revenue amounts by project, budget type and period, the primary source of the ITD/YTD/PTD/TOT figures.
  • PA_PROJECT_ACCUM_HEADERS (SYNONYM) — the header-level accumulation table for the corresponding accumulation structures.
  • PA_STATUS (PACKAGE) — a PL/SQL package involved in the view logic.

The view joins these objects to align accumulation amounts with the project and its budget type. Because PA_PROJECT_ACCUM_BUDGETS is a summarized accumulation table rather than a transactional one, the view reflects rolled-up budget and revenue totals rather than individual budget lines. Note that the four referenced objects are documented as synonyms in the APPS schema, resolving to the underlying PA base tables and package.

Key Columns

The view exposes PROJECT_ID and BUDGET_TYPE_CODE as its identifying keys, plus a family of measure columns:

  • BASELINE_REVENUE_ITD / _YTD / _PP / _PTD / _TOT — baseline revenue amounts across the respective time buckets.
  • ORIGINAL_REVENUE_ITD / _YTD / _PP / _PTD / _TOT — original budget version revenue amounts.
  • ORIGINAL_LABOR_HOURS_ITD / _YTD / _PP / _PTD / _TOT — original labor hours across the respective time buckets.
  • BASELINE_LABOR_HOURS_ITD / _YTD / _PP / _PTD / _TOT — baseline labor hours across the respective time buckets; the YTD column is the target of the user's search.

The ITD, YTD, PP and PTD figures derive from the period-based accumulation rows, while the _TOT columns provide a total figure for the project and budget type combination. All measure columns are NUMBER type.

Common Use Cases and Queries

This view is typically queried to compare baseline versus original project budgets and revenue for a single project or set of projects, often for status reporting or form-driven inquiry. A representative query retrieving baseline labor hours YTD is:

SELECT project_id, budget_type_code, baseline_labor_hours_ytd, original_labor_hours_ytd, baseline_revenue_ytd FROM apps.pa_status_proj_bgt_rev_v WHERE project_id = :p_project_id;

Because the view is a forms-only supplementary view, Oracle explicitly warns that it should not be queried or altered for custom development, and its definition may change significantly in subsequent minor or major releases. For custom reporting, the recommended approach is to query the underlying accumulation tables (PA_PROJECT_ACCUM_BUDGETS and PA_PROJECT_ACCUM_HEADERS) directly rather than relying on this view's structure remaining stable.