Search Results gms_events_v




Overview
Explore in AI Chat

Overview

GMS_EVENTS_V is an APPS-owned database view within the Oracle E-Business Suite Grants Accounting (GMS) module. It is a status VALID object in both EBS 12.1.1 and 12.2.2 environments. The view consolidates grant event data drawn from the core Oracle Projects event model and the GMS-specific event attribute extension, presenting a single denormalized record per grant event. Its principal role is reporting and integration: it exposes event, billing, revenue distribution, and award-related attributes so that reporting tools, concurrent programs, and downstream interfaces can retrieve grants event information without navigating multiple base tables. Because the view joins Projects event records to GMS attribute records, it is the logical access point when grant event context must be enriched with grant-specific attributes such as installment, expenditure organization, and event calling process. The column PE.CALLING_PROCESS is directly exposed by this view, which is why it surfaces for searches relating to calling_process — it records the business process or program context that created the event, while its companion column GEA.EVENT_CALLING_PROCESS (aliased from the GMS attribute table) carries the equivalent calling-process value on the grants side of the join.

Underlying Base Objects

The documented base objects referenced by GMS_EVENTS_V are two synonyms: PA_EVENTS and GMS_EVENT_ATTRIBUTE. The join condition links them as PE.PROJECT_ID = GEA.PROJECT_ID AND PE.EVENT_NUM = GEA.EVENT_NUM, meaning each event in PA_EVENTS is matched to its corresponding grant attribute row by project and event number. PA_EVENTS provides the standard Projects event attributes — event type, description, amounts, distribution flags, rejection codes, request/program audit columns, descriptive flexfield attributes, and event identifiers. GMS_EVENT_ATTRIBUTE supplies the Grants Accounting extension fields, including installment identifier, actual project and task identifiers, burden cost code, expenditure organization, write-off amount, revenue accumulated, resource list member, expenditure type, and the grants-side event calling process. This join structure means the view returns only those events for which a matching GMS attribute record exists, effectively scoping the result set to grant-related events.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling billed versus distributed revenue on grant events, auditing events created by specific calling processes, and identifying held or rejected events. A representative query selecting calling-process and distribution diagnostics follows:

  • SELECT event_num, project_id, event_type, calling_place, calling_process, event_calling_process, revenue_distributed_flag, rev_dist_rejection_code FROM gms_events_v WHERE project_id = :p_project_id;
  • SELECT event_id, installment_id, expenditure_org_id, revenue_amount, write_off_amount FROM gms_events_v WHERE revenue_distributed_flag = 'N';
  • SELECT event_num, calling_process, request_id, program_update_date FROM gms_events_v WHERE calling_process IS NOT NULL ORDER BY creation_date DESC;

Because the view is a join of two synonyms and performs no aggregation, it is suitable for direct SELECT statements in reports, custom concurrent programs, and integration extracts. Query performance is generally governed by indexes on PA_EVENTS.PROJECT_ID and EVENT_NUM and the matching GMS_EVENT_ATTRIBUTE columns, so filtering by PROJECT_ID or EVENT_NUM is recommended.