Results for “lp_1”

8 results




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

Overview

APPS.GMS_REPORTS_V is a reporting view in the Oracle E-Business Suite Grants Management (GMS) module. It presents a denormalized, presentation-ready projection of the GMS_REPORTS entity, joining report records to their templates, lookup meanings, customer site uses, and the filing person's name. In Oracle EBS 12.1.1 and 12.2.2, the view is owned by APPS and exposed as a synonym to the GMS application schema. Its principal role is to supply reporting and integration layers with report-level attributes — report identifier, installment, template name, report type meaning, due and filed dates, and the person who filed — without requiring consumers to reconstruct the joins themselves. Because it resolves the lookup code and person name internally, it is well suited to concurrent program output, BI Publisher data sources, and OAF-based inquiry pages.

Underlying Base Objects

The view is defined over a mix of base tables, synonyms, views, and package-backed views, as documented in the ETRM metadata. The driving object is GMS_REPORTS (exposed as a synonym), aliased R. It is joined to GMS_REPORT_TEMPLATES (synonym, aliased RT) on REPORT_TEMPLATE_ID, providing the template name and template type. GMS_LOOKUPS (view, aliased LP_1) supplies the decoded report type, restricted to LOOKUP_TYPE = 'REPORT_TYPE'. HZ_CUST_SITE_USES (synonym, aliased SU) is outer-joined on SITE_USE_ID, linking the report to a customer site use. PER_PEOPLE_X (view, aliased PER) is outer-joined on FILED_BY = PERSON_ID, resolving the filer's full name. PER_PEOPLE_X itself is backed by the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, meaning the view indirectly enforces person-level security when queried interactively.

Key Columns

  • REPORT_ID — primary identifier of the report row in GMS_REPORTS.
  • INSTALLMENT_ID — the installment the report belongs to.
  • REPORT_TEMPLATE_ID — foreign key to the report template.
  • REPORT_NAME — descriptive name of the template from GMS_REPORT_TEMPLATES.
  • MEANING — decoded lookup meaning for the template's TYPE (for example, the report type description).
  • SITE_USE_ID — customer site use to which the report applies.
  • COPY_NUMBER — copy sequence for the report, where multiple copies exist.
  • DUE_DATE — the date the report is due.
  • DATE_FILED — the date the report was actually filed.
  • FILED_BY — person identifier of the filer.
  • FULL_NAME — resolved filer name from PER_PEOPLE_X.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • ROWID — the physical row identifier for the underlying GMS_REPORTS row.

Common Use Cases and Queries

A typical use is listing outstanding and filed reports for a given installment or template:

  • Reporting on compliance: select reports with DUE_DATE in a period and DATE_FILED null to identify delinquent filings.
  • Reconciliation: compare the report type MEANING against expected lookup values for reporting accuracy.
  • Audit: surface FILED_BY and FULL_NAME alongside DATE_FILED to trace who submitted each report.

Sample query:

SELECT report_id, installment_id, report_name, meaning, due_date, date_filed, full_name FROM apps.gms_reports_v WHERE date_filed IS NULL AND due_date < SYSDATE ORDER BY due_date;

Note that the joins to HZ_CUST_SITE_USES and PER_PEOPLE_X are outer joins, so reports without a linked site use or filer still appear; consumers should null-handle SITE_USE_ID and FULL_NAME accordingly. Because PER_PEOPLE_X is security-aware via HR_SECURITY, results may vary by the querying user's person security profile.