Search Results create_note

Overview

IRC_NOTES_API is a public PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It provides the programmatic interface for creating, maintaining, and removing notes associated with offer status history records within the iRecruitment module. Notes captured through this API are attached to the status progression of an offer, allowing recruiters, hiring managers, and approvers to record commentary, decisions, and audit-relevant annotations at specific points in the offer lifecycle.

The package follows the standard Oracle EBS API design pattern. Each public procedure acts as a wrapper around the corresponding business logic, delegating the physical insert, update, and delete operations to the underlying table-handler package IRC_INO_INS while invoking user hooks through IRC_NOTES_BK1. The header date of the source, 2005/09/27, and the version string irinoapi.pkb 120.0 place the package within the 11i/12.x code line; the documented procedures remain unchanged in 12.1.1 and 12.2.2, where the API classification is recorded as API in the ETRM repository.

Key Procedures and Functions

• CREATE_NOTE — Inserts a new note row against a given offer status history identifier. It accepts the note text and the owning offer status history ID, and returns the newly generated note identifier together with the object version number for the created record. A validation mode parameter allows the caller to exercise the full validation path without committing data.
• UPDATE_NOTE — Modifies the text of an existing note. It operates on a previously created note, applies the supplied attribute changes, and maintains the object version number so that concurrent modification is detected through the standard optimistic locking mechanism.
• DELETE_NOTE — Removes an existing note from the offer status history. Following EBS convention, deletion is performed through the API rather than by direct DML so that the delete user hook and any dependent validation logic are honoured.

Each procedure opens with a savepoint and delegates pre-processing to the corresponding user hook in IRC_NOTES_BK1. If the hook program unit is absent, the package traps HR_API.CANNOT_FIND_PROG_UNIT and routes the condition through HR_API.CANNOT_FIND_PROG_UNIT_ERROR, preserving the extensibility contract expected of a public EBS API.

Tables Accessed

The ETRM metadata for this package lists no directly referenced tables through APPS synonyms. This is consistent with the observed implementation: CREATE_NOTE performs no direct INSERT, instead calling IRC_INO_INS.INS to populate the underlying note table, which is the notes entity keyed by offer status history. Read and write access to the physical table is therefore encapsulated in the private table-handler package, and all audit columns and object version numbers are derived there. Customisations should treat IRC_INO_INS and the note table as internal to the API and continue to address data only through IRC_NOTES_API.

Usage Notes

IRC_NOTES_API is referenced by two other packages in the APPS schema, indicating that it is a supporting API consumed by higher-level offer and recruitment business flows rather than an entry point in its own right. Typical invocation occurs from iRecruitment offer status forms and from custom or extension code that must record notes during automated status transitions. Because the procedures expose an object version number and a validation flag, they are suitable for both interactive form sessions and batch processing where rows are manipulated without end-user intervention. Callers should always supply the offer status history identifier, commit or roll back the enclosing transaction explicitly, and expect the normal HR_API error stack when validation fails.