Search Results fnd_notifications_s

Overview

The APPS.NTN package body is a Workflow Notification utility package in Oracle E-Business Suite, delivered and valid in both 12.1.1 and 12.2.2. It provides a programmatic interface for creating, manipulating, forwarding, and deleting rows in the Oracle Workflow notification tables, bypassing the interactive Notification System web pages. The package wraps the underlying FND_NOTIFICATIONS base table and its FND_NOTIFICATIONS_S sequence, exposing a small, controlled surface of PL/SQL entry points that application teams can call from forms, concurrent programs, or custom code. The documented API classification is OTHER, reflecting that it is an internal helper rather than a published, supported public API.

The user search term fnd_notifications_s is directly relevant: the sequence is a hard dependency of NTN and is used to generate primary keys for new notification rows.

Key Procedures and Functions

• SEND_NOTIFICATION — Creates a notification, returning the newly generated notification identifier. This is the principal outbound entry point for programmatically notifying a recipient.
• DELETE_NOTIFICATION — Removes a notification identified by its notification ID, providing cleanup beyond the standard Workflow APIs.
• DELETE_NOTIF_BY_ID_TYPE — Deletes notifications by combining an identifier with a notification type, supporting bulk or targeted removal where the type discriminates the rows.
• GET_NOTIFICATION_ATTRIBUTE — Retrieves a single attribute value from a notification. This is the read-side accessor used to interrogate notification content.
• FORWARD_NOTIFICATION — Reassigns an existing notification to a different recipient, effectively delegating or redirecting an outstanding work item.
• NAME — Returns the package name string, a standard helper used for diagnostics, error messages, and tracing contexts.
• TEST_IN — A testing entry point used to exercise the package's notification logic in isolation.

No parameter signatures are documented in the ETRM metadata, so exact argument lists should be confirmed against the deployed package specification in the relevant environment.

Tables Accessed

• FND_NOTIFICATIONS — The core transactional table for workflow notifications. NTN reads, inserts, updates, and deletes here.
• FND_NOTIFICATIONS_S — The sequence supplying primary keys for new notification rows created via SEND_NOTIFICATION.
• FND_APPLICATION — Referenced to resolve application context associated with notifications.
• DUAL — Used for simple sequence and expression evaluation.

All table references resolve through APPS synonyms, and the package additionally depends on FND_MESSAGE, FND_PROFILE, HR_EMPLOYEES, PO_MESSAGE_S, and the standard DBMS_SQL, DBMS_OUTPUT, and DBMS_STANDARD packages.

Usage Notes

NTN is not referenced by any other database object, so it is invoked only by external callers. Typical consumers are custom concurrent programs that must raise or clear workflow notifications automatically, form personalizations or custom forms that redirect approvals, and integration code that forwards notifications when an approver is unavailable. Because the package writes directly to FND_NOTIFICATIONS rather than exclusively through the supported Workflow Notification APIs, DBAs should treat calls to it as sensitive and validate them in a test environment before production use. The presence of TEST_IN reinforces that the package was designed with internal verification in mind. On 12.2.2 the online patching editioning model applies, so the APPS edition in which NTN resolves must be considered when calling from custom code.