Search Results gms_award_bal_v




Overview
Explore in AI Chat

Overview

GMS_AWARD_BAL_V is a Grants Accounting (GMS) reporting view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It consolidates award-level financial balances — budget, actual expenditures, and encumbrances — into a single queryable structure keyed by project, award, task, resource list member, and budget version. The view is documented as a retrofitted object, meaning it was adapted to preserve backwards compatibility and behavior across release levels while the underlying GMS schema evolved.

Its principal role is to serve as the reporting and integration layer for award balance inquiries, particularly those driven by period-to-date (PTD) measures. Users searching for "actual_period_to_date" are typically looking to reconcile expenditure activity recorded against an award for a defined accounting or project period. In GMS_AWARD_BAL_V this concept is surfaced through the ACTUALS column, which is populated in part from SUM(NVL(ACTUAL_PERIOD_TO_DATE,0)) against GMS_BALANCES and from debit/credit activity in the GMS_BC_PACKETS award packet table. The view therefore allows actual period-to-date figures to be retrieved at the award, task, project, and resource level without querying the base balance tables directly.

Underlying Base Objects

The view text is a three-way UNION ALL. The first branch aggregates GMS_BALANCES, filtering on BALANCE_TYPE IN ('AP','BGT','ENC','EXP','PO','REQ') and summing the period-to-date budget, actual, and encumbrance columns. The second and third branches aggregate GMS_BC_PACKETS joined to PA_PERIODS and GL_PERIOD_STATUSES respectively, depending on the TIME_PHASED_TYPE_CODE ('P' for project periods or 'G' for GL periods), and derive actuals and encumbrances from ENTERED_DR less ENTERED_CR.

The documented referenced objects include the synonyms GMS_BALANCES, GMS_BC_PACKETS, GMS_AWARDS, GMS_BUDGET_VERSIONS, PA_PERIODS, PA_PROJECTS_ALL, PA_TASKS, PA_BUDGET_ENTRY_METHODS, and GL_PERIOD_STATUSES, along with the helper views GMS_DTRANGE_BAL_V and GMS_NONE_BAL_V. These provide the project, task, award, period, and budget definition context required to interpret the raw balance and packet amounts.

Key Columns

  • PROJECT_ID, AWARD_ID, TASK_ID: The award and project/task dimensions the balance belongs to; TASK_ID and TOP_TASK_ID are NVL'd to 0 for top-task reporting.
  • RESOURCE_LIST_MEMBER_ID, PARENT_MEMBER_ID: Identify the burden/resource structure associated with the balance.
  • BUDGET_VERSION_ID: The approved budget version against which balances are reported.
  • START_DATE, END_DATE: Period start and end boundaries derived from PA or GL periods.
  • BUDGET: Aggregate period-to-date budget from GMS_BALANCES.
  • ACTUALS: Period-to-date actual expenditures, mapping directly to ACTUAL_PERIOD_TO_DATE.
  • ENCUMBRANCES: Period-to-date commitments for requisitions, purchase orders, and other encumbrance types.
  • TOP_TASK_ID: Top-level task for hierarchical reporting.

Common Use Cases and Queries

Typical use cases include verifying award actual period-to-date spend, comparing budget to actuals for a budget version, and reconciling encumbrance exposure per award. A representative query is:

SELECT project_id, award_id, task_id, resource_list_member_id, budget_version_id, start_date, end_date, budget, actuals, encumbrances FROM apps.gms_award_bal_v WHERE award_id = :award_id AND start_date >= :period_start AND end_date <= :period_end;

To isolate actual period-to-date figures for a resource, filter on resource_list_member_id and budget_version_id and compare the ACTUALS column across periods. Because ACTUALS originates from ACTUAL_PERIOD_TO_DATE in GMS_BALANCES, results reflect stored period-to-date balances rather than a running cumulative total, so care is required when summing across periods.