Search Results gms_budget_lines




Overview
Explore in AI Chat

Overview

The GMS_BUDGET_LINES table is a core data object within the Oracle E-Business Suite Grants Accounting (GMS) module, specifically for releases 12.1.1 and 12.2.2. It functions as the detailed transactional repository for project and task budgets. While higher-level budget headers define the overall funding and periods, this table stores the granular, time-phased financial plan. Each record represents a specific budgeted amount for a particular resource assignment over a defined period, enabling precise tracking of planned expenditures against awarded grants and contracts. Its integrity is critical for generating accurate budgetary control, expenditure reporting, and fund availability checks throughout the project lifecycle.

Key Information Stored

The table's structure is designed to capture the detailed breakdown of a budget. The primary key, composed of RESOURCE_ASSIGNMENT_ID and START_DATE, ensures uniqueness for each budget line entry. While the provided metadata specifies these key columns, typical columns in such a detail table would include, by inference and common schema patterns, the associated BUDGET_VERSION_ID, TASK_ID, EXPENDITURE_TYPE, RAW_COST, BURDENED_COST, REVENUE_AMOUNT, and END_DATE. The RESOURCE_ASSIGNMENT_ID is the critical foreign key that links each detailed budget line back to its parent resource assignment definition in the GMS_RESOURCE_ASSIGNMENTS table, establishing the "what" (resource) for the budgeted amount.

Common Use Cases and Queries

This table is central to budgetary control and analysis within Grants Accounting. Common operational and reporting use cases include generating detailed budget versus actual reports, performing fund availability checks before incurring expenditures, and analyzing budget distributions across tasks and periods. A typical query might join GMS_BUDGET_LINES with GMS_RESOURCE_ASSIGNMENTS and project tables to summarize budgeted costs by task or expenditure type for a specific award.

Sample SQL Pattern:
SELECT gbl.start_date,
gbl.end_date,
gbl.raw_cost,
gra.resource_name
FROM gms_budget_lines gbl,
gms_resource_assignments gra
WHERE gbl.resource_assignment_id = gra.resource_assignment_id
AND gra.task_id = :p_task_id
ORDER BY gbl.start_date;

Related Objects

The GMS_BUDGET_LINES table has a documented, integral relationship with the GMS_RESOURCE_ASSIGNMENTS table, which defines the resources (people, equipment, etc.) assigned to project tasks. The relationship is enforced by a foreign key constraint where GMS_BUDGET_LINES.RESOURCE_ASSIGNMENT_ID references GMS_RESOURCE_ASSIGNMENTS. This means every detailed budget line must correspond to a valid, pre-existing resource assignment. While not listed in the provided excerpt, this table is also inherently linked to parent budget header tables (like GMS_BUDGET_VERSIONS) and project core tables (PA_PROJECTS, PA_TASKS) through the resource assignment entity, forming the complete budget hierarchy within the GMS architecture.