Search Results gms_resg_v




Overview
Explore in AI Chat

Overview

GMS_RESG_V is an Oracle E-Business Suite seeded view owned by the APPS schema and shipped with the Grants Accounting (GMS) product family. It is classified in the ETRM repository as VALID and carries the description "Retrofitted," indicating that it was re-implemented or carried forward from an earlier release into the 12.1.1 / 12.2.2 code line. Functionally, GMS_RESG_V presents award-level budget, actual, and encumbrance balances aggregated by resource group and (optionally) by task, depending on the budget entry method used by the associated budget version. It is a reporting and integration view rather than a transactional entity; no direct DML should be performed against it. In Oracle EBS 12.1.1 and 12.2.2 the view remains a read-only presentation layer used by grant-funding inquiries, budget-versus-actual analysis, and downstream extracts that need resource-group roll-ups without interrogating the underlying award balance view directly.

Underlying Base Objects

The view text is a join and aggregation across several documented objects. Its primary driver is GMS_AWARD_BAL_V, aliased as GMS, which supplies budget, actual, and encumbrance amounts together with project, award, task, and resource-list member identifiers. Budget entry semantics are resolved through GMS_BUDGET_VERSIONS (a synonym to the budget version table) joined to PA_BUDGET_ENTRY_METHODS on BUDGET_ENTRY_METHOD_CODE; the ENTRY_LEVEL_CODE from the entry method drives DECODE logic that suppresses task-level detail when the method is project-level ('P'). Resource attribution is resolved through PA_RESOURCE_LIST_MEMBERS and PA_RESOURCES, both documented synonyms, so that PR.NAME yields the resource group name. A NOT EXISTS subquery against PA_RESOURCE_LISTS and PA_RESOURCE_LIST_MEMBERS excludes resource lists whose GROUP_RESOURCE_TYPE_ID is zero. Two packages, GMS_BUDGET_UTILS and PA_CROSS_BUSINESS_GRP, plus FND_PROFILE are referenced in the documented dependency list; GMS_BUDGET_UTILS.GET_TASK_NUMBER is invoked in the SELECT list to derive the task number, and FND_PROFILE typically supplies multi-org and MOAC context.

Key Columns

The view exposes thirteen columns. PROJECT_ID, AWARD_ID, and BUDGET_VERSION_ID are the core keys linking to PA_PROJECTS, GMS_AWARDS, and budget version records respectively. TASK_ID and TOP_TASK_ID identify the task hierarchy; both return zero when the budget entry method is project-level, so consumers must interpret zero as "no task breakdown." TASK is the formatted task number produced by GMS_BUDGET_UTILS.GET_TASK_NUMBER. PARENT_MEMBER_ID is derived via DECODE so that a null parent falls back to the RESOURCE_LIST_MEMBER_ID and the value zero also maps to RESOURCE_LIST_MEMBER_ID; RESOURCE_GROUP_NAME carries the resource name from PA_RESOURCES. START_DATE and END_DATE bound the budget version period. The three measure columns — BUDGET, ACTUALS, and ENCUMBRANCES — are each summed in the GROUP BY, delivering consolidated figures per project/award/version/task/resource-group combination.

Common Use Cases and Queries

Typical usage includes award budget-versus-actual reports, encumbrance exposure analysis, and resource-group-level extracts for grants reconciliation. A representative query is:

  • SELECT project_id, award_id, task, resource_group_name, SUM(budget), SUM(actuals), SUM(encumbrances) FROM apps.gms_resg_v WHERE award_id = :award_id GROUP BY project_id, award_id, task, resource_group_name;
  • SELECT budget_version_id, resource_group_name, budget - actuals AS variance FROM apps.gms_resg_v WHERE project_id = :project_id AND budget_version_id = :version_id;
  • SELECT * FROM apps.gms_resg_v WHERE start_date >= :from_date AND end_date <= :to_date;

Because the view already aggregates, additional filters on PROJECT_ID or BUDGET_VERSION_ID are advisable for performance. Callers should also account for the project-level DECODE behavior, which returns TASK_ID of zero and a null TASK for entry methods flagged 'P'.