Results for “installment_num”

36 results




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

Overview

GMS_SUM_PRJ_FUNDINGS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the GMS (Grants Accounting) product family. It exposes summarized funding, revenue, and billing balances at the project, task, and installment level, enriched with award and agreement context. The view consolidates transactional funding data held in GMS_SUMMARY_PROJECT_FUNDINGS with descriptive and organizational attributes drawn from awards, installments, projects, and tasks.

The view is notable for its handling of row-level security. Per the documented implementation note, the original GMS_SECURITY.ALLOW_QUERY(AWD.AWARD_ID) = 'Y' predicate in the WHERE clause was commented out as a result of Bug 1538406, replaced by the always-true construct 'Y' IN (SELECT GMS_SECURITY.ALLOW_QUERY(AWD.AWARD_ID) FROM SYS.DUAL). Column-level security is instead applied through PA_SECURITY.ALLOW_QUERY(P.PROJECT_ID), which drives DECODE logic returning either real project, task, and lookup values or the secured-data lookup meaning where access is not granted. This makes the view suitable for reporting and integration contexts where masked display of unauthorized records is preferable to outright row exclusion.

Underlying Base Objects

The view is defined over the following documented base objects:

Key Columns

  • ROW_ID — the row identifier from GMS_SUMMARY_PROJECT_FUNDINGS, useful for direct updates or drill-through.
  • PROJECT_ID / PROJECT_NUMBER / PROJECT_NAME — project identity; number and name are subject to PA_SECURITY masking.
  • TASK_ID / TASK_NUMBER / TASK_NAME — optional task context, likewise security-masked.
  • INSTALLMENT_ID / INSTALLMENT_NUM — the award installment associated with the funding record.
  • TOTAL_FUNDING_AMOUNT / TOTAL_REVENUE_AMOUNT / TOTAL_BILLED_AMOUNT — the core funding, revenue, and billing measures at the summarized grain.
  • AGREEMENT_ID / AWARD_ID / AWARD_NUMBER / AWARD_SHORT_NAME — award and agreement identification for reporting rollups.
  • ORG_ID — the operating unit column, supporting multi-org reporting filters.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include award funding status reporting, project-level revenue and billing reconciliation, and integration extracts feeding downstream analytics. Because ORG_ID and award identifiers are exposed, the view supports both operating-unit-scoped and cross-org reporting.

Sample query listing funding balances for a given project:

  • SELECT project_number, project_name, award_number, installment_num, total_funding_amount, total_billed_amount FROM apps.gms_sum_prj_fundings_v WHERE project_id = :p_project_id;

Sample aggregation by award for an operating unit:

  • SELECT award_id, award_number, SUM(total_funding_amount) funded, SUM(total_revenue_amount) revenue FROM apps.gms_sum_prj_fundings_v WHERE org_id = :p_org_id GROUP BY award_id, award_number;

Because security masking returns lookup meanings rather than true values when access is denied, consumers should treat project and task display columns as potentially non-identifying and apply their own authorization checks where full visibility is required.