Search Results baseline_raw_cost_pp




Overview
Explore in AI Chat

Overview

APPS.PA_STATUS_TASK_BGT_COST_LOW_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It exposes task-level budget cost and labor hour accumulations for Oracle Projects, presenting both original and baseline budget figures aggregated across several time dimensions. The view is registered under FND Design Data as PA.PA_STATUS_TASK_BGT_COST_LOW_V and carries a status of VALID.

Per Oracle's documented guidance, this is a supplementary view used to simplify Forms coding. Oracle explicitly warns that it does not recommend querying or altering data through this view, as its definition may change dramatically between minor or major releases. It should therefore be treated as an internal implementation object rather than a stable, supported integration interface. The "LOW" suffix indicates the view operates at a low-level (detail) granularity — by project, task, and budget type — as opposed to the summary-level views that roll the same measures up for higher-level display.

The user query term "baseline_burdened_cost_ptd" corresponds directly to one of the columns this view exposes, confirming that the view is the object behind the reported budget-to-date burdered cost figure.

Underlying Base Objects

The documented referenced base objects for this view are:

  • PA_BUDGET_TYPES (synonym) — supplies the budget type definitions that classify each row.
  • PA_PROJECT_ACCUM_BUDGETS (synonym) — the primary accumulation table holding the period-by-period original and baseline cost, burdened cost, and labor hour balances.
  • PA_PROJECT_ACCUM_HEADERS (synonym) — provides the accumulation header context that groups the accumulated budget amounts.
  • PA_TASKS (synonym) — supplies task-level attributes and validates the task hierarchy against the project.
  • PA_STATUS (package) — the Oracle Projects status package, which is referenced by the view logic to derive status-controlled values.

Because the view joins accumulation data against budget types and task definitions, each row represents a unique combination of project, task, and budget type, with measures drawn from the accumulated budget balances rather than from transaction detail.

Key Columns

Key columns exposed by the view are organized around identifier keys, budget classification, and the measure groups:

  • PROJECT_ID and TASK_ID — the project and task keys that uniquely identify where the budget balances belong. TASK_ID is essential since the view operates at task level.
  • BUDGET_TYPE_CODE — the budget type (for example, the project's approved cost budget versus other defined types) that labels the measure set on the row.
  • BASELINE_BURDENED_COST_PTD — the baseline burdened cost for the period-to-date window; this is the column the user's search term targets. Burdened cost includes raw cost plus applied burden.
  • BASELINE_RAW_COST_PTD, BASELINE_RAW_COST_ITD, BASELINE_RAW_COST_YTD, BASELINE_RAW_COST_PP, BASELINE_RAW_COST_TOT — the companion original (raw) baseline cost measures across period-to-date, inception-to-date, year-to-date, prior period, and total windows.
  • ORIGINAL_RAW_COST_* and ORIGINAL_BURDENED_COST_* — the same family of windows applied to the original (non-baselined) budget figures.
  • BASELINE_LABOR_HOURS_* and ORIGINAL_LABOR_HOURS_* — labor hour quantities in the same ITD, YTD, PP, PTD, and TOT windows, allowing cost and effort to be analyzed side by side.

The ITD, YTD, PP, PTD, and TOT suffixes carry established Oracle Projects meaning: inception-to-date, year-to-date, prior period, period-to-date, and total.

Common Use Cases and Queries

Typical uses include retrieving baseline burdened cost period-to-date for a given project and task, comparing baseline against original budget across time windows, and feeding downstream budget-versus-actual reporting. Because the view is classified as supplementary and subject to change, production integrations should generally be built against the documented base tables instead. Illustrative queries include:

  • SELECT project_id, task_id, budget_type_code, baseline_burdened_cost_ptd FROM apps.pa_status_task_bgt_cost_low_v WHERE project_id = :project_id;
  • SELECT task_id, baseline_raw_cost_itd, original_raw_cost_itd FROM apps.pa_status_task_bgt_cost_low_v WHERE project_id = :project_id AND budget_type_code = :budget_type;
  • SELECT task_id, baseline_labor_hours_ptd, baseline_burdened_cost_ptd FROM apps.pa_status_task_bgt_cost_low_v WHERE project_id = :project_id ORDER BY task_id;
  • SELECT project_id, task_id, original_burdened_cost_tot, baseline_burdened_cost_tot FROM apps.pa_status_task_bgt_cost_low_v WHERE project_id = :project_id AND task_id = :task_id;

Any use of this object should account for Oracle's stated caveat that the view definition may change significantly across releases.