Search Results test_in




Overview

The APPS.NTN package is a workfow notification utility within Oracle E-Business Suite, declared with AUTHID CURRENT_USER and residing in the APPS schema. Its principal business function is to serve as a programmatic wrapper around the Oracle Workflow notification engine, allowing PL/SQL code to create, forward, and delete notifications without directly manipulating the underlying Workflow tables. The $Header comment identifies the source file as PONSENDS.pls, with a revision dated November 2002, indicating the package has been stable across the 11i and Release 12 code lines, including 12.1.1 and 12.2.2.

Users searching for forward_notification are typically looking for the mechanism by which an existing Workflow notification is redirected to a different recipient. This is exposed directly through the FORWARD_NOTIFICATION procedure described below.

Key Procedures and Functions

  • SEND_NOTIFICATION — The primary creation routine. It builds and dispatches a Workflow notification to a specified employee, associating it with a message name, an object identifier, a priority, and a range of optional document and date attributes. Recipient identity is passed by employee ID, with an optional from_id to designate the sender. A character array and its lower/upper bounds allow arbitrary notification attributes to be supplied, and the procedure returns both a status code and the generated notification identifier.
  • DELETE_NOTIFICATION — Removes a single notification identified by its notification ID, returning a status code.
  • DELETE_NOTIF_BY_ID_TYPE — Performs a bulk removal of notifications filtered by object ID and document type, useful when cleaning up notifications tied to a business object that is being cancelled or purged.
  • FORWARD_NOTIFICATION — Redirects an existing notification, identified by notification ID, to a new recipient, optionally attaching a forwarding note. This is the procedure corresponding to the user's search term.
  • GET_NOTIFICATION_ATTRIBUTE — Documented but commented out in the package body. It was intended to retrieve the value of a named notification attribute by notification ID.
  • NOTIF_CURRENT — A boolean function that tests whether a given notification ID refers to a current (open) notification.
  • TEST_IN — A diagnostic procedure retained for internal testing purposes.

The NAME entry reflected in the object metadata corresponds to the package's type and internal identifier declarations rather than a callable business API.

Tables Accessed

  • FND_NOTIFICATIONS and FND_NOTIFICATIONS_S — The core Workflow notification tables. These store the notification header, recipient routing, status, and the associated message attributes populated by SEND_NOTIFICATION and modified by FORWARD_NOTIFICATION and the delete routines.
  • FND_APPLICATION — Used to resolve application context, since notifications are keyed to a source application.
  • DUAL — Employed for simple scalar evaluations and function return checks.
  • DBMS_OUTPUT and DBMS_SQL — Standard PL/SQL utilities referenced for diagnostic output and dynamic SQL handling.

Usage Notes

NTN is typically invoked from PL/SQL-based customizations, Workflow function activities, database triggers, and concurrent programs that must raise a notification as a side effect of a business event. It is not generally called directly from an Oracle Forms user interface, because Forms-based Workflow interactions normally go through the Workflow Notification System pages. When a notification must be reassigned — for example during employee departure or workload balancing — FORWARD_NOTIFICATION provides the supported programmatic path. Because the package is compiled with AUTHID CURRENT_USER, privileges are evaluated against the calling schema, and effective use depends on the caller holding appropriate execute grants and access to the underlying FND tables. The metadata records no dependent packages referencing NTN, so it should be treated as a leaf utility rather than a shared framework component.