Search Results irc_notes_api




Overview
Explore in AI Chat

Overview

IRC_NOTES_API is a public PL/SQL API in the APPS schema that manages the creation, maintenance, and removal of notes attached to Oracle iRecruitment business objects. In Oracle E-Business Suite 12.1.1 and 12.2.2, iRecruitment relies on a notes infrastructure to capture free-form textual commentary throughout the recruitment lifecycle — for example, recruiter observations on applicants, interview feedback annotations, and status-related remarks recorded against offers and requisitions. IRC_NOTES_API provides the sanctioned programmatic entry point for this infrastructure, insulating callers from the underlying note storage model and enforcing consistent handling of note attributes such as context, visibility, and audit columns.

The package is classified as an API in the ETRM repository, carries a VALID status, and is owned by APPS. Its dependency footprint includes the HR_API package, reflecting the shared Oracle Human Resources technology stack that iRecruitment builds upon, along with the SYS.STANDARD package that is common to virtually all PL/SQL units.

Key Procedures and Functions

Three documented procedures constitute the public interface of IRC_NOTES_API:

  • CREATE_NOTE — Inserts a new note record linked to the relevant iRecruitment entity. Callers supply the note content and the identifying context of the parent object; the procedure is responsible for populating mandatory columns and defaulting system-maintained attributes so that the resulting row is fully consistent with the notes data model.
  • UPDATE_NOTE — Modifies the content or attributes of an existing note that was previously created through the API. This allows corrections and amendments to be applied without direct DML against the underlying table.
  • DELETE_NOTE — Removes a note from the repository, typically invoked when a note is obsolete or was recorded in error. Use of the API ensures that any dependent processing associated with note removal is respected.

Only these three entry points are documented in the ETRM metadata; no additional public procedures or functions are enumerated. Parameter lists are intentionally omitted here, and implementers should consult the package specification in the target instance for exact signatures.

Tables Accessed

The ETRM extract for this object does not enumerate specific base tables; the documented metadata records no explicit table list. Functionally, the package operates against the iRecruitment notes storage underlying the IRC_NOTES entity, accessed through APPS synonyms. Because CREATE_NOTE, UPDATE_NOTE, and DELETE_NOTE collectively cover the full insert, update, and delete lifecycle, the package performs both read and write operations: it validates and inserts new note rows, updates existing rows in place, and deletes rows upon request. Direct table access through synonyms rather than fully qualified schema references is the standard pattern in the APPS-owned iRecruitment APIs and preserves the install-portable naming convention.

Usage Notes

IRC_NOTES_API is referenced by other packages in the iRecruitment stack, notably IRC_NOTES_SWI, which acts as a supplemental or wrapper interface, and IRC_OFFER_STATUS_HISTORY_API, which records notes as part of offer status transitions. This inbound dependency indicates that the API is invoked implicitly during routine iRecruitment processing — for example, when an offer status change generates a historical note — as well as explicitly by application code that needs to attach commentary to a record.

Typical invocation scenarios include iRecruitment self-service and professional forms that present a notes region to recruiters and hiring managers, concurrent or workflow-driven processes that annotate records automatically, and custom extensions or integrations that must add notes while preserving data integrity. Custom code should call the documented API rather than performing direct inserts or updates against the notes table, because the API centralizes validation, defaulting, and any dependent side effects. Because the package depends on HR_API, callers should ensure that the standard HR security and business-group context is initialized before invocation. In patched or upgraded environments, the specification in the deployed instance remains the authoritative reference for available overloads and parameter semantics.