Search Results pa_budget_items




Overview
Explore in AI Chat

Overview

The PA_BUDGET_ITEMS table is a core data object within the Oracle E-Business Suite (EBS) Projects module (PA). It serves as the detailed transactional repository for individual budget lines. The table's role is to store the granular cost and revenue budget amounts associated with specific tasks, expenditure categories, and types for a given project budget. The "10SC Only" description in the ETRM metadata indicates this table is a foundational component of the 10-SC (Standard Calendar) budget versioning model, which is the primary budgeting architecture in Oracle Projects. It is the child table to PA_BUDGETS and PA_SUBBUDGETS, holding the decomposed financial plan that supports budget entry, tracking, variance analysis, and integration with financial controls.

Key Information Stored

The table's structure is defined by its composite primary key and related descriptive columns. The primary key uniquely identifies a budget line item through the combination of PROJECT_ID, TASK_ID, BUDGET_TYPE_CODE, and LINE_NUM. This design allows for multiple budget lines per task and budget type. Key columns include BUDGET_TYPE_CODE (e.g., 'AC', 'AR' for Cost, Revenue), which classifies the budget nature, and LINE_NUM, which sequences items. Critical financial columns store the BUDGET_AMOUNT for the line. The table also links to the expenditure classification system via EXPENDITURE_CATEGORY and EXPENDITURE_TYPE, enabling detailed planning by labor, equipment, or other cost types. Other significant columns include RESOURCE_ASSIGNMENT_ID for role-based planning and various period-based amount columns for time-phased budgeting.

Common Use Cases and Queries

This table is central to budget reporting and reconciliation processes. A common use case is generating a detailed budget versus actual (BVA) report, which requires joining PA_BUDGET_ITEMS to expenditure transaction tables like PA_EXPENDITURES_ALL. Another frequent scenario involves querying budget summaries by expenditure category for analysis. Sample SQL to retrieve all cost budget lines for a specific project would be:

  • SELECT task_id, expenditure_category, budget_amount FROM pa_budget_items WHERE project_id = :p_project_id AND budget_type_code = 'AC';

For technical integrations, data is typically manipulated via the public Oracle Projects API, PA_BUDGET_PUB, rather than through direct DML on the table, to maintain data integrity and business rule validation.

Related Objects

PA_BUDGET_ITEMS maintains defined foreign key relationships with several key tables, as documented in the provided ETRM metadata. These relationships are critical for data integrity and query joins:

  • PA_SUBBUDGETS: Joined via PROJECT_ID, BUDGET_TYPE_CODE, and TASK_ID. This is the direct parent table, where PA_BUDGET_ITEMS rolls up its amounts.
  • PA_EXPENDITURE_CATEGORIES: Joined via EXPENDITURE_CATEGORY. Validates the category used on the budget line.
  • PA_EXPENDITURE_TYPES: Joined via EXPENDITURE_TYPE. Validates the expenditure type used on the budget line.

Furthermore, the table is a primary source for key budget-related views such as PA_BUDGET_VERSIONS_V and PA_PROJECT_BUDGETS_V. It is also heavily referenced by the PA_BUDGET_PUB package for all budget creation and maintenance operations.