Search Results pa_budget_versions

Overview

The PA_BUDGET_VERSIONS table is a core data repository within Oracle E-Business Suite Projects (PA) module, specifically for releases 12.1.1 and 12.2.2. It serves as the master table for storing header-level information for every distinct version of a project budget or financial plan. Each record represents a unique snapshot or iteration of budgeted amounts, costs, and revenues for a specific project. The table's primary role is to define the version's attributes, such as its type, status, entry method, and structural dependencies, while the detailed line-item data is stored in related child tables. It is fundamental to the project budgeting, forecasting, and financial planning lifecycle.

Key Information Stored

The table's structure captures metadata and control attributes for each budget version. The primary key is BUDGET_VERSION_ID, a unique system-generated identifier. Critical foreign key columns establish relationships to other master data, defining the version's context and rules. These include PROJECT_ID linking to PA_PROJECTS_ALL, BUDGET_TYPE_CODE linking to PA_BUDGET_TYPES (e.g., original, current, baseline), and BUDGET_ENTRY_METHOD_CODE linking to PA_BUDGET_ENTRY_METHODS (e.g., spread, manual). Other significant columns include RESOURCE_LIST_ID, FIN_PLAN_TYPE_ID, PERIOD_MASK_ID, and RBS_STRUCT_VERSION_ID, which govern the resources, planning options, time periods, and Resource Breakdown Structure (RBS) used. The PARENT_PLAN_VERSION_ID supports version hierarchy by linking to another record within the same table, enabling scenarios like creating a new version from a copy of an existing one.

Common Use Cases and Queries

This table is central to queries for budget version reporting, audit trails, and data integrity checks. A common use case is generating a list of all budget versions for a specific project, including their types and creation details. Another is identifying the current or baseline budget version for financial reporting. Sample SQL patterns include joining to project and budget type tables for descriptive reporting:

• Listing versions for a project: SELECT pbv.budget_version_id, pbv.version_name, pbt.name budget_type, pbv.creation_date FROM pa_budget_versions pbv, pa_budget_types pbt WHERE pbv.project_id = :p_project_id AND pbv.budget_type_code = pbt.budget_type_code ORDER BY pbv.creation_date DESC;
• Finding the hierarchy of versions: SELECT child.version_name, parent.version_name parent_version FROM pa_budget_versions child LEFT JOIN pa_budget_versions parent ON child.parent_plan_version_id = parent.budget_version_id WHERE child.project_id = :p_project_id;

It is also frequently referenced in data fixes to update version attributes or correct invalid foreign key references.

Related Objects

As indicated by its extensive foreign key relationships, PA_BUDGET_VERSIONS is a pivotal hub within the Projects schema. Key related objects include:

• Parent/Dimension Tables: PA_PROJECTS_ALL, PA_BUDGET_TYPES, PA_BUDGET_ENTRY_METHODS, PA_FIN_PLAN_TYPES_B, PA_RESOURCE_LISTS_ALL_BG, PA_PERIOD_MASKS_B, PA_PROJ_ELEMENT_VERSIONS (for RBS and Project Structure versions).
• Child/Transaction Tables: PA_BUDGET_LINES and PA_BUDGET_ACCT_LINES store the detailed budget quantities and amounts. PA_BC_PACKETS, PA_BC_BALANCES, and PA_BC_COMMITMENTS_ALL link budget versions for burdening and commitments processing.
• Financial Planning Objects: PA_FP_ELEMENTS, PA_FP_ADJ_ELEMENTS, and PA_FIN_PLAN_ADJ_LINES use BUDGET_VERSION_ID to tie planning adjustments to a specific version.
• Grants Accounting (GMS): The GMS_BALANCES table references it for tracking award-funded project balances.