Search Results create_note_a

Overview

IRC_NOTES_BK1 is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle iRecruitment (IRC) product family and implements the business knowledge (BK) layer of the Notes API for Application Programming Interface hook processing. The package was generated by the Oracle HRMS API Hook Pre-processor, as indicated by the header comment, and the source header identifies the underlying file as irinoapi.pkb, version 120.0. Its creation timestamp of 2008/11/06 places it within the 12.1.1 development lineage, and the object remains present and documented in 12.2.2.

The package functions as a thin wrapper that bridges the Notes entity API to the HR API hook framework. Rather than performing business logic directly, it delegates processing to the corresponding business entity package, IRC_NOTES_BE1, when the hook framework signals that application hooks should be invoked. This separation of concerns allows customer extensions and legislative logic to be plugged in without modifying the base API surface. It is classified under the ETRM API classification of OTHER and is referenced by one dependent package.

Key Procedures and Functions

The package body exposes two documented procedures.

• CREATE_NOTE_A — The primary creation routine. It accepts the note identifier, the associated offer status history identifier, the note text, and an object version number. Internally it records the entry point with hr_utility.set_location, captures the current commit unit via hr_api.return_commit_unit, and conditionally invokes IRC_NOTES_BE1.CREATE_NOTE_A when hr_api.call_app_hooks returns true. On completion it closes the validation set with hr_multi_message.end_validation_set, validates the commit unit against the 'CREATE_NOTE' action for the 'AP' product, and logs its exit.
• CREATE_NOTE_B — A companion procedure that accepts the offer status history identifier and note text. In the documented source it contains only entry and exit location markers, indicating it is a hook placeholder generated for the pre-processing framework rather than an active implementation.

Tables Accessed

The documented metadata for this package lists no directly referenced tables through APPS synonyms. This is consistent with its architectural role: all data manipulation is performed by the business entity layer (IRC_NOTES_BE1) that the package invokes, and by the HR API infrastructure procedures such as hr_api.validate_commit_unit. Persistent writes to the underlying Notes and offer status history records therefore occur indirectly rather than through SQL embedded in this package body. Deployments that need to trace database impact should inspect the business entity package rather than this hook layer.

Usage Notes

IRC_NOTES_BK1 is invoked automatically through the HRMS API hook mechanism and is not typically called directly by end users. Standard invocations originate from the Notes API entry points used by iRecruitment forms, self-service pages, and any concurrent or custom code that creates notes associated with offer status history. The call_app_hooks guard ensures the delegated logic executes only when the runtime environment has application hooks enabled.

Because the package follows the generated hook pattern, it should not be modified in place; any required extension should be implemented in the designated hook packages or in the business entity layer. The commit-unit validation performed at the end of CREATE_NOTE_A means callers must operate within a properly initialized HR API transaction context. Developers troubleshooting note creation failures should verify that the commit unit matches, that validation messages are flushed correctly, and that the dependent package reference has not been invalidated during patching or upgrades.