Results for “pa_budget_lines”

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

Overview

PA_BUDGET_LINES is the detail-line table for project and task budgets in Oracle Projects (PA). It resides in the PA schema and stores the individual budget lines that roll up into a budget version, capturing planned quantities, raw cost, burdened cost, and revenue at the resource-assignment level. In the Oracle EBS 12.1.1 and 12.2.2 data model, PA_BUDGET_LINES is the transactional core of the budgeting feature: whenever a user enters, generates, or baselines a budget, the resulting detail rows are written here. The table is owned by PA, has a VALID status, and contains 127 documented columns. From a Data Vault modeling perspective, the FK structure classifies PA_BUDGET_LINES as satellite-leaning — it carries descriptive and measured attributes that hang off the PA_BUDGET_VERSIONS parent (via BUDGET_VERSION_ID) and the PA_RESOURCE_ASSIGNMENTS parent (via RESOURCE_ASSIGNMENT_ID), rather than acting as a pure hub or link. One row represents a single budget line for a specific resource assignment, transaction currency, and period range within a budget version.

Key Information Stored

The primary key is PA_BUDGET_LINES_PK on BUDGET_LINE_ID, a system-generated surrogate identifier. Two unique indexes document business-key candidates: PA_BUDGET_LINES_U2 (BUDGET_LINE_ID) and PA_BUDGET_LINES_U1 (RESOURCE_ASSIGNMENT_ID, START_DATE, TXN_CURRENCY_CODE), which confirms that a resource assignment may have one line per start date and transaction currency within a version.

• BUDGET_LINE_ID – surrogate PK and the column referenced by downstream tables.
• BUDGET_VERSION_ID – FK to PA_BUDGET_VERSIONS; ties each line to its parent budget version.
• RESOURCE_ASSIGNMENT_ID – FK to PA_RESOURCE_ASSIGNMENTS; identifies the budgeted resource.
• START_DATE / END_DATE / PERIOD_NAME – the effective date range and GL period of the line.
• QUANTITY – budgeted quantity for the resource assignment.
• RAW_COST / BURDENED_COST / REVENUE – the primary financial measures, expressed in the project functional currency.
• TXN_RAW_COST / TXN_BURDENED_COST / TXN_REVENUE / TXN_CURRENCY_CODE – transaction-currency equivalents used for multi-currency budgets.
• PROJECT_RAW_COST / PROJECT_BURDENED_COST / PROJECT_REVENUE – project-currency amounts obtained via the PROJECT_* rate type/rate/date columns.
• CODE_COMBINATION_ID – FK to GL_CODE_COMBINATIONS; the accounting flexfield for the line.
• QUANTITY_SOURCE, RAW_COST_SOURCE, BURDENED_COST_SOURCE, REVENUE_SOURCE – indicate how each amount was derived (entered, calculated, spread).
• COST_REJECTION_CODE / REVENUE_REJECTION_CODE / BURDEN_REJECTION_CODE – rejection flags for budget validation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY – standard audit columns.

Common Use Cases and Queries

Typical use cases include budget-versus-actual reporting, baseline budget extraction for revenue and cost forecasting, and funding/budgetary-control integration. Because PA_BUDGET_LINES joins cleanly to PA_BUDGET_VERSIONS and PA_RESOURCE_ASSIGNMENTS, most queries filter by budget version and project. A representative pattern:

• List all lines for a version: SELECT BUDGET_LINE_ID, RESOURCE_ASSIGNMENT_ID, START_DATE, QUANTITY, RAW_COST, BURDENED_COST, REVENUE FROM PA_BUDGET_LINES WHERE BUDGET_VERSION_ID = :version_id ORDER BY START_DATE;
• Multi-currency comparison: select TXN amounts alongside PROJECT amounts and their exchange rate type/date columns to reconcile currencies.
• Budget versus actual: match budgeted RAW_COST/BURDENED_COST against expenditure items by RESOURCE_ASSIGNMENT_ID and period.
• Rejection diagnostics: select rows where COST_REJECTION_CODE or REVENUE_REJECTION_CODE is not null.
• Baseline audit: join to PA_BUDGET_VERSIONS to identify lines for the current baseline version.

Related Objects

PA_BUDGET_LINES sits between its parent budget version and its resource assignment. The most significant related objects are:

• PA_BUDGET_VERSIONS – parent version via PA_BUDGET_LINES.BUDGET_VERSION_ID.
• PA_RESOURCE_ASSIGNMENTS – budgeted resource via RESOURCE_ASSIGNMENT_ID.
• PA_MC_BUDGET_LINES – multi-currency budget lines referencing BUDGET_LINE_ID.
• PA_BC_PACKETS and PA_BC_COMMITMENTS_ALL – budgetary control packet and commitment records referencing BUDGET_LINE_ID.
• PA_COST_DISTRIBUTION_LINES_ALL – cost distribution lines tied to budget lines for funding control.
• GL_DAILY_CONVERSION_TYPES – referenced by the many exchange rate type columns.
• GL_CODE_COMBINATIONS – accounting flexfield via CODE_COMBINATION_ID.
• PA_FP_SPREAD_CALC_TMP and PA_BUDGET_LINES_M_UPG_DTRANGE – temporary and upgrade utility tables referencing BUDGET_LINE_ID.

These relationships confirm PA_BUDGET_LINES as the de facto detail satellite for project budgeting, joined on BUDGET_LINE_ID, BUDGET_VERSION_ID, and RESOURCE_ASSIGNMENT_ID.