Search Results gms_ssa_awards_v




Overview
Explore in AI Chat

Overview

GMS_SSA_AWARDS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Grants Accounting (GMS) product family. Its name reflects its purpose: it exposes award records that are eligible for the Sponsored Projects Self-Service Awards (SSA) function, filtered to awards using a deferred (sponsored) award template. The view consolidates award header information with the project and task structures that were created from those awards, producing a single denormalized result set suitable for self-service inquiry screens, concurrent reporting, and downstream integration.

Unlike a simple table synonym, this view embeds significant business logic. Only awards with a status of AT_RISK or ACTIVE, an AWARD_TEMPLATE_FLAG of DEFERRED, and at least one baselined budget version are surfaced. The view therefore represents operationally live, budgeted sponsored awards together with their associated projects and chargeable tasks, which is precisely the population of interest to grants administrators and principal investigators using self-service pages.

Underlying Base Objects

The view is defined over a join of several GMS and Oracle Projects objects, all accessed through APPS synonyms. Documented referenced base objects include GMS_AWARDS, GMS_INSTALLMENTS, GMS_SUMMARY_PROJECT_FUNDINGS, GMS_BUDGET_VERSIONS, PA_PROJECTS_ALL, PA_TASKS, and HR_ORGANIZATION_UNITS. The HR_GENERAL and HR_SECURITY packages, which implement organization-based security, are also referenced.

The join chain begins at GMS_AWARDS and proceeds through GMS_INSTALLMENTS to GMS_SUMMARY_PROJECT_FUNDINGS, linking awards to the projects and tasks funded by them. PA_PROJECTS_ALL supplies the project number (SEGMENT1), while PA_TASKS supplies task identifiers and the chargeable flag. HR_ORGANIZATION_UNITS provides the award organization name, resolving the AWARD_ORGANIZATION_ID. Project-to-task linkage is deliberately loose: the summary funding task is matched to a task when it equals TASK_ID, equals the project's TOP_TASK_ID, or is null, ensuring top-level tasks and project-level fundings are represented. An EXISTS subquery against GMS_BUDGET_VERSIONS restricts output to awards having a baselined budget version (BUDGET_STATUS_CODE = 'B') for the relevant project. The DISTINCT keyword eliminates duplication introduced by the multiple-task join path.

Key Columns

Common Use Cases and Queries

Typical uses include validating that a deferred-template award is visible in self-service after budget baselining, reconciling award-to-project mappings, and feeding grants dashboards. A basic query:

  • SELECT award_number, award_short_name, award_organization_name, project_number, task_number, start_date, end_date FROM apps.gms_ssa_awards_v WHERE org_id = :p_org_id ORDER BY award_number;
  • Filtering by project: SELECT award_number, project_number, task_number FROM apps.gms_ssa_awards_v WHERE project_number = :p_project_number;
  • Detecting awards nearing expiration: SELECT award_number, end_date FROM apps.gms_ssa_awards_v WHERE end_date BETWEEN SYSDATE AND SYSDATE + 90;

Because the view already applies status, template, budget, and chargeability filters, queries should not re-filter on those dimensions unless explicitly auditing excluded awards, in which case the base GMS_AWARDS and GMS_SUMMARY_PROJECT_FUNDINGS tables should be queried directly. Access is governed by APPS schema privileges and HR security packages.