Results for “gms_awards_v”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMS_AWARDS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the Grants Accounting (GMS) product family. It presents a denormalized, query-ready projection of award records held in GMS_AWARDS, joined to customer, party, agreement, rate schedule, invoice format, operating unit, and funding summary data. Its principal purpose is to supply Grants Accounting forms, LOVs, and custom reports with award header information in a single consistent structure, avoiding the need for report authors to reconstruct the underlying join logic. The ETRM documentation notes that the view text was modified to comment out the allow_query filter in the WHERE clause as per Bug 1538406, meaning the current definition no longer applies the row-level allow-query restriction directly inside the view. Security enforcement is therefore expected from the calling form or from GMS_SECURITY, which is listed among the referenced objects. The view remains VALID in both 12.1.1 and 12.2.2 and is not a multi-org partitioned view in the classic sense, though it exposes AWARD_ORGANIZATION_ID and relies on GMS_OPERATING_UNITS_V and MO_GLOBAL for organization context.

Underlying Base Objects

The documented referenced objects span several modules. Award data originates from GMS_AWARDS (synonym), with allowability schedules from GMS_ALLOWABILITY_SCHEDULES and lookup meanings from GMS_LOOKUPS. Customer and party names are resolved through HZ_CUST_ACCOUNTS and HZ_PARTIES, while agreement numbers come from PA_AGREEMENTS_ALL. Project-related attributes derive from PA_IND_RATE_SCHEDULES, PA_INVOICE_FORMATS, PA_SUMMARY_PROJECT_FUNDINGS, and PA_UTILS. Payment terms are sourced from RA_TERMS. Organization names are obtained from HR_ALL_ORGANIZATION_UNITS or GMS_OPERATING_UNITS_V, with MO_GLOBAL supplying operating unit context. The view also references FND_PROFILE and GMS_SECURITY packages, indicating that profile-option and security logic is embedded in the definition. Attribute columns are passed through directly from GMS_AWARDS, and DUAL supports any constant expressions.

Key Columns

Common Use Cases and Queries

Typical usage includes award LOVs, award dashboards, and custom grant reports requiring customer, schedule, and billing metadata in one row. A representative query joining the view to a project or customer follows:

  • SELECT award_id, award_number, award_short_name, customer_name, status FROM apps.gms_awards_v WHERE status = 'A';
  • SELECT aw.award_number, aw.customer_name, aw.billing_frequency, aw.ind_rate_sch_name FROM apps.gms_awards_v aw WHERE aw.award_organization_id = :org_id;
  • SELECT aw.award_number, aw.total_billed_amount, aw.total_accrued_amount FROM apps.gms_awards_v aw WHERE aw.customer_id = :cust_id;

Because the allow_query predicate was commented out, custom code that previously relied on the view to enforce security must apply organization or role restrictions explicitly, typically by filtering on AWARD_ORGANIZATION_ID or by invoking GMS_SECURITY directly. The user search term pa_organizations_lov_v relates to the PA organization LOV rather than this view; for organization names within GMS_AWARDS_V, the applicable source is HR_ALL_ORGANIZATION_UNITS or GMS_OPERATING_UNITS_V.