Search Results gms_task_v




Overview
Explore in AI Chat

Overview

GMS_TASK_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMS – Grants Accounting product family. The view is documented as VALID and carries the description "Retrofitted," indicating it was reconstructed or adapted during an upgrade cycle rather than authored as a first-generation object. In both EBS 12.1.1 and 12.2.2 it exposes award task-level budget balances, aggregating budget, actual, and encumbrance amounts by award, project, task, and budget version.

Its role is primarily informational rather than transactional. Because the view is defined over another reporting view rather than directly over base tables, it functions as a convenience layer that presents pre-aggregated, task-numbered figures suitable for grants reporting, reconciliation, and downstream integration extracts. It does not store data; every query re-executes the underlying aggregation against GMS_AWARD_BAL_V.

Underlying Base Objects

The documented base objects referenced by GMS_TASK_V are:

  • GMS_AWARD_BAL_V (VIEW) – the immediate source of all rows, supplying budget, actual, and encumbrance balances along with the award, project, task, and budget version identifiers. GMS_TASK_V adds a GROUP BY aggregation on top of this view.
  • GMS_BUDGET_UTILS (PACKAGE) – invoked through the function GET_TASK_NUMBER(TASK_ID), which resolves a task identifier into its displayed task number. The function is called in both the SELECT list and the GROUP BY clause.

Because GMS_TASK_V is layered entirely on GMS_AWARD_BAL_V, its accuracy, performance, and row counts are inherited from that view and, transitively, from the Grants Accounting award and budget tables beneath it. There are no direct table references in the view text.

Key Columns

  • PROJECT_ID – identifier of the project associated with the award task.
  • AWARD_ID – identifier of the governing award.
  • TASK_ID – internal identifier of the task.
  • TASK_NUMBER – the task number returned by GMS_BUDGET_UTILS.GET_TASK_NUMBER(TASK_ID), suitable for display and reporting.
  • BUDGET_VERSION_ID – the budget version to which the aggregated amounts belong; a single award task may appear multiple times, once per version.
  • START_DATE / END_DATE – the effective date range associated with the task or budget version.
  • BUDGET – aggregated budgeted amount (SUM of the source view's budget column).
  • ACTUALS – aggregated actual expenditure (SUM of the source view's actuals column).
  • ENCUMBRANCES – aggregated encumbrance amount (SUM of the source view's encumbrances column).

Common Use Cases and Queries

Typical usage covers award task balance enquiry, funding-versus-spend analysis, and extract feeds to external grant reporting systems. Results are generally constrained by AWARD_ID or PROJECT_ID and narrowed to a single BUDGET_VERSION_ID to avoid double-counting across versions.

Example: retrieve task-level balances for one award and budget version:

  • SELECT award_id, project_id, task_id, task_number, budget, actuals, encumbrances FROM apps.gms_task_v WHERE award_id = :p_award_id AND budget_version_id = :p_version_id ORDER BY task_number;

Example: compute remaining availability at task level:

  • SELECT award_id, task_number, budget, actuals, encumbrances, (budget - actuals - encumbrances) available FROM apps.gms_task_v WHERE project_id = :p_project_id;

Example: summarize totals for an award across tasks:

  • SELECT award_id, budget_version_id, SUM(budget) total_budget, SUM(actuals) total_actuals FROM apps.gms_task_v WHERE award_id = :p_award_id GROUP BY award_id, budget_version_id;

Because the TASK_NUMBER column is derived through a PL/SQL function call, queries filtering on TASK_NUMBER may not benefit from ordinary indexes; filtering on TASK_ID or AWARD_ID generally performs better. The view should not be treated as a transactional interface, and no DML should be issued against it.