Results for “award_id”

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

Overview

The GMS_FUNDING_AWARDS_V view is a public Oracle E-Business Suite database object owned by the APPS schema and shipped with the GMS (Grants Accounting) product family. In Oracle EBS 12.1.1 and 12.2.2, it exposes the relationship between awards and the projects funded by those awards, presenting a denormalized, reporting-friendly endpoint over the Grants Accounting funding model. Its documented description is succinct: "Projects that are funded by a particular award."

The view plays a bridging role in Grants Accounting reporting. Awards master data resides in GMS_AWARDS, while project masters live in PA_PROJECTS_ALL. The association between the two is captured through the installment and summary funding tables. GMS_FUNDING_AWARDS_V collapses that multi-table join into a single queryable object, allowing report writers, discoverer workbooks, and integration programs to obtain the award-to-project funding map without reconstructing the join manually. This is particularly useful for grants administrators reconciling award-funded project portfolios, and for custom OAF or concurrent program views that must display funded projects alongside award identifiers.

Underlying Base Objects

The view is defined over four referenced base objects, all exposed as APPS synonyms:

• GMS_AWARDS — the award master table in Grants Accounting (aliased GA).
• GMS_SUMMARY_PROJECT_FUNDINGS — summary funding records linking projects to installments (aliased GF).
• GMS_INSTALLMENTS — award installment records, the pivot between awards and funding summaries (aliased GI).
• PA_PROJECTS_ALL — the Projects master table, providing the actual project identity (aliased PP).

The internal join path is: GF.PROJECT_ID = PP.PROJECT_ID, GF.INSTALLMENT_ID = GI.INSTALLMENT_ID, and GI.AWARD_ID = GA.AWARD_ID. Rows are aggregated with a GROUP BY over GA.AWARD_ID, GA.AWARD_SHORT_NAME, PP.PROJECT_ID, and GA.ORG_ID, which eliminates duplicates introduced by multiple funding summary rows referencing the same award-project pair. Because it is a simple view without an INSTEAD OF trigger, it is read-only.

Key Columns

• AWARD_ID — the primary key of the award in GMS_AWARDS; the foreign key used for joins to other Grants Accounting tables.
• AWARD_NAME — the award short name, sourced as GA.AWARD_SHORT_NAME. This is the column surfaced to users searching for an award_name; it is the human-readable award identifier.
• ACTUAL_PROJECT_ID — the project ID from PA_PROJECTS_ALL, aliased here because the view's purpose is to return the funded project rather than the award itself.
• ORG_ID — the operating unit (business group) identifier from the award, enabling multi-org filtered queries.

Note that the view exposes the project ID rather than the project number or name; callers must join to PA_PROJECTS_ALL to resolve descriptive project attributes.

Common Use Cases and Queries

Typical scenarios include listing all projects funded by a given award, enumerating awards that fund a given project, and seeding LOVs or cross-reference extracts. Because the view does not include ORG_ID in a policy-mandated form, queries should filter explicitly on ORG_ID.

Find every project funded by a named award:

• SELECT award_id, award_name, actual_project_id
• FROM apps.gms_funding_awards_v
• WHERE award_name = :award_name AND org_id = :org_id;

Resolve the funding awards for a specific project:

• SELECT award_id, award_name
• FROM apps.gms_funding_awards_v
• WHERE actual_project_id = :project_id AND org_id = :org_id;

Join to project master for descriptive reporting:

• SELECT f.award_name, p.segment1 project_number, p.name project_name
• FROM apps.gms_funding_awards_v f, apps.pa_projects_all p
• WHERE f.actual_project_id = p.project_id AND f.org_id = :org_id;

Since AWARD_NAME is derived from AWARD_SHORT_NAME, queries should not expect the long award description; join back to GMS_AWARDS if additional descriptive fields are required.