Results for “gms_budget_matrix_v”

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

Overview

GMS_BUDGET_MATRIX_V is an APPS-owned database view in the Oracle E-Business Suite Grants Accounting (GMS) module. It is a retrofitted reporting object, meaning it was re-implemented during the transition to the multi-org, multi-language architecture of EBS 12.1.1 and 12.2.2 to preserve the behavior expected by legacy Grants Accounting reports and integrations.

The view presents a queryable, denormalized representation of budget matrix data. The term "matrix" reflects the fact that Grants budget data is stored in a cross-tabulated form: each budget line carries quantity, raw cost, burdened cost, and revenue values that are pivoted according to an award/resource lookup code. The view resolves those pivoted values into a single flat row so that reporting tools, concurrent programs, and external integrations can retrieve them without invoking the GMS_BUDGET_MATRIX PL/SQL package directly. Because it is a view rather than a table, it introduces no physical storage and always reflects the current state of the underlying budget lines.

The user search term "p1_amt" corresponds to the amount style columns surfaced by the view. The view text exposes DF_LONG_P1_1 and DF_LONG_P1_2 descriptor-flex concatenations, and the amount columns are derived through DECODE on the lookup code, so a "p1 amount" style column typically resolves the quantity, raw cost, burdened cost, or revenue figure depending on the row's LOOKUP_CODE.

Underlying Base Objects

The documented base objects referenced by GMS_BUDGET_MATRIX_V are:

• GMS_BUDGET_LINES — the primary source of budget line records, keyed by BUDGET_VERSION_ID and TASK_ID.
• GMS_RESOURCE_ASSIGNMENTS — supplies the RESOURCE_ASSIGNMENT_ID and UNIT_OF_MEASURE and TRACK_AS_LABOR_FLAG attributes.
• PA_RESOURCE_LIST_MEMBERS — joins resource list membership, providing RESOURCE_LIST_MEMBER_ID, RESOURCE_LIST_ID, RESOURCE_ID, and ALIAS.
• FND_LOOKUP_VALUES — provides lookup meanings and the lookup code that drives the DECODE logic and display order.
• GMS_BUDGET_MATRIX (PACKAGE) — the underlying PL/SQL package whose matrix logic the view mirrors for set-based access.

The DECODE expressions compare the lookup code against 'QU' (quantity), 'RC' (raw cost), 'BC' (burdened cost), and 'RE' (revenue). Up to four parallel budget amount sets (C, C2, C3, C4) are pivoted from the budget lines, which is what allows the view to return up to four amount columns per row.

Key Columns

• BUDGET_VERSION_ID — identifies the budget version to which the row belongs.
• TASK_ID — the task within the award associated with the budget line.
• RESOURCE_ASSIGNMENT_ID — the resource assignment that generated the line.
• RESOURCE_LIST_MEMBER_ID / RESOURCE_LIST_ID / RESOURCE_ID / ALIAS — resource list member identity and short alias.
• UNIT_OF_MEASURE — the unit for quantity-type lines.
• TRACK_AS_LABOR_FLAG — indicates whether the resource is tracked as labor.
• LOOKUP_CODE and MEANING — the budget category (QU, RC, BC, RE) and its display meaning.
• The four DECODE columns returning QUANTITY, RAW_COST, BURDENED_COST, or REVENUE depending on the lookup code — the "p1_amt"-style amount columns.
• DF_LONG_P1_1 and DF_LONG_P1_2 — concatenated descriptor-flex attribute strings (ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY, CHANGE_REASON_CODE, DESCRIPTION) padded with the delimiter "(|)" for downstream parsing.

Common Use Cases and Queries

The view is typically queried to reconcile budget matrix data for an award/task, to feed Grants budget inquiry screens, or to export budget amounts to a custom interface. A representative query retrieving one budget version's amounts follows:

• SELECT budget_version_id, task_id, resource_assignment_id, lookup_code, meaning FROM apps.gms_budget_matrix_v WHERE budget_version_id = :p_budget_version_id ORDER BY decode_order;
• SELECT m.task_id, m.alias, m.lookup_code, m.meaning, m.unit_of_measure FROM apps.gms_budget_matrix_v m WHERE m.budget_version_id = :p_version AND m.resource_list_id = :p_resource_list;
• SELECT m.resource_assignment_id, m.df_long_p1_1 FROM apps.gms_budget_matrix_v m WHERE m.track_as_labor_flag = 'Y';

Because the amount columns are resolved via DECODE on LOOKUP_CODE, consumers should always filter or group by LOOKUP_CODE to avoid mixing quantity, raw cost, burdened cost, and revenue values in a single aggregation. The padded descriptor-flex columns should be split on the "(|)" delimiter before use in downstream reporting.