Search Results pa_status_ei_drive_v




Overview
Explore in AI Chat

Overview

The PA_STATUS_EI_DRIVE_V view is a Projects (PA) module reporting object owned by the APPS schema in Oracle E-Business Suite (validated on 12.1.1 and 12.2.2). It exposes a denormalized, security-filtered projection of expenditure item (EI) data intended for status-based expenditure inquiry, reporting, and integration interfaces. The view joins core expenditure item rows to tasks, expenditure types, system linkages, and organizations, and enriches them with project, task, and resource identifiers resolved through the PA_STATUS package.

A distinguishing feature is its cost-security handling: labor and burdened cost columns are conditionally masked via PA_SECURITY.VIEW_LABOR_COSTS. When the SYSTEM_LINKAGE_FUNCTION is 'ST' or 'OT' (short-term and overtime labor linkages) and the current user is not authorized to view labor costs, the raw and burdened cost values are returned as NULL. This makes the view suitable for controlled reporting where cost visibility must respect Projects security rules.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PA_STATUS_EI_BASE_V — the primary driving view, supplying the core expenditure item rowset (aliased PSEI).
  • PA_EXPENDITURE_ITEMS_ALL and PA_EXPENDITURES_ALL — the transactional expenditure item and expenditure header tables.
  • PA_PROJECTS, PA_TASKS — project and task master data providing project/task identifiers and task number/name.
  • PA_EXPENDITURE_TYPES — expenditure type definitions supplying expenditure and revenue category codes, plus unit of measure.
  • PA_SYSTEM_LINKAGES — linkage definitions supplying the SYSTEM_LINKAGE_FUNCTION and its meaning.
  • PA_LOOKUPS — lookup values, including the unit-of-measure meaning.
  • HR_ALL_ORGANIZATION_UNITS_TL — organization names for expenditure organizations.
  • PA_SECURITY and PA_STATUS — PL/SQL packages invoked for cost masking and identifier resolution.

The join is driven by a LEADING(PSEI) USE_NL(EI) hint, indicating a nested-loop strategy from the base view to the expenditure item table.

Key Columns

Common Use Cases and Queries

The view is typically queried for expenditure status reporting, cost visibility audits, and downstream integrations requiring resolved project/task context. Because cost columns are security-filtered, it is well suited to user-facing reports where labor cost suppression is mandatory.

  • Cost inquiry by project period: SELECT EXPENDITURE_ITEM_ID, PA_PERIOD, RAW_COST, BURDENED_COST FROM PA_STATUS_EI_DRIVE_V WHERE PA_PERIOD = :period;
  • Task-level expenditure detail: SELECT TASK_NUMBER, EXPENDITURE_TYPE, QUANTITY, BILLABLE_QUANTITY FROM PA_STATUS_EI_DRIVE_V WHERE TASK_NUMBER = :task;
  • Linkage analysis: SELECT SYSTEM_LINKAGE_FUNCTION, SYSTEM_LINKAGE_M, COUNT(*) FROM PA_STATUS_EI_DRIVE_V GROUP BY SYSTEM_LINKAGE_FUNCTION, SYSTEM_LINKAGE_M;
  • Organization rollup: SELECT EXPENDITURE_ORGANIZATION_NAME, SUM(RAW_COST) FROM PA_STATUS_EI_DRIVE_V GROUP BY EXPENDITURE_ORGANIZATION_NAME;

Note that returned cost amounts depend on the querying user's Projects security profile; users lacking labor cost privilege will see NULL cost columns for 'ST' and 'OT' linkages.