Search Results base_burdened_cost




Overview
Explore in AI Chat

Overview

PA_BUDGET_BY_RESOURCE_V is an Oracle Applications (APPS) view in the Projects (PA) module. Per the ETRM metadata, its status is VALID and its description is simply "10Sc Only." This notation indicates the view is a legacy or internal construct associated with Oracle Projects budgeting functionality, most likely tied to a resource-level budget aggregation used by earlier Projects releases and reporting extracts. In Oracle EBS 12.1.1 and 12.2.2 the view remains valid, but its practical role is that of a reporting and integration surface: it presents budget amounts summarized by project, task, budget type, and resource, rather than exposing raw transactional detail.

Because the view aggregates amounts, it is well suited for reporting bursts, custom concurrent programs, discovery-based integrations, and downstream data warehousing extracts where consumers need cost, revenue, and quantity totals keyed to a resource list member. The user search term "base_revenue" maps directly to one of the view's exposed columns, BASE_REVENUE, confirming the view is a common entry point when querying budgeted revenue at the resource level.

Underlying Base Objects

The only documented referenced base object is PA_NG_BUDGET_BY_RESOURCE_V, itself a view (the "NG" prefix is a naming artifact within Projects). PA_BUDGET_BY_RESOURCE_V is a straightforward aggregation layer defined over that base view. Critically, the projection applies no filter other than a GROUP BY, so every row returned is the sum of matching detail rows from PA_NG_BUDGET_BY_RESOURCE_V.

The GROUP BY clause is: PROJECT_ID, TASK_ID, BUDGET_TYPE_CODE, RESOURCE_LIST_MEMBER_ID, RESOURCE_LIST_ID, RESOURCE_ID, and RESOURCE_ACCUMULATED_FLAG. Understanding this grouping key is essential: a single logical project/task budget appears once per distinct combination of resource list member, list, resource, and accumulated flag. If a caller joins this view to detail tables expecting unique project/task rows, duplicate aggregation will occur.

Key Columns

  • PROJECT_ID / TASK_ID — the project and task the budget lines belong to; these form part of the grouping key.
  • BUDGET_TYPE_CODE — identifies the budget version/type (for example, approved cost or revenue budgets) to which the amounts apply.
  • RESOURCE_LIST_MEMBER_ID / RESOURCE_LIST_ID / RESOURCE_ID — the resource structure context; together with RESOURCE_ACCUMULATED_FLAG they determine how resources were rolled up.
  • BASE_RAW_COST, BASE_BURDENED_COST, BASE_REVENUE, BASE_QUANTITY, BASE_LABOR_QUANTITY — summed base (functional currency) amounts. BASE_REVENUE is the total budgeted revenue in base currency and is the column of interest for the "base_revenue" search.
  • UNIT_OF_MEASURE — derived via a DECODE that returns NULL when the maximum unit of measure is '0' or NULL; otherwise the maximum non-zero unit of measure.
  • ORIG_RAW_COST, ORIG_BURDENED_COST, ORIG_REVENUE, ORIG_QUANTITY, ORIG_LABOR_QUANTITY — corresponding original-currency (transaction currency) sums, enabling comparison between base and original amounts.

Common Use Cases and Queries

Typical uses include budget-versus-actual reporting, revenue budget extracts, and reconciliation of resource-level budget figures. The following query returns base currency revenue budgets for a project:

  • SELECT project_id, task_id, budget_type_code, resource_id, SUM(base_revenue) FROM apps.pa_budget_by_resource_v WHERE project_id = :p_project_id GROUP BY project_id, task_id, budget_type_code, resource_id;

To compare base and original revenue by budget type:

  • SELECT budget_type_code, SUM(base_revenue) base_rev, SUM(orig_revenue) orig_rev FROM apps.pa_budget_by_resource_v WHERE project_id = :p_project_id GROUP BY budget_type_code;

Because the view is already aggregated, callers should apply additional SUM and GROUP BY when consolidating past the documented grouping key. Filters on PROJECT_ID, TASK_ID, and BUDGET_TYPE_CODE are the most selective and should be applied first.