Results for “pa_budget_lines_v”

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

Overview

PA_BUDGET_LINES_V is an Oracle Projects (PA) reporting view owned by the APPS schema. It exposes budget line detail at the level of the resource assignment, combining header attributes from PA_RESOURCE_ASSIGNMENTS, resource definition attributes from PA_RESOURCE_LIST_MEMBERS, and descriptive decode values from PA_LOOKUPS. The view is documented as "10SC Only," indicating a product-specific or locale-specific scope rather than a fully general-purpose Projects interface object.

In Oracle EBS 12.1.1 and 12.2.2, the view serves as a flattened, query-ready presentation of budget line data. It shields report developers and integration code from the multi-table join logic required to resolve resource names, unit-of-measure meanings, change reason meanings, and budget line amounts. Because it carries budget version, project, and task context alongside quantity, raw cost, burdened cost, and revenue figures, it is useful for budget-versus-actual comparisons at the lowest budgetable grain.

Underlying Base Objects

The view is defined over four referenced objects:

• PA_BUDGET_LINES (synonym) — the primary source of budget line rows, supplying quantity, raw cost, burdened cost, revenue, period, dates, currency, attributes, and the *_SOURCE columns.
• PA_RESOURCE_ASSIGNMENTS (synonym) — supplies budget version, project, task, resource list member, unit of measure, and the track-as-labor flag.
• PA_RESOURCE_LIST_MEMBERS (synonym) — supplies resource list, resource, and alias (rendered as RESOURCE_NAME).
• PA_LOOKUPS (view) — supplies decoded meanings for unit of measure (LOOKUP_TYPE = 'UNIT') and change reason (LOOKUP_TYPE = 'BUDGET CHANGE REASON').

Joins are made on RESOURCE_ASSIGNMENT_ID and RESOURCE_LIST_MEMBER_ID, with lookup joins defined as outer joins. A filter excludes resource list members where NVL(M.MIGRATION_CODE,'-99') = 'N'. Lookup joins carry the (+) outer-join operator on the PA_LOOKUPS side.

Key Columns

• ROW_ID, RESOURCE_ASSIGNMENT_ID — row identity and the assignment-level key linking to PA_RESOURCE_ASSIGNMENTS.
• BUDGET_VERSION_ID, PROJECT_ID, TASK_ID — the budget and project/task context for each line.
• RESOURCE_LIST_ID, RESOURCE_ID, RESOURCE_NAME — resource membership and display name (the ALIAS column).
• QUANTITY, UNIT_OF_MEASURE, UNIT_OF_MEASURE_M — budgeted quantity and its decoded unit meaning.
• RAW_COST, BURDENED_COST, REVENUE — the three primary monetary measures carried on the line.
• RAW_COST_SOURCE, BURDENED_COST_SOURCE, QUANTITY_SOURCE, REVENUE_SOURCE — provenance indicators describing how each measure was derived. These directly answer searches for burdened_cost_source.
• CHANGE_REASON_CODE, CHANGE_REASON_M — change reason code and its decoded meaning.
• PERIOD_NAME, START_DATE, END_DATE, TXN_CURRENCY_CODE — periodicity, effective dates, and transaction currency.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segments.

Common Use Cases and Queries

Typical uses include budget line extracts for reporting, reconciliation of burdened cost against raw cost, and auditing of how cost and quantity figures were sourced. The following query returns budget lines with their sourcing indicators for a given project:

• SELECT project_id, task_id, budget_version_id, resource_name, quantity, unit_of_measure_m, raw_cost, raw_cost_source, burdened_cost, burdened_cost_source, revenue, revenue_source FROM pa_budget_lines_v WHERE project_id = :p_project_id ORDER BY task_id, resource_name;
• SELECT period_name, SUM(raw_cost) raw, SUM(burdened_cost) burdened, SUM(revenue) revenue FROM pa_budget_lines_v WHERE budget_version_id = :p_version GROUP BY period_name ORDER BY period_name;
• SELECT change_reason_m, COUNT(*) FROM pa_budget_lines_v WHERE project_id = :p_project_id GROUP BY change_reason_m;

Because the view resolves lookups and resource membership, it is a convenient single source for budget line reporting without re-implementing the base joins. Note the 10SC-only scope and the migration filter before relying on it for general Projects reporting.