Search Results pa_expenditure_items_all




Overview
Explore in AI Chat

Overview

The PA_EXPENDITURE_ITEMS_ALL table is a core transactional table within the Oracle E-Business Suite Projects module (PA). It stores the smallest, most granular units of cost or expenditure charged to projects and tasks, forming the foundation for project costing, billing, and financial analysis. Every row represents a single expenditure item, such as a labor hour, a purchased item, or an expense report line, that is associated with a specific project task. Its role is critical for capturing raw cost data, which is subsequently processed for capitalization, invoicing, and transfer to the General Ledger. The '_ALL' suffix indicates it is a multi-org table, storing data for all operating units.

Key Information Stored

The table's primary key is the system-generated EXPENDITURE_ITEM_ID. Essential columns include EXPENDITURE_ID, linking the item to its parent batch header in PA_EXPENDITURES_ALL; PROJECT_ID and TASK_ID, defining the charge destination; and EXPENDITURE_TYPE, classifying the nature of the cost. It holds comprehensive financial data such as raw and burdened cost amounts, quantities, and dates. Crucially, it maintains multi-currency information through columns like DENOM_CURRENCY_CODE (transaction currency), ACCT_CURRENCY_CODE (ledger currency), and PROJECT_CURRENCY_CODE, along with associated exchange rate types (e.g., ACCT_RATE_TYPE) for conversions.

Common Use Cases and Queries

Direct updates to this table are strongly discouraged outside of approved Oracle APIs (e.g., PA_EXPENDITURE_ITEMS_PUB) due to complex downstream integrations. Common operational and reporting use cases involve querying expenditure details. For instance, identifying items for a specific project or analyzing costs by type and task are frequent needs. A sample query to examine expenditure items might be:

  • SELECT expenditure_item_id, project_id, task_id, expenditure_type, raw_cost, denom_currency_code
  • FROM pa_expenditure_items_all
  • WHERE project_id = :p_project_id
  • AND expenditure_item_date BETWEEN :p_start_date AND :p_end_date;

Data fixes, when necessary, must be orchestrated through the public APIs to maintain data integrity, particularly for attributes like expenditure type or project/task assignment, which trigger validation and posting workflows.

Related Objects

PA_EXPENDITURE_ITEMS_ALL has extensive relationships within the EBS schema. Its primary parent is PA_EXPENDITURES_ALL. Key foreign keys link to PA_PROJECTS_ALL, PA_TASKS, and PA_EXPENDITURE_TYPES for basic validation. It also references FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES for currency management. The table has self-referential foreign keys for transferred (TRANSFERRED_FROM_EXP_ITEM_ID) and source items (SOURCE_EXPENDITURE_ITEM_ID), supporting internal adjustments and allocations. Data from this table flows into cost distribution, revenue accrual, and invoice generation processes, impacting tables like PA_COST_DISTRIBUTION_LINES_ALL and PA_DRAFT_INVOICE_ITEMS_ALL.