Search Results billable_burdened_cost




Overview
Explore in AI Chat

Overview

APPS.PA_STATUS_EI_BASE_V is a reporting view in Oracle EBS Projects (PA) that aggregates expenditure item–level project status amounts, grouped by expenditure item, project accounting start date, and PA period. Its role is to consolidate the task-level and resource-level status base views into a single, unified result set so that downstream status inquiry and reporting logic can query one consistent source of truth. The view is defined as the UNION ALL of PA_STATUS_TASK_EI_BASE_V and PA_STATUS_RSRC_EI_BASE_V, and it is referenced by the PA_STATUS package, which drives the project status generation and reporting process.

Because it is a base reporting view rather than a transaction table, it carries no independent data of its own. All figures it exposes are derived at runtime from its two child views. In the Oracle EBS 12.1.1 and 12.2.2 releases, this view supports the project status and expenditure inquiry flows where users examine cost, burden, billable, and revenue amounts on a period-by-period basis. The inclusion of the PA_PERIOD column makes it particularly relevant to users searching for pa_period, since period-level aggregation is central to project performance reporting.

Underlying Base Objects

The ETRM metadata documents the view as referencing three objects: the PA_STATUS package and two views, PA_STATUS_TASK_EI_BASE_V and PA_STATUS_RSRC_EI_BASE_V. The view text confirms that the SELECT statements draw exclusively from these two base views. Each branch of the UNION ALL aggregates the same set of measures over the same grouping keys (EXPENDITURE_ITEM_ID, PA_START_DATE, PA_PERIOD), and returns identical column lists, allowing Oracle to combine them without column mismatch. The PA_STATUS package is the consuming object that calls this view during project status compilation, so changes to either child view or to the expenditure item data beneath them flow through to any report that relies on PA_STATUS_EI_BASE_V.

Key Columns

  • EXPENDITURE_ITEM_ID — Identifier of the expenditure item; a primary grouping key.
  • PA_START_DATE — Project accounting start date associated with the item; used as a grouping key for time-based reporting.
  • PA_PERIOD — The PA accounting period name; central to period-by-period rollups and the column most commonly filtered for period reporting.
  • QUANTITY — Total quantity of the expenditure item.
  • RAW_COST — Unburdened cost amount.
  • BURDENED_COST — Cost including burden (overhead) amounts.
  • BILLABLE_QUANTITY, BILLABLE_RAW_COST, BILLABLE_BURDENED_COST — Billable portions of quantity, raw cost, and burdened cost.
  • REVENUE — Revenue amount attributed to the item.
  • DENOM_RAW_COST, DENOM_BURDENED_COST — Denominator cost figures used in burden and rate calculations.
  • ACCT_RAW_COST, ACCT_BURDENED_COST — Accounted (GL-relevant) raw and burdened cost amounts.

Common Use Cases and Queries

A frequent scenario is retrieving period-specific cost and revenue for a given expenditure item. The following query summarizes the measures for a single item across periods:

SELECT expenditure_item_id, pa_period, SUM(raw_cost), SUM(burdened_cost),
      SUM(billable_raw_cost), SUM(revenue)
FROM apps.pa_status_ei_base_v
WHERE expenditure_item_id = :p_ei_id
GROUP BY expenditure_item_id, pa_period
ORDER BY pa_period;

Another common requirement is to report all activity within a specific PA period, which is the pattern implied by the pa_period search leading to this view:

SELECT expenditure_item_id, pa_start_date, SUM(raw_cost), SUM(burdened_cost)
FROM apps.pa_status_ei_base_v
WHERE pa_period = :p_pa_period
GROUP BY expenditure_item_id, pa_start_date;

Because the view performs aggregation internally, additional grouping or filtering should be applied with care; the SUM() functions shown above are used to re-aggregate across the UNION ALL branches if a report requires a single, consolidated line per expenditure item and period. Users should also account for the UNION ALL behavior, which preserves rows from both the task and resource branches rather than eliminating duplicates, so a distinct or grouped query may be needed for reconciliation reporting.