Search Results pa_status_ei_v




Overview
Explore in AI Chat

Overview

The APPS.PA_STATUS_EI_V view is a Projects (PA) module reporting and integration object that consolidates expenditure item cost, revenue, and descriptive attributes into a single denormalized result set. Its primary design objective is to resolve the "incurred by" party for an expenditure item regardless of whether that party is a labor resource (an employee) or a non-labor resource (a supplier/vendor). This is accomplished through the derived columns EMPLOYEE_VENDOR_NAME and EMPLOYEE_VENDOR_NUMBER, which are computed as NVL(FULL_NAME, VENDOR_NAME) and NVL(EMPLOYEE_NUMBER, SEGMENT1) respectively. The view therefore serves as an authoritative source for any process that must report or extract a unified identifier for the party incurring a project cost, whether that party is internal staff or an external vendor. Typical consumers include cost reporting, project status inquiries, and downstream interfaces that require a single, stable identifier for the incurring resource.

Underlying Base Objects

The view is owned by APPS and is defined over a defined set of base objects: PO_VENDORS, PA_COST_DIST_LINES_ALL_BAS, PER_JOBS, HR_ALL_ORGANIZATION_UNITS_TL, PA_EXPENDITURE_COMMENTS, PA_TRANSACTION_SOURCES, GL_DAILY_CONVERSION_TYPES, PER_ALL_PEOPLE_F, PA_STATUS_EI_DRIVE_V, and the PA_STATUS and PA_SECURITY packages. The core transactional data is drawn from PA_COST_DIST_LINES_ALL_BAS, which supplies expenditure item identifiers, quantities, raw and burdened costs, billable amounts, revenue, and currency conversion attributes. Employee attributes are joined from PER_ALL_PEOPLE_F (FULL_NAME, EMPLOYEE_NUMBER), job attributes from PER_JOBS, and organization descriptions from HR_ALL_ORGANIZATION_UNITS_TL. Vendor attributes are joined from PO_VENDORS. Business rules for row-level access and status derivation are applied through the PA_SECURITY and PA_STATUS packages, and the view references PA_STATUS_EI_DRIVE_V as a supporting driver view.

Key Columns

Common Use Cases and Queries

A frequent requirement is to report all expenditure items along with the unified incurring party identifier, using EMPLOYEE_VENDOR_NUMBER to avoid separate employee and vendor handling logic.

  • Cost reporting by incurring party: SELECT EXPENDITURE_ITEM_ID, PROJECT_ID, TASK_NUMBER, EMPLOYEE_VENDOR_NUMBER, EMPLOYEE_VENDOR_NAME, BURDENED_COST FROM PA_STATUS_EI_V WHERE PROJECT_ID = :project_id.
  • Labor versus non-labor segregation: WHERE INCURRED_BY_PERSON_ID IS NOT NULL for labor, or WHERE VENDOR_ID IS NOT NULL for supplier-delivered costs.
  • Period-based analysis: GROUP BY PA_PERIOD with SUM(BURDENED_COST) and SUM(REVENUE).
  • Interface extraction: SELECT EMPLOYEE_VENDOR_NUMBER, EXPENDITURE_ITEM_DATE, ACCT_BURDENED_COST as input to downstream financial or procurement feeds.

Because the view enforces project security through PA_SECURITY and status rules through PA_STATUS, queries inherit the same access restrictions as standard Projects reporting, ensuring that extracted data respects responsibility-level visibility.