Search Results pa_status_task_ei_base_v




Overview
Explore in AI Chat

Overview

PA_STATUS_TASK_EI_BASE_V is an Oracle Projects (PA) view owned by the APPS schema. It is classified as an expenditure inquiry (EI) base view, a class of views that Oracle EBS uses to drive the Project Status Inquiry (PSI), Project Status Inquiry reporting windows, and related expenditure and revenue drill-down functionality. The view consolidates transaction accumulation data with cost distribution and revenue distribution detail, presenting a period-keyed, project- and task-level monetary and quantity picture that reporting programs and forms can consume without querying the underlying transactional tables directly.

A distinguishing characteristic of this view is its dependence on the PA_STATUS package for run-time context. The WHERE clause references PA_STATUS.GETPROJID, PA_STATUS.GETTASKID, PA_STATUS.GETRSRCMEMBERID, PA_STATUS.GETSTARTDATE, and PA_STATUS.GETENDDATE, meaning the view is intended to be queried within an initialized Project Status Inquiry session rather than as a general-purpose standalone view. Querying it outside of that context returns no rows or defaults based on the package's session-level globals.

Underlying Base Objects

The documented base objects referenced by the view are PA_TXN_ACCUM, PA_TXN_ACCUM_DETAILS, PA_COST_DISTRIBUTION_LINES_ALL, PA_CUST_REV_DIST_LINES_ALL, and PA_PERIODS, all of which are exposed in APPS through synonyms, along with the PA_STATUS package.

PA_TXN_ACCUM supplies the transaction accumulation header — the project, task, period, and TXN_ACCUM_ID with which each expenditure item is associated. PA_TXN_ACCUM_DETAILS joins to it on TXN_ACCUM_ID and EXPENDITURE_ITEM_ID, and drives the union: cost rows are isolated by LINE_TYPE = 'C' and revenue rows by LINE_TYPE = 'R'. For cost, the view joins to PA_COST_DISTRIBUTION_LINES_ALL (on EXPENDITURE_ITEM_ID and LINE_NUM) to obtain raw, burdened, denominator, and accounted cost amounts and quantities. For revenue, it joins to PA_CUST_REV_DIST_LINES_ALL (again on EXPENDITURE_ITEM_ID and LINE_NUM) to obtain the revenue amount. PA_PERIODS resolves each PA_PERIOD name to its period START_DATE and END_DATE, and additionally serves as the driver for the date-range filter.

Key Columns

  • PROJECT_ID / TASK_ID — the project and task identifiers, joined to the current PSI context through PA_STATUS.GETPROJID and PA_STATUS.GETTASKID.
  • TXN_ACCUM_ID / PA_PERIOD — the transaction accumulation header identifier and the accounting period in which the transaction accumulated.
  • START_DATE / END_DATE — period start and end dates derived from PA_PERIODS, and the values against which GETSTARTDATE and GETENDDATE are applied.
  • EXPENDITURE_ITEM_ID — the expenditure item link shared across the accumulation details and the cost or revenue distribution line.
  • QUANTITY, AMOUNT, BURDENED_COST — raw quantity, raw cost, and burdened cost from the cost distribution line; these are populated only on the cost branch of the union.
  • BILLABLE_QUANTITY, BILLABLE_RAW_COST, BILLABLE_BURDENED_COST — the same measures filtered by DECODE on BILLABLE_FLAG, returning the value when the item is billable ('Y') and zero otherwise.
  • DENOM_RAW_COST / DENOM_BURDENED_COST — denominator amounts used for revenue and margin calculations.
  • ACCT_RAW_COST / ACCT_BURDENED_COST — accounted raw and burdened cost amounts.
  • Revenue amount column — on the revenue branch of the union, RDL.AMOUNT is projected into the amount position while the cost-only columns are set to 0 or NULL, distinguishing revenue rows from cost rows.

Common Use Cases and Queries

The primary use case is Project Status Inquiry. When a user drills into expenditure or revenue on a project or task in the PSI window, the application sets the PA_STATUS package globals and then queries this view to retrieve the summarized cost and revenue by period. The view is typically consumed through the standard PSI forms and concurrent programs rather than through custom code.

A representative direct query, executed from a PSI-initialized session, resembles:

  • SELECT project_id, task_id, pa_period, start_date, end_date, quantity, amount, burdened_cost, billable_burdened_cost FROM pa_status_task_ei_base_v WHERE project_id = :p_project ORDER BY start_date;

Because the view reads the package state implicitly, a more practical pattern for custom reporting is to initialize the PA_STATUS context (via the same calls the PSI form makes) before issuing the SELECT, or to treat the view as a template and replicate its joins directly against PA_TXN_ACCUM, PA_TXN_ACCUM_DETAILS, PA_COST_DISTRIBUTION_LINES_ALL, PA_CUST_REV_DIST_LINES_ALL, and PA_PERIODS with explicit project, task, and date predicates. Custom reports should filter on PROJECT_ID, TASK_ID, and PA_PERIOD rather than relying solely on the package, and should account for the union's zero/NULL placeholders when aggregating, since cost and revenue rows are returned from separate branches.