Results for “pa_budgets”

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

Overview

PA_BUDGETS is a Projects (PA) module table in Oracle E-Business Suite, documented under ETRM metadata with the terse description "10SC Only." It serves as the header-level repository for project budgets, storing one row per project-budget-type combination and acting as the anchor for the budget structure hierarchy used throughout Oracle Projects. In the standard PA data model, PA_BUDGETS holds the top-level budget definition, while the detailed budget line amounts reside in the PA_BUDGET_LINES and PA_BUDGET_VERSIONS structures; the parent table therefore governs the existence, readiness, and descriptive attributes of a given budget. The object is owned by the PA schema and is classified as VALID in the documented environment.

Under the heuristic Data Vault classification derived from its foreign key topology, PA_BUDGETS is characterized as satellite-leaning. This suggests a modeling approach in which the budget header behaves as a descriptive satellite attached to project and budget-type business keys rather than as a pure hub or link. Practitioners designing integration or warehousing layers for Oracle Projects may find this classification useful when mapping PA_BUDGETS to conformed dimensions and hubs, though it is a heuristic observation and not a mandated Oracle construct.

Key Information Stored

The documented physical schema comprises 19 columns. The primary key, PA_BUDGETS_PK, is a composite business key defined on PROJECT_ID and BUDGET_TYPE_CODE; a supporting unique index, PA_BUDGETS_U1, mirrors the same column pair. Because the key is composite and natural, there is no separate surrogate identifier documented for this table—PROJECT_ID combined with BUDGET_TYPE_CODE uniquely identifies each budget record. The most significant columns are:

• PROJECT_ID — the project to which the budget belongs; a foreign key to PA_PROJECTS_ALL.
• BUDGET_TYPE_CODE — the classification of the budget (for example, approved cost or revenue budget), forming the second half of the composite key.
• READY_TO_BASELINE_FLAG — indicates whether the budget has been sufficiently defined to permit baselining, a key control in the budget lifecycle.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing audit lineage for each record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE10 — the descriptive flexfield (DFF) segments enabling client-specific extensions without schema modification.

The presence of multiple ATTRIBUTE columns indicates that PA_BUDGETS supports a descriptive flexfield, allowing organizations to capture supplemental budget metadata such as funding source, approval reference, or internal classification codes.

Common Use Cases and Queries

The table is most frequently queried when reporting on project budget status, validating which projects have baseline-ready budgets, and joining header attributes to the detailed subbudget and budget line tables. A representative query retrieves budget headers for a project, joining to PA_PROJECTS_ALL for the project number:

SELECT b.project_id, p.segment1 project_number, b.budget_type_code, b.ready_to_baseline_flag, b.last_update_date FROM pa.pa_budgets b, pa.pa_projects_all p WHERE b.project_id = p.project_id AND b.budget_type_code = :budget_type;

Another common pattern identifies budgets flagged as ready to baseline for downstream approval workflows or dashboard reporting:

SELECT project_id, budget_type_code FROM pa.pa_budgets WHERE ready_to_baseline_flag = 'Y';

Because PA_BUDGETS is the parent of PA_SUBBUDGETS, reporting that requires budget-versus-actual comparisons typically starts at this header level and drills into subbudgets and budget lines. The DFF attributes are frequently exposed in extensions and interface tables where client-specific data must be associated with a budget header. Data extraction for enterprise reporting should filter by PROJECT_ID and BUDGET_TYPE_CODE to avoid cross-project ambiguity.

Related Objects

The following objects are most significant in relation to PA_BUDGETS, based on the documented foreign key relationships:

• PA_PROJECTS_ALL — referenced by PA_BUDGETS.PROJECT_ID; the master project definition and the principal source of project attributes.
• PA_SUBBUDGETS — references PA_BUDGETS on PROJECT_ID and BUDGET_TYPE_CODE, forming the child-level budget structure beneath the header.
• PA_BUDGETS_PK / PA_BUDGETS_U1 — the primary key constraint and unique index enforcing the composite business key.
• Budget line and version structures (for example, PA_BUDGET_LINES and PA_BUDGET_VERSIONS) — depend on the header record for budget type and baselining context.
• Oracle Projects budget APIs and concurrent programs — create, update, and baseline budget headers through this table.

Together these objects form the header-to-line budget hierarchy that underpins budget entry, baselining, and budget-versus-actual reporting in Oracle Projects 12.1.1 and 12.2.2.