Results for “gms_default_reports_v”

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

Overview

GMS_DEFAULT_REPORTS_V is an APPS-owned database view within the Oracle E-Business Suite Grants Accounting (GMS) module. Its ETRM record classifies the object as VALID and notes that it was retrofitted during the upgrade cycle that produced release 12.1.1 / 12.2.2, which explains the terse "Retrofitted" annotation carried in the source documentation. The view presents the setup of default award reports — the report templates assigned to a grant award, the delivery frequency, the due window, the intended recipient site use, and the copy count — in a denormalized, user-readable form. In that role it functions as a reporting and integration layer over the transactional configuration tables, sparing report writers and interface developers from manually joining lookup tables and customer site-use records whenever they need to describe how an award's deliverables are scheduled.

Underlying Base Objects

The view text joins four documented objects. GMS_DEFAULT_REPORTS (a synonym in the documented metadata) supplies the driving rows: one per default report assignment, keyed by DEFAULT_REPORT_ID and linked to AWARD_ID. GMS_REPORT_TEMPLATES is joined on REPORT_TEMPLATE_ID to retrieve REPORT_NAME and, indirectly, the report type. HZ_CUST_SITE_USES is outer-joined on SITE_USE_ID, so rows without a valid recipient site are retained; this tolerates incomplete or historical site configurations. GMS_LOOKUPS is referenced twice, aliased LP_1 and LP_2, against LOOKUP_TYPE values of 'REPORT_FREQUENCY' and 'REPORT_TYPE' respectively, translating the FREQUENCY code and the template TYPE code into their display meanings. Because GMS_LOOKUPS is itself a view in the documented hierarchy, the join chain reaches the lookup foundation tables indirectly. The outer join on the site-use object is the only non-equality join; all other predicates are simple code translations.

Key Columns

• DEFAULT_REPORT_ID — primary key of the underlying default-report assignment row.
• AWARD_ID — the grant award to which the report obligation belongs.
• REPORT_TEMPLATE_ID / REPORT_NAME — identifier and descriptive name of the report template.
• TYPE_DIS — decoded report type, derived from the GMS_LOOKUPS entry for 'REPORT_TYPE'.
• FREQUENCY / FREQUENCY_DIS — the stored frequency code and its decoded meaning from the 'REPORT_FREQUENCY' lookup set.
• DUE_WITHIN_DAYS — the number of days before the due date, or after period end, that the report must be submitted.
• SITE_USE_ID / COPY_NUMBER — the recipient customer site use and the number of copies required.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, ROWID — standard audit and concurrency columns.

Common Use Cases and Queries

Typical uses include award compliance reporting, reconciliation of scheduled deliverables, and data extraction for external reporting systems. The view is frequently the source for a "report schedule by award" listing.

• Listing all scheduled reports for a specific award: SELECT report_name, type_dis, frequency_dis, due_within_days FROM gms_default_reports_v WHERE award_id = :award_id;
• Auditing decoded frequency distribution: SELECT frequency_dis, COUNT(*) FROM gms_default_reports_v GROUP BY frequency_dis;
• Extracting an incremental feed using audit columns: SELECT * FROM gms_default_reports_v WHERE last_update_date >= :last_run_date;
• Identifying rows missing a valid recipient site: SELECT default_report_id, award_id FROM gms_default_reports_v WHERE site_use_id IS NULL;

Because the view is read-only and exposes no row-level security of its own, access is governed by grants on the view itself and by the security applied to the Grants Accounting responsibility from which it is queried.