Search Results top_task_number




Overview
Explore in AI Chat

Overview

APPS.GMS_TASK_BAL_V is a reporting view in the Oracle E-Business Suite Grants Management (GMS) module, available in releases 12.1.1 and 12.2.2. It presents award budget balances aggregated at the top task level, combining budget, actual, and encumbrance amounts for a given award, project, and budget version. The view is a consolidation layer built on top of GMS_AWARD_BAL_V, whose rows are grouped and summed so that each combination of award, project, top task, and budget version yields a single summarized balance record. Its name and structure indicate that it is intended to support grant and award financial reporting, particularly where users need consolidated balances by top-level task rather than the fully exploded detail available from the award-level balance view.

Because it exposes pre-aggregated, ready-to-query balances, the view is well suited to integration and reporting scenarios such as Oracle Discoverer worksheets, BI Publisher reports, custom concurrent programs, and third-party interfaces that consume award financial data. The searched term "top_task_id" corresponds directly to one of the view's grouping keys, making it a natural entry point for queries that pivot award balances by task hierarchy root.

Underlying Base Objects

The ETRM metadata documents exactly two referenced objects for this view:

  • GMS_AWARD_BAL_V (VIEW) — the immediate source of all data. GMS_TASK_BAL_V selects its columns and applies a GROUP BY over budget_version_id, award_id, project_id, top_task_id, the derived task number, start_date, and end_date, summing budget, actuals, and encumbrances. This makes GMS_TASK_BAL_V a dependent view on GMS_AWARD_BAL_V rather than on base tables directly.
  • GMS_BUDGET_UTILS (PACKAGE) — a PL/SQL utility package, used here through the function GMS_BUDGET_UTILS.GET_TASK_NUMBER(top_task_id), which returns the task number for a given top task identifier. This function is invoked both in the SELECT list and in the GROUP BY clause, so its result participates in the aggregation grouping.

This dependency chain means that changes to GMS_AWARD_BAL_V or to GMS_BUDGET_UTILS propagate to GMS_TASK_BAL_V, and query performance depends on the underlying award balance view's efficiency.

Key Columns

  • PROJECT_ID — identifies the project to which the award and task belong.
  • AWARD_ID — the award identifier, used together with project_id to scope balances.
  • TOP_TASK_ID — the identifier of the top-level task (the root of the task hierarchy) for which balances are aggregated; this is the primary grouping dimension that distinguishes this view from GMS_AWARD_BAL_V. The search term "top_task_id" maps directly to this column.
  • GMS_BUDGET_UTILS.GET_TASK_NUMBER(TOP_TASK_ID) — a derived column returning the human-readable task number associated with the top task.
  • BUDGET_VERSION_ID — identifies the budget version being reported, allowing comparison across versions.
  • START_DATE / END_DATE — the date range associated with the aggregated balances.
  • SUM(BUDGET) — total budgeted amount for the award/project/top task/version grouping.
  • SUM(ACTUALS) — total actual expenditure or cost recorded for the grouping.
  • SUM(ENCUMBRANCES) — total encumbered amounts, representing committed but not yet actualized funds.

Common Use Cases and Queries

Typical scenarios include consolidated award balance reporting by top task, budget-versus-actual variance analysis, and extraction of encumbrance balances for funding reviews. A basic query retrieving balances for a specific top task might appear as follows:

SELECT project_id,
       award_id,
       top_task_id,
       budget_version_id,
       start_date,
       end_date,
       SUM(budget)        AS budget,
       SUM(actuals)       AS actuals,
       SUM(encumbrances)  AS encumbrances
FROM   apps.gms_task_bal_v
WHERE  top_task_id = :p_top_task_id
GROUP  BY project_id, award_id, top_task_id,
          budget_version_id, start_date, end_date;

A second common pattern joins the view to project and award tables to produce a report keyed by task number and award name. Because the view already aggregates by top task, consumers should be aware that task-level detail below the top task is not available from this object; the full detail resides in GMS_AWARD_BAL_V. Queries should therefore be directed to GMS_TASK_BAL_V only when top-task-level totals are the intended granularity.