Results for “gms_summary_project_fundings”

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

Overview

GMS_SUMMARY_PROJECT_FUNDINGS is a table in the GMS (Grants Accounting) schema of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It stores summarized funding amounts that have been allocated from an award installment down to specific projects and tasks. In the grants lifecycle, an award installment represents a scheduled tranche of sponsor funding recorded in Oracle Grants/Federal Installments (IGS). When that installment is distributed across the projects and tasks that draw upon it, GMS_SUMMARY_PROJECT_FUNDINGS captures the resulting project-level and task-level funding totals, along with related billed and revenue amounts. The table therefore acts as a consolidated rollup sitting between award-level installment records and project-level expenditure and billing activity, allowing reporting without repeatedly aggregating transaction detail.

Under the heuristic Data Vault classification supplied in the metadata, this object is assessed as standalone. That is a modeling suggestion rather than a physical constraint: the table records funding allocation facts (amounts) keyed by project, task, and installment, so in a Data Vault design it would most naturally be treated as a satellite or fact-style entity rather than a hub. Its single documented foreign key to IGS_FI_PP_INSTLMNTS confirms its role as a dependent, transaction-oriented structure.

Key Information Stored

The table is documented with twelve columns. The most significant are:

• INSTALLMENT_ID — identifier of the award installment from which funding is allocated; foreign key to IGS_FI_PP_INSTLMNTS.
• PROJECT_ID — the project receiving the allocated funding.
• TASK_ID — the task within the project to which funding is distributed.
• TOTAL_FUNDING_AMOUNT — total funding allocated to the project/task from the installment.
• TOTAL_BILLED_AMOUNT — cumulative amount billed against that funding allocation.
• TOTAL_REVENUE_AMOUNT — cumulative revenue amount associated with the allocation.

The three identifier columns (PROJECT_ID, TASK_ID, INSTALLMENT_ID) form the unique business key, enforced by index GMS_SUMMARY_PROJECT_FUNDING_U1. The remaining columns are standard EBS audit and concurrency attributes: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and REQUEST_ID, the last recording the concurrent request that created or last populated the row. The metadata does not document a separate surrogate primary key column; the unique index on the three business columns serves as the key candidate.

Common Use Cases and Queries

Typical uses include reconciling installment-funded amounts against project billing, producing award-to-project funding rollups, and feeding grants reporting on sponsored project revenue. A representative query joins the table to its parent installment table:

• Funding by project and task: SELECT project_id, task_id, SUM(total_funding_amount) FROM gms.gms_summary_project_fundings GROUP BY project_id, task_id;
• Funding versus billing variance: SELECT project_id, task_id, total_funding_amount - total_billed_amount FROM gms.gms_summary_project_fundings WHERE total_billed_amount > total_funding_amount;
• Installment reconciliation: SELECT i.installment_id, s.project_id, s.total_funding_amount FROM igs_fi_pp_instlmnts i, gms_summary_project_fundings s WHERE i.installment_id = s.installment_id;

These patterns support grant administrator dashboards, sponsor reporting, and audit of award fund distribution.

Related Objects

The primary documented relationship is the foreign key from INSTALLMENT_ID to IGS_FI_PP_INSTLMNTS, the installment master in Oracle Grants/Federal Installments. Functionally, the table is closely associated with project and task definitions in PA_PROJECTS and PA_TASKS, with award definitions in GMS_AWARDS and their funding structures, and with billing and revenue detail in the GMS and PA revenue tables. As a summary store, it is typically populated by Grants funding processes rather than entered manually, and it should be treated as dependent on the installment and project master data for referential and business integrity.