Results for “gms_budget_versions”

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

Overview

GMS_BUDGET_VERSIONS is a table in the GMS (Grants Accounting) schema that stores versions of award budgets within Oracle E-Business Suite. In the grants management model, budgets are not static artifacts; they evolve through negotiation, baseline, revision, and re-baseline cycles, and each discrete state is captured as a separate row in this table. The object therefore serves as the authoritative record of every budget iteration associated with a project and an award, providing the historical and current context needed for sponsored-project financial management, indirect cost calculation, and reporting to funding agencies.

From a dimensional modeling perspective, the documented foreign-key structure — which references PA_PROJECTS_ALL, IGF_AW_AWARD_ALL, PA_BUDGET_TYPES, PA_BUDGET_ENTRY_METHODS, and PA_RESOURCE_LISTS_ALL_BG, while itself being referenced by GMS_RESOURCE_ASSIGNMENTS — suggests a satellite-leaning classification. It behaves as a descriptive child anchored to the project/award hub, holding version-specific attributes rather than defining independent business entities.

Key Information Stored

The table contains 51 documented columns. The surrogate primary key is BUDGET_VERSION_ID, enforced by the GMS_BUDGET_VERSIONS_PK constraint and also maintained as a unique index (GMS_BUDGET_VERSIONS_U1). A second unique index, GMS_BUDGET_VERSIONS_U2, defines the business-key candidate over PROJECT_ID, AWARD_ID, BUDGET_TYPE_CODE, BUDGET_STATUS_CODE, and VERSION_NUMBER — the natural combination that identifies a specific budget version.

• BUDGET_VERSION_ID — Surrogate primary key for the budget version.
• PROJECT_ID / AWARD_ID — Foreign keys to PA_PROJECTS_ALL and IGF_AW_AWARD_ALL, anchoring the version to its funded project and award.
• BUDGET_TYPE_CODE — References PA_BUDGET_TYPES (for example, approved cost or revenue budgets).
• VERSION_NUMBER / VERSION_NAME — Sequencing and user-facing label for the budget iteration.
• BUDGET_STATUS_CODE — Workflow or lifecycle state of the version (draft, submitted, baselined, rejected).
• CURRENT_FLAG / ORIGINAL_FLAG / CURRENT_ORIGINAL_FLAG — Indicators identifying the active, first-baselined, or current-original version.
• RESOURCE_LIST_ID — References PA_RESOURCE_LISTS_ALL_BG, defining the resource structure used to build the budget.
• BUDGET_ENTRY_METHOD_CODE — References PA_BUDGET_ENTRY_METHODS, indicating how amounts were entered.
• LABOR_QUANTITY / LABOR_UNIT_OF_MEASURE / RAW_COST / BURDENED_COST / REVENUE — Aggregate budget amounts and quantities.
• BASELINED_BY_PERSON_ID / BASELINED_DATE — Audit trail for baseline approval.
• WF_STATUS_CODE / PRC_GENERATED_FLAG / CONC_REQUEST_ID — Workflow and concurrent-process tracking.

Common Use Cases and Queries

The most frequent access pattern retrieves the current budget version for a project or award, typically filtered on CURRENT_FLAG or the highest VERSION_NUMBER for a given BUDGET_TYPE_CODE. Reporting queries join to PA_PROJECTS_ALL and IGF_AW_AWARD_ALL to present budget-versus-actual comparisons, and to GMS_RESOURCE_ASSIGNMENTS to explode line-level resource detail.

• Identify the active baselined budget for an award:

  SELECT bv.budget_version_id, bv.version_number, bv.budget_status_code,
         bv.raw_cost, bv.burdened_cost, bv.revenue
  FROM   gms_budget_versions bv
  WHERE  bv.project_id = :project_id
  AND    bv.award_id   = :award_id
  AND    bv.current_flag = 'Y';

• Audit full budget version history for a project, ordered by version.
• Feed indirect cost and revenue calculations using RAW_COST, BURDENED_COST, and REVENUE.
• Drive approval workflow monitoring using WF_STATUS_CODE and CONC_REQUEST_ID.

Related Objects

• PA_PROJECTS_ALL — joined on PROJECT_ID; source of project context.
• IGF_AW_AWARD_ALL — joined on AWARD_ID; source of award context.
• PA_BUDGET_TYPES — joined on BUDGET_TYPE_CODE.
• PA_BUDGET_ENTRY_METHODS — joined on BUDGET_ENTRY_METHOD_CODE.
• PA_RESOURCE_LISTS_ALL_BG — joined on RESOURCE_LIST_ID.
• GMS_RESOURCE_ASSIGNMENTS — child table referencing BUDGET_VERSION_ID, holding resource-level budget lines.