Search Results irc_ino_upd




Overview
Explore in AI Chat

Overview

The APPS.IRC_INO_UPD package is a PL/SQL database object within the Oracle E-Business Suite (EBS) Applications schema, classified under the iRecruitment (IRC) product family. Its naming convention—combining the IRC product prefix with INO (iRecruitment Notes/Notification Objects) and the UPD suffix—indicates its role as a procedural update handler for iRecruitment note records. The package holds VALID status in both Oracle EBS 12.1.1 and 12.2.2, confirming it remains an active component of the iRecruitment architecture across releases.

The package serves as a low-level update utility that supports the broader iRecruitment notes framework. Rather than exposing business-facing functionality directly, it provides the internal mechanism through which note content maintained by the iRecruitment application is modified within the database. It is documented in the E-Business Suite Technical Reference Manual (ETRM) as an OTHER-classified API, distinguishing it from standard public APIs such as those conforming to the HR_API interface pattern.

Key Procedures and Functions

The documented package specification exposes one program unit:

  • UPD — The sole documented procedure in the package. Consistent with the package's naming and dependency profile, its purpose is to perform the update operation against iRecruitment note data. It embodies the write-side logic that complements the IRC_INO_SHD shadow (read/display) package referenced in the dependency chain. As with other shadow-and-update package pairs in EBS, IRC_INO_UPD.UPD is intended to be called by higher-level APIs rather than invoked directly by end users or forms. The ETRM documentation does not publish a parameter list for this procedure; callers should resolve the signature from the package specification in the target instance before attempting direct invocation.

Tables Accessed

Per the documented metadata, the package accesses the following via APPS synonyms:

  • IRC_NOTES — The primary iRecruitment notes table. This stores note records associated with recruitment entities such as vacancies, candidates, and requisitions. The UPD procedure writes to this table to persist modified note content.
  • DBMS_LOB — Not a table in the conventional sense, but the Oracle-supplied Large Object package. Its presence in the referenced-object list indicates that IRC_INO_UPD manipulates CLOB or BLOB columns on IRC_NOTES—most likely the extended note text or attached content—using LOB locator APIs rather than plain SQL string operations. This is significant for performance and locking considerations when updating large notes.

Usage Notes

IRC_INO_UPD is referenced by one documented package: IRC_NOTES_API. This confirms its position as an internal implementation layer beneath the public iRecruitment Notes API. Standard application flow therefore reaches IRC_INO_UPD.UPD indirectly through IRC_NOTES_API, which handles validation and business rules before delegating the physical update.

The package also appears in its own reference list—a normal artifact of package body and specification cross-references in the ETRM dependency extract—and it declares dependencies on HR_API, IRC_INO_SHD, and the SYS STANDARD package, situating it firmly within the Oracle HRMS/iRecruitment stack.

Typical invocation scenarios include:

  • Updates driven by iRecruitment self-service forms when a user edits or appends note text to a recruitment record.
  • Concurrent or batch processes that programmatically revise notes, provided they call through IRC_NOTES_API.
  • Custom extensions that require direct note updates; in such cases the supported route remains IRC_NOTES_API, and direct calls to IRC_INO_UPD.UPD should be treated as unsupported and carefully regression-tested during patch or upgrade cycles.