Results for “budget_lines”

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

Overview

GMS.GMS_BUDGET_LINES is a transactional table in the Oracle EBS Grants Management (GMS) schema that stores the detail rows of a project or task budget. Each row captures a single budget line, tying a resource assignment to a specific time period and holding the budgeted quantity, raw cost, burdened cost, and revenue amounts. A defining characteristic of the table is that the time period is not restricted to a single calendar: the PERIOD_NAME may reference a Projects period, a General Ledger period, or any user-defined period, which allows budgeting cadences to follow client-specific reporting conventions.

The table belongs to the APPS_TS_TX_DATA tablespace and carries standard Oracle EBS Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) for audit purposes. It also exposes a full Descriptive Flexfield via ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15, enabling customer-specific extensions without schema modification. From a Data Vault modeling perspective, the mined relationship structure classifies this object as satellite-leaning: it keys to a parent resource assignment, which is central to the budget taxonomy. This classification is a heuristic suggestion based on foreign-key structure rather than a mandated design.

Key Information Stored

The primary key is GMS_BUDGET_LINES_PK, composed of RESOURCE_ASSIGNMENT_ID and START_DATE. It is reinforced by the unique index cited in the search term, GMS_BUDGET_LINES_U1, defined on the same two columns and stored in APPS_TS_TX_IDX. Both serve as the business-key candidates for uniquely identifying a budget line.

• RESOURCE_ASSIGNMENT_ID — Identifier of the resource assignment for the budget line; the foreign-key component linking to GMS_RESOURCE_ASSIGNMENTS.
• START_DATE / END_DATE — The effective span of the budget line, which together with PERIOD_NAME defines the budgeting window.
• PERIOD_NAME — The Projects, GL, or user-defined period the line belongs to.
• QUANTITY — Units budgeted for the line.
• RAW_COST, BURDENED_COST, REVENUE — The core monetary measures: unburdened cost, fully burdened cost, and expected revenue.
• RAW_COST_SOURCE, BURDENED_COST_SOURCE, QUANTITY_SOURCE, REVENUE_SOURCE — Source indicators documenting how each amount was derived.
• CHANGE_REASON_CODE, DESCRIPTION — Context explaining why the line exists or was modified.
• PM_PRODUCT_CODE, PM_BUDGET_LINE_REFERENCE — Cross-references into Oracle Project Management structures for traceability.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive Flexfield context and segments.

Common Use Cases and Queries

The most frequent use is budget-versus-actual reporting at the resource assignment level. A typical query aggregates budgeted amounts by project, task, or period:

SELECT resource_assignment_id, period_name, start_date, end_date,
       SUM(raw_cost) raw_cost, SUM(burdened_cost) burdened_cost,
       SUM(revenue) revenue, SUM(quantity) quantity
FROM   gms.gms_budget_lines
WHERE  period_name IN ('JAN-24','FEB-24')
GROUP  BY resource_assignment_id, period_name, start_date, end_date;

Other scenarios include identifying budget lines created by specific change-reason codes, tracing PM_BUDGET_LINE_REFERENCE values back to Project Management budgets, and extracting DFF segments for client-specific analysis. Because the table is large and transactional, queries should filter on RESOURCE_ASSIGNMENT_ID, START_DATE, or PERIOD_NAME to leverage GMS_BUDGET_LINES_U1 or the NONUNIQUE index GMS_BUDGET_LINES_N1 on START_DATE and END_DATE.

Related Objects

• GMS.GMS_RESOURCE_ASSIGNMENTS — Parent table referenced via GMS_BUDGET_LINES.RESOURCE_ASSIGNMENT_ID; supplies resource and assignment context.
• GMS_BUDGET_LINES_PK — Primary key constraint over RESOURCE_ASSIGNMENT_ID and START_DATE.
• GMS_BUDGET_LINES_U1 — Unique index (business-key candidate) over RESOURCE_ASSIGNMENT_ID and START_DATE in APPS_TS_TX_IDX.
• GMS_BUDGET_LINES_N1 — Nonunique index over START_DATE and END_DATE, supporting date-range filtering.
• Oracle Project Management budget APIs and views — Reference PM_PRODUCT_CODE and PM_BUDGET_LINE_REFERENCE for integrated project budgeting.
• GMS schema budget header and project/task tables — Provide the owning project and task context for each assignment.
• GL and Oracle Projects period definitions — Interpret PERIOD_NAME values that drive the line's accounting calendar.