Search Results pa_expenditure_items_ar




Overview
Explore in AI Chat

Overview

The PA_EXPENDITURE_ITEMS_AR table is a core data archival object within the Oracle E-Business Suite Projects (PA) module. It serves a critical operational role in the system's data lifecycle management. As explicitly stated in the ETRM documentation, this table functions specifically for "Archive/Purge" processes. Its purpose is to store historical transactional data—specifically, detailed expenditure item records—that have been moved from the primary online transaction processing (OLTP) tables. This architectural separation allows for the maintenance of performance in active transactional tables while preserving a complete, queryable audit trail of project costs and commitments for compliance and historical reporting purposes.

Key Information Stored

While the provided ETRM excerpt directs users to refer to the main table for column-specific comments, the structure of PA_EXPENDITURE_ITEMS_AR mirrors its operational counterpart, PA_EXPENDITURE_ITEMS. It contains archived versions of all critical attributes for a project expenditure line item. This typically includes the primary key (EXPENDITURE_ITEM_ID), associated project and task identifiers, expenditure type, date, quantity, raw and burdened cost amounts, and the system linkage to the original transaction source. Crucially, the documented foreign key relationships indicate it also stores archived references to external system data, such as Purchase Order line identifiers (PO_LINE_ID) and manufacturing resources (WIP_RESOURCE_ID), preserving the integrity of the original transactional context.

Common Use Cases and Queries

The primary use case is historical analysis and regulatory reporting on project financials after the source data has been purged from the main transactional tables. Queries against this table are essential for reconstructing project cost history, performing long-term trend analysis, and fulfilling audit requests. A typical reporting query would join this archive table to other archived or static reference tables to generate historical cost reports.

  • Sample Query Pattern: Retrieving archived expenditure details for a specific project.
    SELECT peia.expenditure_item_id, peia.expenditure_item_date, peia.quantity, peia.raw_cost
    FROM pa_expenditure_items_ar peia
    WHERE peia.project_id = :p_project_id
    ORDER BY peia.expenditure_item_date;
  • Operational Scenario: The table is populated and managed by the official Oracle Projects Archive/Purge process, not by direct user or application DML. Direct querying is standard, but data manipulation should only occur through the sanctioned archival utilities.

Related Objects

PA_EXPENDITURE_ITEMS_AR maintains defined relational integrity with other EBS modules through foreign key constraints, as documented in the ETRM metadata. These relationships are preserved from the original transaction to ensure the archived data remains consistent within the broader application ecosystem.

  • PO_LINES_ALL: Via the column PA_EXPENDITURE_ITEMS_AR.PO_LINE_ID. This links the archived project expenditure item back to its originating Purchase Order line in the Purchasing (PO) module.
  • BOM_RESOURCES: Via the column PA_EXPENDITURE_ITEMS_AR.WIP_RESOURCE_ID. This links the archived item to a manufacturing resource defined in the Bills of Material (BOM) module, relevant for project-related manufacturing activities.

The primary related object is the main transaction table, PA_EXPENDITURE_ITEMS, from which records are sourced during archival. This archive table is also a likely source for custom historical data extracts and data warehouse feeds.