Results for “gms_budget_lines_pk”

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

Overview

GMS.GMS_BUDGET_LINES is the detail-level budget table within the Oracle E-Business Suite Grants Accounting (GMS) module. It stores the individual line items that make up project and task budgets, capturing the quantities, costs, and revenue amounts planned for a specific resource assignment over a defined period. While the parent budgeting structures define the overall financial plan for an award or project, this table records the granular, time-phased detail used for cost planning, budget-versus-actual comparisons, and award compliance reporting.

In Data Vault modeling terms, the heuristic classification for this object is satellite-leaning. Its composite primary key (RESOURCE_ASSIGNMENT_ID, START_DATE) anchors each row to a parent resource assignment while adding descriptive, time-varying measures such as cost and quantity. This suggests its natural role is a satellite attached to the resource assignment hub/link rather than an independent hub or associative link.

Key Information Stored

The table contains 37 documented columns. The most significant include:

• RESOURCE_ASSIGNMENT_ID and START_DATE — the composite primary key (GMS_BUDGET_LINES_PK) and business-key candidate exposed via unique index GMS_BUDGET_LINES_U1. Together they identify the assignment and the effective start of the budget line.
• END_DATE — the effective end of the budget line's validity window.
• PERIOD_NAME — the accounting period to which the line belongs, enabling period-based reporting.
• QUANTITY — the planned resource quantity (for example, hours or units).
• RAW_COST, BURDENED_COST, and REVENUE — the core financial measures for the line.
• RAW_COST_SOURCE, BURDENED_COST_SOURCE, QUANTITY_SOURCE, REVENUE_SOURCE — indicators describing the origin or derivation method of each corresponding measure.
• CHANGE_REASON_CODE and DESCRIPTION — audit and explanatory context for line modifications.
• PM_PRODUCT_CODE and PM_BUDGET_LINE_REFERENCE — cross-reference fields tying the line back to project management budget structures.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield columns for extensible client-specific data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical reporting and integration scenarios include budget-versus-actual analysis, period-by-period cost forecasting, and reconciliation between Grants Accounting budgets and Oracle Projects. A common join retrieves budget detail alongside the resource assignment:

SELECT b.RESOURCE_ASSIGNMENT_ID, b.START_DATE, b.PERIOD_NAME, b.QUANTITY, b.RAW_COST, b.BURDENED_COST, b.REVENUE FROM GMS.GMS_BUDGET_LINES b WHERE b.RESOURCE_ASSIGNMENT_ID = :assignment_id ORDER BY b.START_DATE;

Aggregation by period supports time-phased reporting:

SELECT PERIOD_NAME, SUM(BURDENED_COST), SUM(REVENUE) FROM GMS.GMS_BUDGET_LINES GROUP BY PERIOD_NAME;

Analysts also filter on CHANGE_REASON_CODE to audit budget revisions and inspect the *_SOURCE columns to confirm whether amounts were entered manually or derived from an external planning source.

Related Objects

The most significant relationship is the foreign key to GMS.GMS_RESOURCE_ASSIGNMENTS, joined on GMS_BUDGET_LINES.RESOURCE_ASSIGNMENT_ID = GMS_RESOURCE_ASSIGNMENTS.RESOURCE_ASSIGNMENT_ID. This parent table supplies the resource, project, and task context for every budget line. Reporting queries typically extend this join to project- and award-level tables within the GMS schema, and to Oracle Projects (PA) budget and expenditure objects via the PM_BUDGET_LINE_REFERENCE and PM_PRODUCT_CODE cross-reference columns. The unique index GMS_BUDGET_LINES_U1 enforces the business-key uniqueness on the assignment and start date combination, ensuring a single budget line per assignment per effective date.