Results for “lp_2”

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

Overview

APPS.GMS_DEFAULT_REPORTS_V is a supplementary view in the Oracle E-Business Suite Grants Management (GMS) module, owned by the APPS schema and registered in FND Design Data as GMS.GMS_DEFAULT_REPORTS_V. Its documented status is VALID, and it is classified as a supplementary view used to simplify forms coding. Oracle explicitly warns that this view is not intended for direct data queries or alterations, since its definition may change substantially across minor or major releases. In practice, the view functions as a presentation layer that resolves internal identifiers into descriptive, user-facing values for the Grants Management reporting setup and notification functionality. The column TYPE_DIS, which appears in the user search query, is a descriptive (decoded) field exposed by the view rather than a raw stored identifier, reflecting this decoding purpose.

Underlying Base Objects

The view is defined over four documented base objects: GMS_DEFAULT_REPORTS (synonym), GMS_LOOKUPS (view), GMS_REPORT_TEMPLATES (synonym), and HZ_CUST_SITE_USES (synonym). GMS_DEFAULT_REPORTS supplies the transactional core of the view, providing the default report assignment records such as identifiers, frequency codes, due-within-days values, and audit columns. GMS_REPORT_TEMPLATES is joined to resolve report template information associated with each default report row. GMS_LOOKUPS is used to decode internal lookup codes into descriptive text, which is how the TYPE_DIS and FREQUENCY_DIS columns are derived. HZ_CUST_SITE_USES links the report assignment to a customer site use, providing the SITE_USE_ID context. On the dependency side, the view is referenced by APPS.GMS_NOTIFICATION_PKG, indicating its role in the notification processing path for scheduled grant reports.

Key Columns

The view exposes fifteen columns plus ROW_ID. DEFAULT_REPORT_ID, AWARD_ID, REPORT_TEMPLATE_ID, SITE_USE_ID, and COPY_NUMBER are numeric identifiers linking the record to its award, report template, customer site use, and duplication sequence. REPORT_NAME is a VARCHAR2(60) descriptive name of the report. TYPE_DIS (VARCHAR2(80)) presents the decoded report type, and FREQUENCY_DIS (VARCHAR2(80)) presents the decoded reporting frequency, both resolved through GMS_LOOKUPS. FREQUENCY (VARCHAR2(30)) retains the internal frequency code, while DUE_WITHIN_DAYS (NUMBER) expresses the lead time in days before a report is due. Standard audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — support change tracking and concurrency. ROW_ID is the ROWID pseudocolumn for the underlying row.

Common Use Cases and Queries

Typical usage centers on grants reporting setup, notification generation, and reporting on default report assignments per award. A basic listing retrieves the decoded report type and frequency for configuration review or validation:

• SELECT default_report_id, award_id, report_name, type_dis, frequency_dis, frequency, due_within_days FROM apps.gms_default_reports_v;
• Filtering by decoded type, for example: ... WHERE type_dis = 'Financial' ORDER BY report_name;
• Joining to award or site use data through AWARD_ID or SITE_USE_ID to reconcile report obligations against specific awards or customer sites.
• Querying DUE_WITHIN_DAYS to identify reports approaching their due threshold for notification planning.

Because GMS_NOTIFICATION_PKG depends on this view, its output also informs scheduled notification logic. Oracle's warning notwithstanding, the view remains useful for read-only diagnostics and integration checks, with the caveat that custom code should not treat its column list as stable across releases.