Search Results create_notification

Overview

IRC_CREATE_NOTIFICATION_PKG is an Oracle E-Business Suite package owned by the APPS schema that supports notification generation within the iRecruitment module. Its principal role is to create notification records for recruitment-related events, drawing preference and recipient data from iRecruitment notification configuration tables. The package is classified as an OTHER API, meaning it is not a public, fully supported interface API in the tradition of Oracle's documented open interfaces; it functions primarily as an internal processing component invoked by iRecruitment processing logic rather than being exposed for direct customer extension.

The header comment embedded in the package specification dates the source to 2006 (ircnrpkg.pkh 120.0) and explicitly states that the file uses ad_parallel_updates to achieve parallelism. This confirms that create_notification is designed to run as a parallel-enabled concurrent program, allowing notification generation to be distributed across multiple worker processes for large volumes of recruitment activity.

Key Procedures and Functions

• CREATE_NOTIFICATION — The single documented procedure in the package. It follows the standard concurrent program entry point convention, returning an error buffer and return code to the concurrent manager via the errbuf and retcode OUT parameters. It accepts a process number, a maximum number of processes, a table owner, and a batch size, all passed as VARCHAR2 values. These parameters drive the parallel processing behavior referenced in the package header: the process number and maximum process count identify the specific worker instance within the parallel run, the batch size controls how many records are processed per iteration, and the table owner parameter allows dynamic SQL or query construction against a designated schema. The procedure's purpose is to evaluate notification preferences and generate the appropriate notification records for recipients.

Tables Accessed

• IRC_NOTIFICATION_PREFERENCES — Stores the configured notification preferences that determine which recruitment events trigger notifications and under what conditions. The procedure reads this table to determine whether a notification should be generated.
• IRC_NOTIFICATION_PREFS_S — The sequence associated with the notification preferences entity, used to generate or resolve preference identifiers during notification creation.
• PER_ALL_ASSIGNMENTS_F — The core HR assignments table. It supplies assignment context, which is essential for identifying the correct person and organization associated with a recruitment notification recipient.
• PER_ALL_PEOPLE_F — The core HR people table, used to resolve recipient identity and personal details required for constructing the notification.
• PLITBLM — The PL/SQL index-by table memory structure used internally for bulk processing and array handling, consistent with the batch-oriented, parallel design of the procedure.

Usage Notes

During the Oracle EBS 12.1.1 and 12.2.2 releases, this package is typically invoked through the concurrent program framework rather than directly from forms or custom code. The presence of errbuf and retcode parameters confirms it is registered as a concurrent program, and the process number, maximum process count, and batch size parameters indicate it is submitted with parallel processing options enabled through ad_parallel_updates. iRecruitment administrators generally interact with it indirectly by submitting the associated notification-generation concurrent request.

The package is referenced by zero other packages according to the documented metadata, which reinforces its position as a terminal processing routine rather than a shared utility. Because it is classified as an OTHER API and carries the "noship" header designation, it is not intended as a supported extension point. Customizations should avoid direct invocation; instead, standard iRecruitment notification configuration and the delivered concurrent program should be used. Any direct call requires awareness that the VARCHAR2 parameters must be passed as valid numeric strings, since the procedure treats numeric values in character form.