Search Results gms_reports




Overview
Explore in AI Chat

Overview

GMS_REPORTS is a transactional table in the GMS (Grants Accounting) schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its documented purpose is to store reports of installment, meaning the filings, submissions, or deliverable reports tied to sponsored-project installment records managed within Grants Accounting. In practice, this table captures the reporting obligations that accompany drawdowns or invoicing activity on a grant award — the periodic submission of financial or technical reports that funders (sponsors) require as a condition of releasing installment payments.

Because the table is keyed to installment records, it functions as the operational log linking an installment schedule to the report artifacts generated against it. Heuristic data-vault classification derived from the foreign-key structure indicates this object is standalone — it references a parent (IGS_FI_PP_INSTLMNTS) but is not itself the target of inbound foreign keys. In a Data Vault model this would most naturally become a satellite hanging off a hub or link representing the installment, with the report attributes described below.

Key Information Stored

The table contains 29 documented columns, with GMS_REPORTS_U1 on REPORT_ID serving as the unique business key.

  • REPORT_ID — surrogate primary key and the column enforced by the unique index GMS_REPORTS_U1. Uniquely identifies each report record.
  • INSTALLMENT_ID — foreign key to IGS_FI_PP_INSTLMNTS. Associates the report with a specific installment line on the award.
  • REPORT_TEMPLATE_ID — identifies the report template or format used, allowing different report types to be standardized.
  • SITE_USE_ID — links the report to the specific party site/address used for submission.
  • COPY_NUMBER — distinguishes multiple copies or versions of the same report.
  • FILED_BY — records the individual or entity that submitted the report.
  • DUE_DATE — the contractual or sponsor-defined deadline for filing.
  • DATE_FILED — the actual filing date, enabling on-time versus late analysis.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive-flexfield block, used for client-specific reporting metadata.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns for change tracking and concurrency control.

Common Use Cases and Queries

The principal use is monitoring report filing obligations and compliance. A typical pattern joins GMS_REPORTS to its parent installment:

  • Listing overdue filings: SELECT r.report_id, r.due_date, r.date_filed FROM gms_reports r WHERE r.date_filed IS NULL AND r.due_date < SYSDATE;
  • Reporting by template: SELECT report_template_id, COUNT(*) FROM gms_reports GROUP BY report_template_id;
  • Joining to installments: SELECT i.installment_id, r.report_id, r.date_filed FROM igs_fi_pp_instlmnts i JOIN gms_reports r ON r.installment_id = i.installment_id;
  • Extracting flexfield detail: filtering on attribute_category and the ATTRIBUTE1–15 columns for institution-specific data.

These queries support deliverable tracking, sponsor reporting dashboards, and audit evidence for grants compliance.

Related Objects

  • IGS_FI_PP_INSTLMNTS — the parent installment table, joined via INSTALLMENT_ID. This is the only documented foreign key.
  • GMS_REPORT_TEMPLATES (functional reference) — supplies REPORT_TEMPLATE_ID definitions.
  • HZ_CUST_SITE_USES_ALL — resolves SITE_USE_ID to customer site information.
  • GMS_AWARDS / GMS_AWARD_INSTALLMENTS — award-level context behind installments.
  • FND_USER — resolves CREATED_BY, LAST_UPDATED_BY, and FILED_BY to user identities.

Consult the GMS schema documentation for reporting APIs that create or update these records during installment processing.