Search Results irc_idp_ins




Overview
Explore in AI Chat

Overview

IRC_IDP_INS is a technical PL/SQL package in the APPS schema of Oracle E-Business Suite Release 12.1.1 and 12.2.2 that implements the insert-side record interface for the iRecruitment default postings entity. The package belongs to the iRecruitment module, which manages external and internal job posting configuration. The prefix "IDP" designates the IRC_DEFAULT_POSTINGS entity, and the suffix "INS" identifies the package as the generated insert handler produced by the Oracle Designer table API generator, evidenced by the object's header signature (iridprhi.pkh) and the standardized procedural scaffolding.

As documented in the ETRM metadata, the package is classified as an "OTHER" API, meaning it is not a public, supported business API intended for external integration. Its access status is explicitly annotated "Internal Development Use Only," signaling that it exists to support generated boilerplate operations for the underlying entity rather than to expose business functionality.

Key Procedures and Functions

The metadata documents three procedures and functions within this package. Two are named explicitly, while the remainder consists of generated validation and pre-processing logic referenced in the insert flow.

  • SET_BASE_KEY_VALUE — Registers the next available primary key value from the database sequence for the entity. This procedure receives the surrogate key attribute (documented as the default posting identifier) and primes the insert process so that system-generated key values are consistent with the sequence.
  • INS — The record interface for the insert process. It inserts a fully validated row for the specified entity into the HR schema and returns system-generated values, such as the primary key and object version number, to the calling process. The documented processing sequence is: (1) the controlling validation process, INSERT_VALIDATE, executes all private and public validation business rules; (2) the PRE_INSERT business process executes to allow logic to run before the insert DML; and (3) the insert DML itself is performed. This procedure is described as the main backbone of the insert process.
  • Additional generated members — The package also exposes the underlying helper procedures implied by the flow above, including the validation and pre-insert hooks. These are internal to the generated API structure and are not invoked directly by end users.

Tables Accessed

Per the ETRM metadata, the package references two database objects via APPS synonyms:

  • IRC_DEFAULT_POSTINGS — The base table that stores iRecruitment default posting configuration records. The INS procedure writes new rows into this table after validation completes.
  • IRC_DEFAULT_POSTINGS_S — The corresponding sequence used by SET_BASE_KEY_VALUE to obtain the next surrogate primary key value. The sequence ensures that generated identifiers remain unique across concurrent inserts.

These two objects form the complete persistence layer for the package; no other tables are documented as accessed.

Usage Notes

IRC_IDP_INS is an internal, generated artifact and is not intended for direct invocation by customers or integrators. The ETRM metadata records that the package is referenced by two other packages, indicating that its insert interface is called from within the iRecruitment framework whenever a new default posting record must be created.

Typical invocation paths include the iRecruitment forms that maintain posting defaults, concurrent processes that seed or copy default posting configurations, and any Oracle-provided package performing entity maintenance on IRC_DEFAULT_POSTINGS. Custom code should avoid calling this package directly; instead, developers requiring default posting inserts should route through the supported business API layers or the standard forms, because the package operates with internal-only status and its logic depends on validation hooks that assume the generated framework context. Any direct call must supply the full validated record payload and expect system-managed key and version values to be returned by the INS procedure.