Search Results baseline_labor_hours_tot




Overview
Explore in AI Chat

Overview

PA_STATUS_TASK_BGT_REV_HIGH_V is an APPS-owned database view within the Oracle E-Business Suite 12.1.1 / 12.2.2 Projects (PA) module. Its ETRM description is recorded simply as "10SC Only," indicating the object is restricted to a specific localization or deployment context rather than being a general-purpose reporting view. Functionally, the view presents budget and revenue status aggregates at the project, task, and budget type grain, with particular emphasis on baseline and original revenue and labor hour figures.

The view is the aggregation layer of a two-tier pair: it consumes PA_STATUS_TASK_BGT_REV_LOW_V and rolls those lower-level rows up by grouping on PROJECT_ID, TASK_ID, and BUDGET_TYPE_CODE. Because it exposes a column literally named BASELINE_LABOR_HOURS_TOT, it is the object typically implicated when users or reports search for "baseline_labor_hours_tot" in the context of project status reporting. It serves reporting and integration consumers that need summarized budget-versus-revenue and hours status without navigating the detail-level view directly.

Underlying Base Objects

The ETRM metadata documents two referenced objects:

  • PA_STATUS_TASK_BGT_REV_LOW_V (VIEW) — the direct source of rows. The view's SELECT statement reads from this lower-level view, aliased as STBR, and groups its output by PROJECT_ID, TASK_ID, and BUDGET_TYPE_CODE.
  • PA_STATUS (PACKAGE) — the PA status package that underpins the status reporting family in the Projects module. It is the documented base object associated with this view hierarchy.

Every measure in the projection is wrapped in SUM(NVL(column, 0)), which both protects against null propagation and consolidates potentially multiple lower-level rows per project/task/budget type combination. This design makes the HIGH view a deterministic, single-row-per-group summary keyed on the three grouping columns.

Key Columns

The view exposes twenty-three columns. The three dimensional keys are PROJECT_ID, TASK_ID, and BUDGET_TYPE_CODE, forming the unique grouping grain. The remaining columns are aggregated measures falling into four families:

The ITD, YTD, PP, and PTD suffixes denote inception-to-date, year-to-date, prior period, and period-to-date accumulations respectively. The _TOT columns provide the total figure most commonly requested by status dashboards and reconciliations. Baseline values represent the approved reference plan, while original values preserve the initial budget position.

Common Use Cases and Queries

Typical consumers use this view to compare baseline versus original labor hours and revenue at task and budget type level, to feed project status dashboards, or to reconcile totals before period close. A representative query is:

  • SELECT project_id, task_id, budget_type_code, baseline_labor_hours_tot, original_labor_hours_tot, baseline_revenue_tot, original_revenue_tot FROM apps.pa_status_task_bgt_rev_high_v WHERE project_id = :p_project_id;
  • Filtering by budget type to isolate a specific approved budget version: ... WHERE budget_type_code = :p_budget_type;
  • Variance analysis joining the view to project and task master tables and computing differences between baseline and original totals.

Because the view is documented as "10SC Only," availability and intended scope should be verified against the specific localization and patch level before relying on it for general reporting in 12.1.1 or 12.2.2.