Results for “pa_subbudgets”

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

Overview

PA_SUBBUDGETS is a Projects (PA) module table owned by the PA schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM repository describes the object as "10SC Only," indicating it is a legacy construct whose functional use was scoped to an earlier product release and is retained in the physical schema for backward compatibility, upgrade integrity, and archival reference. It stores sub-budget level detail beneath the parent budget defined in PA_BUDGETS, keyed by the combination of project, budget type, and task.

Under the heuristic Data Vault classification derived from the foreign key structure, PA_SUBBUDGETS is satellite-leaning. Its composite key (PROJECT_ID, BUDGET_TYPE_CODE, TASK_ID) is entirely composed of foreign references to parent entities — PA_PROJECTS_ALL, PA_BUDGETS, and PA_TASKS — rather than an independently generated surrogate. This suggests the table should be modeled as a descriptive satellite attached to the project/budget/task hub-link combination, carrying the measurable budget amounts and descriptive attributes that vary over time.

Key Information Stored

The documented physical schema contains 28 columns. The principal key and descriptive columns are:

• PROJECT_ID — Identifier of the owning project; part of the composite primary key PA_SUBBUDGETS_PK and a foreign key to PA_PROJECTS_ALL and PA_BUDGETS.
• BUDGET_TYPE_CODE — Classifies the budget version (for example, approved cost or revenue budget); part of the primary key and a foreign key to PA_BUDGETS.
• TASK_ID — The task within the project to which the sub-budget applies; part of the primary key and a foreign key to PA_TASKS.
• COST, REVENUE, LABOR_HOURS — The quantified sub-budget amounts for cost, revenue, and labor effort respectively.
• COST_BREAKDOWN_CODE — Indicates the cost breakdown structure applied to the sub-budget amount.
• ROLLUP_FLAG — Controls whether the row's amounts are aggregated into the parent budget totals.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE10 — The standard Oracle Flexfield descriptive columns for extensible, customer-defined attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program traceability columns identifying the process that last populated the row.

Two key structures are documented: the primary key PA_SUBBUDGETS_PK and the unique index PA_SUBBUDGETS_U1, both defined on the same three business columns (PROJECT_ID, BUDGET_TYPE_CODE, TASK_ID). Because the uniqueness constraint is expressed on business attributes rather than a generated surrogate, PA_SUBBUDGETS_U1 is the definitive business-key candidate, and no separate surrogate identifier is exposed in the documented metadata.

Common Use Cases and Queries

Typical usage centers on sub-budget extraction and reconciliation against parent budget and actual cost data. A representative query retrieves all sub-budget rows for a project and budget type, joining to the task for naming:

• Sub-budget vs. actuals comparison — Join PA_SUBBUDGETS to PA_BUDGET_ITEMS on PROJECT_ID, BUDGET_TYPE_CODE, and TASK_ID to compare budgeted cost, revenue, and labor hours against detail budget lines and expenditure actuals.
• Task-level budget reporting — Join to PA_TASKS on TASK_ID to present task names and hierarchy alongside COST and LABOR_HOURS.
• Rollup analysis — Filter on ROLLUP_FLAG to isolate rows that contribute to consolidated project budget totals.
• Audit and lineage — Use REQUEST_ID and PROGRAM_ID to trace which concurrent process populated or last updated a given sub-budget record.
• Upgrade and archival verification — Because the table is 10SC only, queries are frequently written to confirm historical data retained through upgrade rather than active transactional use.

Related Objects

The documented FK relationships connect PA_SUBBUDGETS to the following significant objects:

• PA_BUDGETS — Parent budget header; joined on PROJECT_ID and BUDGET_TYPE_CODE.
• PA_TASKS — Task definition; joined on TASK_ID.
• PA_PROJECTS_ALL — Project master; joined on PROJECT_ID.
• PA_BUDGET_ITEMS — Detail budget lines that reference PA_SUBBUDGETS on PROJECT_ID, BUDGET_TYPE_CODE, and TASK_ID; this is the principal child table.
• PA_BUDGET_VERSIONS and PA_BUDGET_TYPES — Supporting lookups that qualify BUDGET_TYPE_CODE in typical reporting joins.