Results for “pa_budget_types_pk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_BUDGET_TYPES is an Oracle Projects (PA) reference and setup table that stores implementation-defined classifications of budget types used across Oracle E-Business Suite for different business purposes. Each row represents a distinct budget type — for example a cost budget, revenue budget, or forecast — that may be assigned to project budget versions and used consistently throughout the Projects and Grants Accounting modules. Because the same budget type code is consumed by budgetary control, financial plan types, capitalized interest calculations, and accumulated budget reporting, the table functions as a controlled vocabulary that keeps budget semantics aligned across the application.

Under the Data Vault classification heuristic mined from its foreign-key structure, PA_BUDGET_TYPES is modeled as a hub. It carries the business key and descriptive attributes for the budget type concept, while the many transactional and configuration tables that reference it behave as satellites and links. Each dependent table (budget versions, budgetary controls, financial plan types, and so on) stores only the code, with descriptive detail remaining centralized here.

The table is fully partitioned for multi-language support in release 12.2.2: the documented physical schema includes the ZD_EDITION_NAME column, and both unique indexes — PA_BUDGET_TYPES_U1 on (BUDGET_TYPE_CODE, ZD_EDITION_NAME) and PA_BUDGET_TYPES_U2 on (BUDGET_TYPE, ZD_EDITION_NAME) — incorporate that column. The physical schema contains 34 columns; users typically maintain rows through the Oracle Projects setup interface or through the seeded data supplied by Oracle.

Key Information Stored

The primary key is PA_BUDGET_TYPES_PK, defined on BUDGET_TYPE_CODE. Two candidate business keys are documented: PA_BUDGET_TYPES_U1 on (BUDGET_TYPE_CODE, ZD_EDITION_NAME) and PA_BUDGET_TYPES_U2 on (BUDGET_TYPE, ZD_EDITION_NAME). The most significant columns are:

• BUDGET_TYPE_CODE — the primary key and the value referenced by all foreign keys.
• BUDGET_TYPE — the user-facing name of the budget classification.
• DESCRIPTION — free-text explanation of the budget type's purpose.
• BUDGET_AMOUNT_CODE — indicates the amount basis (for example cost versus revenue) associated with the type.
• PREDEFINED_FLAG — identifies seeded, Oracle-provided types versus user-defined ones.
• ACCUMULATION_FLAG — controls whether budgets of this type accumulate across versions or periods.
• PLAN_TYPE — links the budget type to a planning configuration.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range for the type.
• ENABLE_WF_FLAG — whether workflow notification is enabled for the type.
• ADW_NOTIFY_FLAG — controls notification behavior for the type.
• UPGRADE_BUDGET_TYPE_FLAG — identifies types involved in migration or upgrade processing.
• ZD_EDITION_NAME — the language or edition discriminator used by the unique indexes.
• ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard Oracle descriptive-flexfield columns.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN for audit tracking.

Common Use Cases and Queries

The most frequent use is validating which budget types are active for a given business need, and joining the type to budget versions for reporting. A typical lookup query is:

• SELECT budget_type_code, budget_type, description, plan_type, predefined_flag FROM pa.pa_budget_types WHERE start_date_active <= SYSDATE AND (end_date_active IS NULL OR end_date_active >= SYSDATE) ORDER BY budget_type;
• SELECT v.budget_type_code, t.budget_type, v.budget_version_name FROM pa.pa_budget_versions v JOIN pa.pa_budget_types t ON t.budget_type_code = v.budget_type_code WHERE v.project_id = :project_id;
• SELECT b.budget_type_code, t.budget_type, COUNT(*) FROM pa.pa_project_accum_budgets b JOIN pa.pa_budget_types t ON t.budget_type_code = b.budget_type_code GROUP BY b.budget_type_code, t.budget_type;

Other practical scenarios include auditing which budget types have budgetary controls enabled, checking capitalized interest rate configurations by budget type, and reviewing upgrade audit rows in PA_FP_UPGRADE_AUDIT. Reporting use cases include a directory of active budget types, a cross-reference of budget types to financial plan types, and a validation report for Grants Accounting budget versions.

Related Objects

The following tables reference PA_BUDGET_TYPES through BUDGET_TYPE_CODE and are the most significant dependents:

• PA_BUDGET_VERSIONS.BUDGET_TYPE_CODE — stores the specific budget version of a project by type.
• PA_PROJECT_ACCUM_BUDGETS.BUDGET_TYPE_CODE — accumulated budget balances per project.
• PA_BUDGETARY_CONTROLS.BUDGET_TYPE_CODE — budgetary control setup by budget type.
• PA_BUDGETARY_CONTROL_OPTIONS.BUDGET_TYPE_CODE — control option detail by budget type.
• PA_CINT_RATE_INFO_ALL.BUDGET_TYPE_CODE — capitalized interest rate information tied to a budget type.
• PA_FIN_PLAN_TYPES_B.MIGRATED_FRM_BDGT_TYP_CODE — the budget type a financial plan type was migrated from.
• PA_FP_UPGRADE_AUDIT.BUDGET_TYPE_CODE — audit trail for budget type upgrades.
• GMS_BUDGET_VERSIONS.BUDGET_TYPE_CODE — the Grants Accounting equivalent of budget versions.

Because PA_BUDGET_TYPES is the hub, all joins to these tables are made on BUDGET_TYPE_CODE, which provides referential consistency across Oracle Projects budget functionality.