Search Results irc_idp_upd




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.IRC_IDP_UPD is a PL/SQL record-interface package belonging to the Oracle iRecruitment schema (IRC) within Oracle E-Business Suite. The package family follows Oracle's standard Table-Handler API (THAPI) design pattern, in which a base table handler (in this case the underline table handler identified by the iridprhi.pkh header reference) exposes a controlled, validated update interface to a single HR schema entity. The suffix _UPD designates that this package supplies the update path of the business process; companion packages typically provide insert (_INS) and delete (_DEL) behaviour.

The business role of the package is to accept a fully validated row in record format from a calling process and persist the update to the underlying entity, returning any system-generated values such as the object version number to the caller. The header dates the file to release 12.1 (120.0.12010000.1, 2008), and the same API classification ("OTHER") applies in the 12.2.2 ETRM metadata, where the package is documented as referencing the IRC_DEFAULT_POSTINGS table through APPS synonyms and as being referenced by one other package.

Key Procedures and Functions

The documented interface exposes a single procedure, UPD, which functions as the record interface for the update process on the specified entity. Its internal processing sequence is defined explicitly in the package comments and proceeds as follows:

  • The row targeted for update is locked and selected into the record structure g_old_rec, ensuring that the caller operates against the current persisted image of the row.
  • Because parameters that are not part of the update need not be defaulted, the procedure reconstructs the updated row by converting any system-defaulted parameters to their corresponding values.
  • The controlling validation process update_validate is executed, which in turn runs all private and public validation business rules applicable to the entity.
  • The pre_update process executes, permitting logic to run before any DML is issued.
  • The update_dml process physically performs the update DML against the specified entity.
  • The post_update process executes, permitting logic to run after the DML completes.

The main business-process parameters must be supplied in the record format expected by the handler. No parameter list is documented in the ETRM metadata; callers should rely on the published package specification rather than on assumptions about individual arguments.

Tables Accessed

The ETRM metadata documents one table referenced via APPS synonyms: IRC_DEFAULT_POSTINGS. iRecruitment uses default postings to define the standard posting configuration applied when requisitions or vacancies are published to recruitment sources; the update API therefore persists changes to those posting definitions for the entity governed by this table handler. Consistent with the THAPI pattern, the procedure reads the pre-update image of the row (locked into g_old_rec) and writes the validated new image back to the same entity, with system-generated attributes such as the object version number refreshed during the update.

Usage Notes

APPS.IRC_IDP_UPD is not intended for ad hoc DML against the underlying table. It is normally invoked from higher-level iRecruitment business logic — typically the entity's higher-level API or PL/SQL wrappers called by Oracle Forms, OAF pages, or concurrent programs that manage default postings. Custom code should call the documented update procedure rather than issuing direct UPDATE statements, so that row locking, validation rules, and pre/post-update logic all execute. Because the package is referenced by one other package, existing callers should be reviewed before custom extensions are introduced. As with all APPS-owned APIs, modifications must be made through a supported customisation mechanism, and the object version number returned by the update should be retained by the caller to support subsequent optimistic-locking checks.