Search Results baseline_labor_hours_pp




Overview
Explore in AI Chat

Overview

APPS.PA_STATUS_TASK_BGT_REV_LOW_V is a supplementary view in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema and classified as VALID in ETRM for both 12.1.1 and 12.2.2. Its designation as a "Low" view, combined with the "STATUS_TASK_BGT_REV" naming convention, indicates that it exists to simplify forms coding rather than to serve as a supported integration or reporting interface. The view aggregates task-level budgeted revenue and labor hour metrics across multiple time-phased dimensions for a given project and task, filtered by budget type.

The user search term "original_revenue_itd" corresponds directly to the ORIGINAL_REVENUE_ITD column exposed by this view. This column represents the inception-to-date original budgeted revenue for a task. Oracle explicitly warns that this view is not recommended for direct querying or data alteration and may change dramatically in subsequent minor or major releases, so it should be treated as an internal forms-support object rather than a stable public interface.

Underlying Base Objects

The documented dependencies for PA_STATUS_TASK_BGT_REV_LOW_V are:

The view therefore sits at the intersection of project/task structure (PA_TASKS), budget configuration (PA_BUDGET_TYPES), and time-phased accumulated amounts (PA_PROJECT_ACCUM_HEADERS, PA_PROJECT_ACCUM_BUDGETS). It does not perform any independent calculation; it reshapes and exposes accumulated budget values at task granularity for form display.

Key Columns

All columns are numeric except BUDGET_TYPE_CODE, which is VARCHAR2(30). The view is keyed on PROJECT_ID, TASK_ID, and BUDGET_TYPE_CODE, meaning each row represents one budget type's figures for a specific task. The metric columns fall into two families — revenue and labor hours — each expressed across four time horizons:

  • BASELINE_REVENUE_ITD / YTD / PP / PTD and BASELINE_REVENUE_TOT — baseline (approved) budget revenue from inception-to-date, year-to-date, prior period, prior-to-date, and total.
  • ORIGINAL_REVENUE_ITD / YTD / PP / PTD and ORIGINAL_REVENUE_TOT — original budget revenue over the same horizons. ORIGINAL_REVENUE_ITD is the item most commonly sought when reconciling original budget revenue against actuals.
  • ORIGINAL_LABOR_HOURS_ITD / YTD / PP / PTD / TOT — original budgeted labor hours by horizon.
  • BASELINE_LABOR_HOURS_ITD / YTD / PP / PTD / TOT — baseline budgeted labor hours by horizon.

The ITD columns represent inception-to-date cumulative amounts; YTD covers the current fiscal year; PTD covers the current period to date; PP reflects the prior period.

Common Use Cases and Queries

Because the view is intended to support forms, typical legitimate uses are diagnostic: inspecting task-level budget figures, validating that form fields populate correctly, or debugging discrepancies between baseline and original budget revenue. A representative query retrieving original inception-to-date revenue for a task is:

  • SELECT project_id, task_id, budget_type_code, original_revenue_itd, original_revenue_tot FROM apps.pa_status_task_bgt_rev_low_v WHERE project_id = :p_project AND task_id = :p_task;
  • SELECT project_id, task_id, budget_type_code, original_revenue_itd, baseline_revenue_itd FROM apps.pa_status_task_bgt_rev_low_v WHERE budget_type_code = :p_budget_type ORDER BY project_id, task_id;

For production reporting requiring the same metrics, developers should query the underlying PA_PROJECT_ACCUM_BUDGETS and PA_PROJECT_ACCUM_HEADERS tables directly, applying the appropriate accumulation logic and PA_BUDGET_TYPES classification, rather than depending on this supplementary view, whose definition is subject to change without notice across releases.