Search Results baseline_burdened_cost_itd




Overview
Explore in AI Chat

Overview

APPS.PA_STATUS_TASK_BGT_COST_HIGH_V is a supplementary database view in the Oracle E-Business Suite Project Accounting (PA) module, owned by the APPS schema and registered within FND Design Data as PA.PA_STATUS_TASK_BGT_COST_HIGH_V. The view is documented as VALID and is delivered in both Oracle EBS 12.1.1 and 12.2.2. Its declared purpose is to simplify Oracle Forms coding by presenting project- and task-level budget cost and quantity summaries in a form that the Project Status Inquiry and related budget-status screens can consume directly.

The view exposes a denormalized, pre-aggregated projection of budget metrics across three cost perspectives: baseline, original, and labor hours. Because Oracle explicitly warns that this is a supplementary Forms view and does not recommend querying or altering data through it—noting that its definition may change dramatically in subsequent minor or major releases—consumers should treat it as an unsupported internal interface. The column BASELINE_BURDENED_COST_ITD, which the user searched, represents the inception-to-date burdened cost for the project baseline budget and is one of the numerically significant measures this view surfaces.

Underlying Base Objects

The documented dependency information lists two referenced base objects: the PL/SQL package PA_STATUS and the view PA_STATUS_TASK_BGT_COST_LOW_V. The PA_STATUS package is the core Project Accounting engine that computes project and task status, including the burdened and raw cost accumulations across ITD, YTD, PP (prior period), and PTD (period-to-date) time windows. PA_STATUS_TASK_BGT_COST_LOW_V is the lower-level companion view that PA_STATUS_TASK_BGT_COST_HIGH_V builds upon, supplying the aggregated baseline and original budget figures.

Given the naming convention—"LOW" and "HIGH" variants in the PA status task budget cost family—the HIGH view is a threshold or rollup-oriented derivation of the LOW view, typically filtering or re-projecting the row set to satisfy a specific screen's status requirements. Underlying physical tables in the PA budget schema (such as PA_BUDGET_VERSIONS, PA_BUDGET_LINES, and the project/task definition tables) are accessed indirectly through PA_STATUS rather than being referenced directly by this view. This abstraction is why the view is labeled supplementary: it is a presentation-layer convenience rather than a reporting-grade interface.

Key Columns

The view's primary key is the combination of PROJECT_ID, TASK_ID, and BUDGET_TYPE_CODE. The 34 exposed numeric columns fall into three metric families, each repeated across four time-phased suffixes:

BASELINE_BURDENED_COST_ITD specifically reports the cumulative burdened cost of the project baseline budget from project inception through the current reporting point, incorporating burden (indirect cost) multipliers applied to raw cost. It is directly comparable to ORIGINAL_BURDENED_COST_ITD, which reflects the original budget rather than the baseline revision.

Common Use Cases and Queries

Typical usage includes Project Status Inquiry screens, budget-versus-actual comparisons, and custom reporting where baseline-to-original variance must be analyzed at task granularity. A representative query retrieving the searched column is:

  • SELECT project_id, task_id, budget_type_code, baseline_burdened_cost_itd, baseline_burdened_cost_ptd, original_burdened_cost_itd FROM apps.pa_status_task_bgt_cost_high_v WHERE project_id = :project_id ORDER BY task_id, budget_type_code;
  • Budget revision delta: SELECT project_id, task_id, budget_type_code, baseline_burdened_cost_itd - original_burdened_cost_itd AS burdened_delta FROM apps.pa_status_task_bgt_cost_high_v;
  • Period comparison: SELECT task_id, baseline_burdened_cost_ptd, baseline_burdened_cost_pp, baseline_burdened_cost_ytd FROM apps.pa_status_task_bgt_cost_high_v;

Because the view is unsupported for direct querying and depends on PA_STATUS package logic, consumers should prefer the Project Status Inquiry concurrent programs or descriptive flexfield-based budget query APIs for production reporting, and reserve direct SELECTs for diagnostics or read-only analysis.