Search Results get_assignment_name




Overview
Explore in AI Chat

Overview

APPS.PA_EXPENDITURE_ITEMS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that flattens the transaction-level expenditure model of Oracle Projects. It joins expenditure items to their parent expenditure, project, task, and non-labor resource records, exposing descriptive attributes alongside raw and burdened cost, revenue, billing, and distribution information on a single row per expenditure item.

The view is the standard source for expenditure inquiries, cost and revenue distribution extracts, billing reconciliation reports, and outbound interfaces into general ledger, subledger accounting, and third-party reporting solutions. Because it resolves project numbers, task numbers, and cost code descriptions in-line, it removes the need for downstream consumers to re-implement the underlying joins. In practice it serves the same functional purpose as querying PA_EXPENDITURE_ITEMS while providing user-facing names rather than surrogate identifiers.

Underlying Base Objects

The view is defined over a set of documented APPS objects. Its core is the PA_EXPENDITURE_ITEMS synonym, aliased E, joined to its parent PA_EXPENDITURES record. Project context is supplied by PA_PROJECTS_ALL (P) for PROJECT_NUMBER and PROJECT_NAME, and task context by PA_TASKS (T). The cost code shown in the derived task descriptor is resolved from PA_RBS_ELEMENTS. Expenditure type classification and unit-of-measure meaning come from PA_EXPENDITURE_TYPES and the lookups objects FND_LOOKUPS and PA_LOOKUPS.

Supporting objects include PA_EXPENDITURE_COMMENTS for the expenditure comment, HR_ALL_ORGANIZATION_UNITS_TL and HR_ORG_UNITS_NO_JOIN for organization information, PA_TRANSACTION_SOURCES for transaction source context, and PO_HEADERS_ALL and PO_LINES_ALL for purchase-order linkage. Utility and security packages referenced are FND_GLOBAL, HR_GENERAL, HR_SECURITY, and PA_UTILS4, which is consistent with MOAC and organization security filtering.

Key Columns

Common Use Cases and Queries

Typical scenarios include cost and revenue reconciliation, billing hold reporting, and external expenditure extracts. A basic project-level listing:

SELECT PROJECT_NUMBER, TASK_NUMBER, EXPENDITURE_ITEM_DATE,
       EXPENDITURE_TYPE, RAW_COST, BURDEN_COST, BILLABLE_FLAG
FROM   APPS.PA_EXPENDITURE_ITEMS_V
WHERE  PROJECT_ID = :p_project_id
ORDER  BY EXPENDITURE_ITEM_DATE;

For assignment-name style reporting, assignment and bill title columns can be combined with personnel information to reconstruct assignment labels used in billing and invoice presentation.

Because the view joins several transactional and setup synonyms and includes HR security logic, queries should filter on project or organization to limit cost, particularly in large implementations. Effective dating on PA_PROJECTS_ALL and PA_TASKS should also be considered when reconciling historical results.