Search Results gms_event_intersect




Overview
Explore in AI Chat

Overview

The GMS_EVENT_INTERSECT table is a core data object within the Oracle E-Business Suite (EBS) Grants Accounting (GMS) module, specifically for versions 12.1.1 and 12.2.2. Its primary function is to establish and maintain the relationship between expenditure items and project events. In the context of grant and award management, this table serves as a critical junction that enables the system to track which specific costs (expenditure items) are associated with which predefined project milestones or activities (events). This linkage is fundamental for compliance reporting, cost allocation, and ensuring that expenditures are properly charged against the correct award tasks and events as required by funding agency regulations.

Key Information Stored

The table's structure is designed to store foreign key references that define the many-to-many or one-to-many relationships between expenditures and events. While the full column list is not detailed in the provided metadata, the documented foreign keys explicitly identify the core columns. The AWARD_PROJECT_ID and EVENT_NUM columns together form a composite foreign key reference to the PA_EVENTS table, identifying the specific project event. The EXPENDITURE_ITEM_ID column is a foreign key reference to the PA_EXPENDITURE_ITEMS_ALL table, identifying the individual cost line item. Collectively, these columns form the essential data: a unique mapping record that certifies an expenditure item is applicable to a particular event for a given award project.

Common Use Cases and Queries

A primary use case is generating audit trails and reports for project managers and grant administrators to demonstrate how funds have been spent relative to planned events. For instance, a query might join GMS_EVENT_INTERSECT to expenditure and event details to list all costs tied to a specific event for a financial report to a sponsor. Another common scenario is during the expenditure item validation process, where the system checks for the existence of a valid event relationship before allowing costs to be posted to an award. A sample SQL pattern to retrieve this linked data would be:

  • SELECT gei.expenditure_item_id, gei.award_project_id, gei.event_num, pei.expenditure_type, pe.event_name FROM gms_event_intersect gei JOIN pa_expenditure_items_all pei ON gei.expenditure_item_id = pei.expenditure_item_id JOIN pa_events pe ON gei.award_project_id = pe.award_project_id AND gei.event_num = pe.event_num WHERE pei.project_id = :p_project_id;

Related Objects

The GMS_EVENT_INTERSECT table sits at the intersection of two major EBS functional areas: Projects and Grants Accounting. Its documented relationships are exclusively through foreign keys, as per the provided metadata:

  • PA_EVENTS: This table is referenced via the composite foreign key using columns GMS_EVENT_INTERSECT.AWARD_PROJECT_ID and GMS_EVENT_INTERSECT.EVENT_NUM. PA_EVENTS stores the definition of project events or milestones.
  • PA_EXPENDITURE_ITEMS_ALL: This table is referenced via the foreign key column GMS_EVENT_INTERSECT.EXPENDITURE_ITEM_ID. PA_EXPENDITURE_ITEMS_ALL holds the detailed transactional records of project costs.

These relationships confirm the table's role as a pure intersection entity, deriving its meaning entirely from its connections to these two parent tables. Processes and reports within the GMS module will heavily rely on joins through these keys to present a unified view of event-driven expenditures.