Results for “gms_fp_distributions_v”

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

Overview

GMS_FP_DISTRIBUTIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMS – Grants Accounting module. It is a denormalized join that combines funding pattern distribution records with their parent award header information, allowing consumers to read distribution-level data alongside the associated award identifiers and audit columns without performing the join themselves. The view is marked VALID in the ETRM metadata for release 12.1.1 and 12.2.2, confirming it is a supported and compiled database object at the documented release levels.

The view exists primarily to support inquiry screens, concurrent reports, and integration extracts within Grants Accounting. Because funding pattern distributions are stored at a lower grain than awards, tooling that needs both the distribution amount and the award number or award name in a single result set would otherwise have to join GMS_FP_DISTRIBUTIONS to GMS_AWARDS manually. This view encapsulates that relationship.

Underlying Base Objects

The view is defined over two documented base objects, both exposed in the APPS schema as synonyms:

• GMS_AWARDS — the award header table, supplying award number, award short name, organization, and standard WHO audit columns.
• GMS_FP_DISTRIBUTIONS — the funding pattern distribution table, supplying the funding pattern identifier, distribution number, and distribution value.

The join predicate is A.AWARD_ID = F.AWARD_ID, an inner join on the award identifier that links each funding pattern distribution row to exactly one award row. Because the view does not select from a third table and applies no filter predicates, the row count matches the qualifying rows in GMS_FP_DISTRIBUTIONS where a matching award exists. Columns sourced from GMS_AWARDS are inherited with the A. alias, and the view text selects the award table first in the FROM clause, although this ordering has no functional effect on results.

Key Columns

The view exposes twelve columns. The following are the most significant for reporting and integration purposes:

• FUNDING_PATTERN_ID — the parent funding pattern identifier; groups distributions belonging to the same pattern.
• DISTRIBUTION_NUMBER — sequence number of the distribution line within the funding pattern.
• AWARD_ID — the award foreign key, shared by both base tables and the join key of the view.
• DISTRIBUTION_VALUE — the distribution amount or value for the line. This is the column most often targeted by ad-hoc searches for distribution_value.
• AWARD_NUMBER — the award's business-facing identifier, drawn from GMS_AWARDS.
• AWARD_NAME — the award short name as stored in GMS_AWARDS; note the ETRM view text aliases AWARD_SHORT_NAME to the AWARD_NAME column position.
• ORG_ID — the operating unit discriminator, essential for multi-org security filtering in any query against this view.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN are inherited from GMS_AWARDS, representing the award header's audit state rather than that of the distribution row.

Common Use Cases and Queries

The view is typically used for award-level funding pattern analysis, reconciliation of distribution totals against award budgets, and extraction into external grants reporting systems. A representative query for locating a specific distribution value is:

• SELECT award_number, award_name, funding_pattern_id, distribution_number, distribution_value FROM gms_fp_distributions_v WHERE distribution_value > 0 AND org_id = :p_org_id ORDER BY award_number, funding_pattern_id, distribution_number;

To aggregate distribution totals per award, a grouped query such as SELECT award_number, SUM(distribution_value) FROM gms_fp_distributions_v WHERE org_id = :p_org_id GROUP BY award_number produces an award-level rollup directly from the view. Because the audit columns reflect the award rather than the distribution, consumers requiring distribution-level change tracking should query GMS_FP_DISTRIBUTIONS directly. All access should be granted through the APPS synonyms, and queries should filter on ORG_ID when operating in a multi-organization environment.