Search Results pa_budget_types

Overview

The PA_BUDGET_TYPES table is a core reference table within the Oracle E-Business Suite Projects (PA) module. It serves as the master repository for implementation-defined classifications of budget types, which are used to categorize budgets for distinct business purposes. In the context of project financial management, this table enables organizations to define and enforce different budgeting methodologies, controls, and reporting requirements. Its role is foundational, as the BUDGET_TYPE_CODE acts as a key foreign key linking budget definitions to numerous transactional and control tables across the Projects and Grants Accounting modules, ensuring data integrity and consistent application of budgetary rules.

Key Information Stored

The primary information stored is the unique budget type code and its associated descriptive attributes. The table's structure is centered on the BUDGET_TYPE_CODE column, which is the primary key (PA_BUDGET_TYPES_PK). While the provided ETRM metadata does not list all columns, typical columns in such a reference table would include BUDGET_TYPE_CODE, NAME, DESCRIPTION, ENABLED_FLAG, and various WHO columns (CREATION_DATE, CREATED_BY, etc.). The critical data point is the code itself, which is referenced throughout the application to classify budget versions, financial plans, and control settings. The descriptive name allows users to identify the purpose of each type, such as "Original Budget," "Current Forecast," or "Management Reserve."

Common Use Cases and Queries

A primary use case is the setup and maintenance of budget types during implementation, which dictates the budgeting framework for all projects. Common reporting and validation queries involve joining this table to transactional budget data. For instance, to list all active budget types and count the number of budget versions created for each, a query would join to PA_BUDGET_VERSIONS. Another critical scenario is auditing the migration of legacy budget types to financial plan types during upgrades, as indicated by the foreign key from PA_FIN_PLAN_TYPES_B. A sample SQL pattern to retrieve all budget types and their associated budgetary control options would be:

• SELECT bt.budget_type_code, bt.name, bco.control_level
• FROM pa_budget_types bt, pa_budgetary_control_options bco
• WHERE bt.budget_type_code = bco.budget_type_code
• AND bt.enabled_flag = 'Y';

Related Objects

As per the provided foreign key relationships, PA_BUDGET_TYPES is integral to the Projects module's budgetary architecture. Key related transactional tables include PA_BUDGET_VERSIONS (where specific budget instances are stored) and PA_PROJECT_ACCUM_BUDGETS (for accumulated budget amounts). It is central to the budgetary control subsystem, linking to PA_BUDGETARY_CONTROLS and PA_BUDGETARY_CONTROL_OPTIONS. The table also has significant relationships in Grants Accounting (GMS_BUDGET_VERSIONS) and intersects with financial planning (PA_FIN_PLAN_TYPES_B, PA_FP_UPGRADE_AUDIT) and rate calculation (PA_CINT_RATE_INFO_ALL). These dependencies underscore its role as a master control point for budget classification across the system.