Results for “event_type”

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

Overview

GMS_NOTIFICATIONS is a Grants Accounting (GMS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that maintains a record of notifications sent to users about award events. Within the broader grants lifecycle — award creation, budget entry, expenditure tracking, and closeout — this table functions as an audit-of-communication store. Each row captures the pairing of a specific award, the type of award event that triggered the alert, and the recipient user. This structure allows organizations to verify that stakeholders (principal investigators, grants administrators, finance staff) were notified when significant award activity occurred.

From a dimensional modeling perspective, the ETRM metadata heuristically classifies GMS_NOTIFICATIONS as satellite-leaning. Its three-column layout — AWARD_ID, EVENT_TYPE, and USER_ID — behaves less like an independent transactional hub and more like a descriptive record hanging off the award entity and the recipient entity. Analysts building a Data Vault or star-schema layer should consider treating it as a satellite or bridge attached to the award hub (IGF_AW_AWARD_ALL) and the user dimension (FND_USER), rather than as a standalone fact. This is a modeling suggestion derived from the foreign-key structure, not a mandated EBS construct.

Key Information Stored

The table is compact, with only three documented columns in the 12.2.2 physical schema, all of which are significant:

• AWARD_ID — The award with which the notification is associated. This is a foreign key into IGF_AW_AWARD_ALL (the award header entity) and is the primary filter used in most reporting and reconciliation queries.
• EVENT_TYPE — The category of award event that generated the notification. Together with AWARD_ID and USER_ID, this column participates in the unique business key that prevents redundant notification records.
• USER_ID — The recipient of the notification, defined as a foreign key to FND_USER. This links the notification record directly to the EBS application user account.

The business-key candidate for this table is the composite unique index GMS_NOTIFICATIONS_U1 on (AWARD_ID, EVENT_TYPE, USER_ID). No single-column surrogate primary key is documented in the supplied metadata. The composite unique constraint effectively guarantees that any given user receives at most one notification per event type per award, which is the key integrity guarantee consumers should rely on. Because the table carries no date, timestamp, status, or message-text columns in the documented schema, it should be understood as a deduplicated recipient mapping rather than an event log with timestamps; any temporal analysis would require joining to notification-queue or workflow-history tables outside this object.

Common Use Cases and Queries

Typical uses of GMS_NOTIFICATIONS include auditing notification coverage per award, identifying which users are associated with an award's event stream, and validating that event-driven alerts fired as expected during award processing or workflow batch runs. A representative query joining to the award header is:

• SELECT n.award_id, a.award_number, n.event_type, n.user_id FROM gms.gms_notifications n JOIN igf.igf_aw_award_all a ON a.award_id = n.award_id WHERE n.event_type = :event_type;
• SELECT n.user_id, COUNT(*) FROM gms.gms_notifications n GROUP BY n.user_id ORDER BY 2 DESC; — recipient activity profile.
• SELECT u.user_name, n.award_id, n.event_type FROM gms.gms_notifications n JOIN fnd_user u ON u.user_id = n.user_id WHERE n.award_id = :award_id; — notification detail for a single award.

Because the table is small and key-based, it is inexpensive to scan and works well as a lookup when building award-centric reporting for grants administrators. Reconciliation reports can compare expected notification recipients against actual rows to detect gaps in alert delivery.

Related Objects

• IGF_AW_AWARD_ALL — referenced via GMS_NOTIFICATIONS.AWARD_ID; the award header/master entity.
• FND_USER — referenced via GMS_NOTIFICATIONS.USER_ID; the EBS user account table providing recipient identity.
• GMS_NOTIFICATIONS_U1 — the unique index enforcing the (AWARD_ID, EVENT_TYPE, USER_ID) business key.
• GMS schema objects — related grants-notification setup and workflow objects in the same schema that generate or consume these records.