Results for “pa_budget_matrix_v”

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

Overview

PA_BUDGET_MATRIX_V is a Projects (PA) module view owned by the APPS schema, carrying a status of VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM as a retrofitted object, meaning the underlying definition was carried forward from earlier releases with minimal modification and remains exposed for backward compatibility with existing reports, integrations, and extensions.

The view presents project budget data in a pivot-style format, transforming budget amounts into a matrix of period or resource-oriented columns. Rather than storing one row per amount type, it uses DECODE logic against an FND lookup code to selectively surface quantity, raw cost, burdened cost, or revenue values into dedicated columns. This makes the view particularly relevant when an application or report expects budget figures already separated by measure, without requiring the consumer to apply the DECODE logic itself. A user searching for "p2_amt" is typically working with a legacy query or report list that references this matrix layout, where positional amount columns are aliased in the client layer rather than in the view definition.

The view serves as a reporting and integration surface over the budget matrix package, isolating consumers from the physical structure of PA_BUDGET_LINES and related resource data.

Underlying Base Objects

ETRM documents five referenced objects, all resolved through APPS synonyms:

• PA_BUDGET_LINES — the core budget line table supplying amounts, quantity, raw cost, burdened cost, and revenue values per budget version and task.
• PA_RESOURCE_ASSIGNMENTS — supplies the resource assignment identifier that links a budget line to a specific assigned resource.
• PA_RESOURCE_LIST_MEMBERS — provides the resource list membership, resource list, resource identifier, alias, and unit of measure context.
• FND_LOOKUP_VALUES — the lookup source for the amount-type code (QU, RC, BC, RE) that drives the DECODE projections.
• PA_BUDGET_MATRIX (PACKAGE) — the PL/SQL package that drives construction and formatting of the matrix output.

The joins are anchored on BUDGET_VERSION_ID and TASK_ID from the budget lines, extended by C2, C3, and C4 aliases representing additional budget line instances that populate successive amount columns within the matrix.

Key Columns

• BUDGET_VERSION_ID, TASK_ID — the primary partitioning keys for a budget matrix row.
• RESOURCE_ASSIGNMENT_ID, RESOURCE_LIST_MEMBER_ID, RESOURCE_LIST_ID, RESOURCE_ID — resource identity and assignment context.
• ALIAS, UNIT_OF_MEASURE, TRACK_AS_LABOR_FLAG — descriptive resource attributes.
• LOOKUP_CODE — the measure discriminator: QU (quantity), RC (raw cost), BC (burdened cost), RE (revenue).
• DECODE(LOOKUP_CODE, ...) columns — the pivoted amount columns, each resolving to the measure appropriate to the lookup code.
• DECODE sort column — yields 1 for QU, 2 for RC, 3 for BC, 4 for RE, providing deterministic ordering.
• DF_LONG_P1_1, DF_LONG_P1_2 — concatenated descriptor fields built from ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY, CHANGE_REASON_CODE, and DESCRIPTION, padded with RPAD to fixed widths.

Common Use Cases and Queries

Typical use cases include budget-versus-actual reporting, resource-level cost distribution, and integration feeds that require budget amounts separated by measure.

SELECT budget_version_id, task_id, resource_id, alias,
       unit_of_measure, lookup_code
FROM   apps.pa_budget_matrix_v
WHERE  budget_version_id = :p_budget_version_id
AND    task_id = :p_task_id;

Filtering by measure isolates a single amount stream:

SELECT budget_version_id, task_id, resource_id
FROM   apps.pa_budget_matrix_v
WHERE  lookup_code IN ('RC','BC')
AND    resource_list_id = :p_resource_list_id;

Because the view resolves synonyms across the APPS schema, queries should be executed with APPS or MO responsibilities and appropriate Projects security applied. The p2_amt naming convention commonly appears in module-level reports that map the pivoted amount columns positionally, so column order and DECODE behavior should be treated as stable across 12.1.1 and 12.2.2.