Search Results gms_reports_u2

Overview

GMS.GMS_REPORTS is a transactional table in the Grants Management (GMS) schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores installment-level report definitions and filings associated with sponsored award installments. Each row represents a single report instance that must be delivered, tracked, and filed against an installment of an award payment schedule. Reports captured in this table may be classified as monthly, quarterly, annual, end-of-installment, or end-of-award, reflecting the reporting obligations commonly attached to sponsored research agreements, federal grants, and similar funding instruments.

The table is registered in FND Design Data as GMS.GMS_REPORTS and is owned by the GMS schema, placing it in the grants management product family alongside award, installment, and reporting-template objects. It holds valid status in the ETRM reference. From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone, meaning it does not exhibit a strong hub-and-satellite pattern driven by foreign-key structure. In practice it behaves as a transaction or link entity that associates a report definition with a specific installment, with descriptive attributes carried directly on the same row.

Key Information Stored

The table contains 29 documented columns. The most operationally significant are:

• REPORT_ID (NUMBER(15), mandatory): the surrogate primary key and the column behind the unique index GMS_REPORTS_U1. This is the value most commonly supplied when the object is referenced as gms_reports_u1, since the unique index on REPORT_ID enforces one row per report instance and is the natural lookup path for direct fetches by identifier.
• INSTALLMENT_ID (NUMBER(15)): the foreign key to IGS_FI_PP_INSTLMNTS, linking the report to the installment it belongs to. Together with REPORT_TEMPLATE_ID and REPORT_ID, it forms the composite non-unique index GMS_REPORTS_U2.
• REPORT_TEMPLATE_ID (NUMBER(15)): identifies the report template governing the expected content, frequency, and layout of the filing.
• SITE_USE_ID (NUMBER(15)): the site or address usage code indicating where the report must be delivered.
• COPY_NUMBER (NUMBER(15)): the number of report copies to be distributed.
• FILED_BY (NUMBER(15)): the identifier of the person or party responsible for filing.
• DUE_DATE and DATE_FILED (DATE): the scheduled due date and the actual filing date, which together drive compliance and delinquency reporting.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN): audit lineage maintained automatically by EBS.
• ATTRIBUTE_CATEGORY (VARCHAR2(30)) and ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2(150) each): the descriptive flexfield structure and segment columns used for client-specific extensions.

The distinction between the surrogate key and business keys is important: REPORT_ID is the enforced unique identifier, while the combination of INSTALLMENT_ID, REPORT_TEMPLATE_ID, and REPORT_ID is indexed non-uniquely to support installment-centric access paths.

Common Use Cases and Queries

The primary use cases are compliance tracking, filing status reporting, and installment-level reporting schedules. A typical lookup by primary key uses the unique index:

• SELECT * FROM gms.gms_reports WHERE report_id = :p_report_id;
• SELECT report_id, installment_id, due_date, date_filed FROM gms.gms_reports WHERE installment_id = :p_installment_id ORDER BY due_date;
• Outstanding report identification: SELECT report_id, due_date FROM gms.gms_reports WHERE date_filed IS NULL AND due_date < SYSDATE;
• Filings by period: filter on DATE_FILED between the period start and end to produce submission summaries.
• Template distribution: group by REPORT_TEMPLATE_ID to count outstanding or completed obligations per template.

Reporting scenarios include producing delinquency lists for grants administrators, reconciling scheduled versus actual filing dates for audit, and generating deliverable calendars by site. Extracts frequently join to installment and award tables to enrich reports with award numbers and sponsor details.

Related Objects

• IGS_FI_PP_INSTLMNTS: referenced by GMS_REPORTS.INSTALLMENT_ID, providing the parent installment record and, through it, the award payment schedule.
• GMS_REPORT_TEMPLATES: the logical parent of REPORT_TEMPLATE_ID, defining report type, frequency, and required content.
• GMS_AWARDS: reached transitively through the installment, supplying sponsor and award context.
• FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE: support the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 descriptive flexfield values.
• HR_ALL_ORGANIZATION_UNITS / HZ_CUST_SITE_USES_ALL: resolve SITE_USE_ID into a deliverable location.
• FND_USER: resolves CREATED_BY, LAST_UPDATED_BY, and FILED_BY into user identities.

Together these relationships position GMS_REPORTS as the operational record of report obligations at the installment level within Oracle Grants Management.