Search Results gms_task_bal_v




Overview
Explore in AI Chat

Overview

GMS_TASK_BAL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Grants Accounting (GMS) product family. Its documented status is VALID, and its ETRM description is recorded as "Retrofitted," indicating that the object was adapted for continued support across release lines, including the 12.1.1 and 12.2.2 code levels. The view exposes budget, actual, and encumbrance balances aggregated at the task level for awards and projects, making it a task-grain companion to the higher-level award balance view.

Rather than storing data, GMS_TASK_BAL_V is a pure aggregation layer. It is defined entirely over another view, GMS_AWARD_BAL_V, and a helper package, GMS_BUDGET_UTILS. Its role is to provide a consistent, denormalized read model that Grants Accounting reporting, inquiry screens, and integrations can consume without re-implementing the grouping and task-number derivation logic. Because it rolls balances up by top task, it is the natural source for task-level budget-versus-actual analysis and award performance reporting.

Underlying Base Objects

The ETRM metadata documents two referenced base objects for this view: GMS_AWARD_BAL_V (a VIEW) and GMS_BUDGET_UTILS (a PACKAGE).

  • GMS_AWARD_BAL_V is the immediate source of every column the view projects. All financial measures and the majority of descriptive keys originate here; GMS_TASK_BAL_V applies no filter predicates against it, so it inherits the full row population of the award balance view and simply re-aggregates it.
  • GMS_BUDGET_UTILS is invoked through its GET_TASK_NUMBER function. This function translates an internal TOP_TASK_ID into a user-facing task number, and it appears both in the SELECT list and in the GROUP BY clause, ensuring the derived task number participates in aggregation grouping consistently.

The grouping keys are BUDGET_VERSION_ID, AWARD_ID, PROJECT_ID, TOP_TASK_ID, the derived task number, START_DATE, and END_DATE. Applying SUM to BUDGET, ACTUALS, and ENCUMBRANCES collapses any finer-grained rows returned by GMS_AWARD_BAL_V so that one row represents one budget version of one task within one award and project for a defined date range.

Key Columns

The view exposes eleven columns, combining surrogate identifiers, a derived descriptive attribute, a date range, and three financial measures.

  • PROJECT_ID — identifies the project to which the task balances belong.
  • AWARD_ID — identifies the award funding the project and task.
  • TOP_TASK_ID — the internal identifier of the top-level task that anchors the aggregation.
  • TOP_TASK_NUMBER — the display value returned by GMS_BUDGET_UTILS.GET_TASK_NUMBER(TOP_TASK_ID), providing the human-readable task number for reporting.
  • BUDGET_VERSION_ID — the budget version against which balances are grouped, allowing comparison across revisions.
  • START_DATE and END_DATE — the effective range associated with the aggregated balance record.
  • BUDGET — the summed budgeted amount for the task.
  • ACTUALS — the summed actual expenditure recorded against the task.
  • ENCUMBRANCES — the summed encumbrance commitments, giving a full committed-cost picture alongside budget and actuals.

Common Use Cases and Queries

Typical uses include task-level budget utilization inquiries, award-versus-actual variance analysis, and feeds into custom dashboards or extracts that require balances at the top-task grain. The following query retrieves task balances for a specific award and budget version:

  • SELECT project_id, award_id, top_task_id, top_task_number, budget_version_id, start_date, end_date, budget, actuals, encumbrances FROM apps.gms_task_bal_v WHERE award_id = :award_id AND budget_version_id = :budget_version_id ORDER BY top_task_number;
  • Variance reporting can be produced directly in the query: SELECT top_task_number, budget, actuals, encumbrances, (budget - actuals - encumbrances) AS available_balance FROM apps.gms_task_bal_v WHERE project_id = :project_id;
  • Encumbrance exposure by task: SELECT top_task_number, SUM(encumbrances) FROM apps.gms_task_bal_v WHERE award_id = :award_id GROUP BY top_task_number;

Because the view depends on GMS_BUDGET_UTILS for the task number, performance is influenced by that function call within the grouping operation, and query plans should be reviewed when large result sets are processed.