Search Results send_notification

Overview

The APPS.HR_WPM_NTF_UTIL package is a utility package within the Oracle E-Business Suite Human Resources module, specifically associated with Oracle Performance Management and the Workforce Performance Management (WPM) notification framework. Its primary business function is to construct and dispatch notifications related to personal scorecards and performance appraisal activities. In the context of Oracle EBS 12.1.1 and 12.2.2, this package acts as a supporting utility that other components of the Performance Management application call upon when a business event requires a notification to be sent to a participant — for example, an employee, a manager, or another stakeholder in a scorecard workflow.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which supports its role as a flexible utility invoked across different execution contexts. It is classified as a UTIL (utility) API in the ETRM documentation.

Key Procedures and Functions

The documented package specification exposes a single named function, SEND_NOTIFICATION, which appears in two overloaded forms. Both overloads return a number, consistent with the package-level constants SUCCESS (1) and FAILURE (0), allowing the caller to determine whether the notification was dispatched successfully.

• send_notification (first overload) — Accepts source and target person identifiers, an action type, a subject message, a scorecard identifier, and a reason. This form is oriented toward notifications where the sender and recipient are explicitly identified by their PER_ALL_PEOPLE_F person identifiers, making it suitable for person-to-person notifications tied to a personal scorecard.
• send_notification (second overload) — Accepts an action type, a scorecard identifier, a manager notification indicator, and a reason. This form derives the notification participants implicitly, for example from the manager relationship and the scorecard context, rather than requiring explicit from/to person identifiers.

Both overloads share the concept of an action type, a scorecard reference, and a reason, which together describe the trigger, the subject matter, and the rationale for the notification.

Tables Accessed

The package reads and writes against several core Oracle HRMS tables, accessed through APPS synonyms:

• PER_PERSONAL_SCORECARDS — The central table holding personal scorecard records; the scorecard identifier drives notification content and context.
• PER_ALL_PEOPLE_F — Used to resolve people and their person type information for notification recipients and senders.
• PER_ALL_ASSIGNMENTS_F, PER_PERSON_TYPES, PER_PERSON_TYPE_USAGES_F, and PER_POS_STRUCTURE_ELEMENTS — Employed to resolve organizational context, assignments, and position hierarchy, which determine routing of performance-related notifications.
• PER_PERF_MGMT_PLANS — Provides the performance management plan context within which a scorecard operates.
• FND_NEW_MESSAGES and WF_LOCAL_ROLES — Support the delivery and addressing of the notification itself, with FND_NEW_MESSAGES holding the generated message and WF_LOCAL_ROLES resolving workflow roles for recipients.

Usage Notes

This utility is typically invoked indirectly rather than directly by end users. It is called by the Oracle Performance Management application logic — including scorecard processing and performance management plan workflows — when a business event requires a notification. The ETRM metadata records that no other packages reference it, indicating it is a leaf-level utility consumed by application code and possibly by notification-generating processes rather than a shared foundation component.

Custom code that needs to replicate the standard Performance Management notification behavior may call SEND_NOTIFICATION directly, choosing the overload appropriate to whether the sender and recipient are explicitly known. Callers should check the return value against SUCCESS and FAILURE to handle dispatch outcomes. Because the package uses AUTHID CURRENT_USER, invoking code must have the necessary privileges on the underlying tables and workflow objects. Availability of the function and its behavior should be verified against the specific patch level of the 12.1.1 or 12.2.2 environment, since the documented header dates to the 12.1 release family.