Search Results pa_status_ei_base_v




Overview
Explore in AI Chat

Overview

PA_STATUS_EI_BASE_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. It is documented with a status of VALID and carries the terse product description "10SC Only," indicating it is part of the consolidated expenditure status reporting infrastructure used by the Project Status Inquiry and related cost/revenue summarization features. The view presents expenditure balances aggregated at the expenditure item level, keyed by the expenditure item, its start date, and the PA period. Its central role in reporting and integration is to provide a single, pre-aggregated source of expenditure item financials — quantity, raw and burdened cost, billable and revenue amounts, and accounting amounts — so that downstream inquiry screens, concurrent summarization programs, and custom extracts do not each have to recompute these figures from raw transaction tables. Because its first column is EXPENDITURE_ITEM_ID, the view is commonly located when users or developers search that identifier while tracing how expenditure item amounts are rolled up for status reporting.

Underlying Base Objects

The view is defined over internal base views rather than directly over transaction tables. Per the documented ETRM metadata for release 12.2.2, the referenced objects are PA_STATUS (PACKAGE), PA_STATUS_RSRC_EI_BASE_V (VIEW), and PA_STATUS_TASK_EI_BASE_V (VIEW). The view text confirms this structure: it performs a UNION ALL of two symmetric SELECT statements, one from PA_STATUS_TASK_EI_BASE_V and one from PA_STATUS_RSRC_EI_BASE_V. Each branch groups its source rows by EXPENDITURE_ITEM_ID, PA_START_DATE, and PA_PERIOD and applies SUM aggregates to the same set of measures. The UNION ALL therefore combines the task-level base with the resource-level base so that a single expenditure item's totals are presented once per period and start date, regardless of which base contributed the rows.

Key Columns

The column list exposes the expenditure item identifier together with its period and date context and seven families of aggregated amounts:

Because every measure is wrapped in SUM, consumers receive one consolidated row per expenditure item, start date, and period, which is well suited to inquiry-style reporting where detail-level transactions are unnecessary.

Common Use Cases and Queries

Typical uses include Project Status Inquiry reconciliation, cost and revenue reporting, and integration extracts that need expenditure item balances rather than raw transactions. A representative query filters by expenditure item and period:

  • SELECT expenditure_item_id, pa_period, pa_start_date, quantity, raw_cost, burdened_cost, billable_raw_cost, billable_burdened_cost, revenue FROM apps.pa_status_ei_base_v WHERE expenditure_item_id = :p_ei_id;
  • SELECT expenditure_item_id, SUM(burdened_cost), SUM(revenue) FROM apps.pa_status_ei_base_v WHERE pa_period = :p_period GROUP BY expenditure_item_id;

Joins are typically made to expenditure item and project tables on EXPENDITURE_ITEM_ID to resolve descriptive attributes. Given the documented "10SC Only" designation, the view should be validated against the target instance before being relied upon in production customizations.