Search Results gms_default_reports_pk

Overview

GMS_DEFAULT_REPORTS is a Grants Accounting (GMS) transactional table that stores the default report definitions associated with awards. Each row represents a scheduled or pre-configured report that the system generates automatically for a specific award, tied to a report template and an optional site use. In Oracle EBS 12.1.1 and 12.2.2, the table acts as the configuration backbone behind the Grants Accounting reporting framework, allowing grant administrators to define which deliverables, billing statements, or sponsor-facing documents should be produced, how frequently, and within what lead time.

Under a heuristic Data Vault classification derived from its foreign-key structure, GMS_DEFAULT_REPORTS is modeled as a standalone entity. It references an award but is not itself referenced by other tables within the mined relationship graph. Consequently, it behaves most like a standalone table rather than a hub, link, or satellite in a strict Data Vault sense; it can be treated as a source for a hub-and-satellite pattern if a warehouse model is layered over it.

Key Information Stored

The table contains 32 documented columns. The most operationally significant include:

• DEFAULT_REPORT_ID — the surrogate primary key (GMS_DEFAULT_REPORTS_PK) that uniquely identifies each default report row.
• AWARD_ID — foreign key to IGF_AW_AWARD_ALL, identifying the award to which the default report belongs.
• REPORT_TEMPLATE_ID — identifies the report template that governs the output format and content.
• SITE_USE_ID — the site use context under which the report applies, supporting multi-site awards.
• FREQUENCY — the recurrence interval governing how often the report is generated.
• DUE_WITHIN_DAYS — the lead-time window, in days, within which the report becomes due.
• COPY_NUMBER — copy or version counter for the default report definition.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program request metadata, linking the definition to its generating concurrent request.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield (DFF) columns used for extension.

Two unique indexes define business-key candidates. GMS_DEFAULT_REPORTS_U1 is a single-column unique index on DEFAULT_REPORT_ID, which mirrors the primary key. GMS_DEFAULT_REPORTS_U2 is a composite unique index on (AWARD_ID, REPORT_TEMPLATE_ID, SITE_USE_ID), enforcing that a given report template may appear only once per award and site use combination.

Common Use Cases and Queries

The table is queried most often to enumerate every default report configured for an award, to audit which templates have been deployed across a portfolio, and to build reports on upcoming deliverable obligations. A representative query joins the table to IGF_AW_AWARD_ALL to expose the award number alongside its configured reports:

• SELECT d.default_report_id, a.award_number, d.report_template_id, d.frequency, d.due_within_days FROM gms_default_reports d, igf_aw_award_all a WHERE d.award_id = a.award_id;
• Filter by site use to see configuration differences across award sites: ... WHERE d.site_use_id = :site_use_id;
• Identify awards with no default reports through an outer join: SELECT a.award_number FROM igf_aw_award_all a, gms_default_reports d WHERE a.award_id = d.award_id(+) AND d.default_report_id IS NULL;
• Trace concurrent generation activity via REQUEST_ID joined to FND_CONCURRENT_REQUESTS.

Typical reporting scenarios include compliance dashboards, sponsor deliverable calendars, and data-migration validation during implementations, where U2 is used to detect duplicate configurations.

Related Objects

The most significant related objects are:

• IGF_AW_AWARD_ALL — referenced by AWARD_ID; the primary parent entity for awards.
• GMS_DEFAULT_REPORTS_PK / GMS_DEFAULT_REPORTS_U1 / GMS_DEFAULT_REPORTS_U2 — the primary and unique indexes enforcing identity and business keys.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to trace report generation.
• FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE — supporting tables for the ATTRIBUTE_CATEGORY DFF columns.
• GMS_REPORT_TEMPLATES (related template definition) — resolved through REPORT_TEMPLATE_ID.
• FND_SITE_USES — supports SITE_USE_ID resolution in multi-site configurations.