Results for “gms_notification_pkg”

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

Overview

The APPS.GMS_NOTIFICATION_PKG package body is a stored PL/SQL program unit within the Oracle E-Business Suite Grants Management (GMS) module, owned by the APPS schema and reported with a VALID status in the ETRM metadata. Its business purpose is to manage the creation, maintenance, and deletion of notification records associated with grants personnel and grant-related reports. Notifications in this context support the Grants Management workflow by alerting users, principal investigators, and administrative personnel to events that require attention, such as report due dates or personnel-related changes.

The package exposes a combination of low-level row maintenance routines (insert, lock, delete) and higher-level business routines that generate or remove default notification events for personnel and reports. It is catalogued with the API classification "OTHER" and is referenced by one other database object. Notably, per the metadata, APPS.GMS_NOTIFICATION_PKG is not referenced by any database object in the dependency listing, while the package itself references several APPS and SYS objects.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions:

• INSERT_ROW — Inserts a new notification record into the GMS_NOTIFICATIONS table, encapsulating the standard column defaults and validation logic expected by the notification data model.
• LOCK_ROW — Acquires a row-level lock on an existing notification record, supporting concurrency control for subsequent updates or deletes within the same transaction.
• DELETE_ROW — Removes a single notification record, typically used when an event or recipient is no longer relevant.
• CRT_DEFAULT_PERSON_EVENTS — Creates the default set of notification events for personnel records, generating the standard notifications that apply to a person in the grants context.
• CRT_DEFAULT_REPORT_EVENTS — Creates the default notification events associated with grant reports, ensuring report-related reminders are established.
• DEL_DEFAULT_PERSON_EVENTS — Removes the default personnel notification events, providing the inverse of CRT_DEFAULT_PERSON_EVENTS during cleanup or reassignment.
• DEL_DEFAULT_REPORT_EVENTS — Removes the default report notification events, reversing the report-event creation logic.

Tables Accessed

Based on the documented dependency list, the package references the following objects through APPS synonyms:

• GMS_NOTIFICATIONS — The primary notification store; every insert, lock, and delete operation ultimately targets this table.
• GMS_PERSONNEL — Supplies personnel data used when creating or deleting default person events.
• FND_USER — Provides user identity information, resolving notification recipients to valid EBS application users.

Additional referenced objects include GMS_DEFAULT_REPORTS_V (a view supplying default report definitions), GMS_ERROR_PKG and APP_EXCEPTION for error handling, FND_MESSAGE for message text resolution, and SYS.STANDARD for Oracle-supplied types.

Usage Notes

This package is typically invoked indirectly rather than by end users. The default-event procedures (CRT_DEFAULT_PERSON_EVENTS and CRT_DEFAULT_REPORT_EVENTS) are commonly triggered during grants setup or award activation, when personnel assignments or report schedules are established. The corresponding DEL_ routines fire when those assignments are terminated or reconfigured.

The row-level procedures support GMS forms and concurrent programs that maintain notification data. Custom extensions and interfaces should call these routines rather than performing direct DML on GMS_NOTIFICATIONS, to preserve business validation and error handling via GMS_ERROR_PKG and APP_EXCEPTION. Because the metadata shows the package is not referenced by other database objects, integrators should treat it as a reusable utility layer whose callers are form-based or external rather than PL/SQL-dependency-driven.