Search Results irc_idp_bus




Overview
Explore in AI Chat

Overview

IRC_IDP_BUS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, and resides within the Oracle iRecruitment product family. The IRC prefix identifies it as part of the iRecruitment application, while the IDP segment denotes its association with the iRecruitment Data Pump or Identified Data Processing component. The package functions as a business logic layer that validates operations against the iRecruitment data structures, providing a controlled interface through which data movement operations are screened before reaching the underlying tables.

In Oracle EBS 12.1.1 and 12.2.2, IRC_IDP_BUS holds VALID status, confirming that it compiles cleanly and its dependencies resolve correctly. The ETRM metadata classifies it under the OTHER API classification, indicating that it is a supporting business package rather than a formally recognized public API. It operates in conjunction with the shadow table IRC_IDP_SHD, which it references directly, and it is depended upon by three related packages: IRC_IDP_DEL, IRC_IDP_INS, and IRC_IDP_UPD. This dependency pattern demonstrates that IRC_IDP_BUS acts as a shared validation layer invoked by dedicated insert, update, and delete handlers.

Key Procedures and Functions

The package exposes three documented validation procedures, each aligned to a specific DML operation:

  • INSERT_VALIDATE — Validates data before a new iRecruitment record is created. It confirms that the candidate record satisfies the business rules governing new entries, such as verifying organizational and positional references.
  • UPDATE_VALIDATE — Validates modifications to existing records. It ensures that proposed changes remain consistent with the associated organization, job, and position definitions before the update is committed.
  • DELETE_VALIDATE — Validates removal operations. It checks whether a record may be safely deleted without violating referential or business constraints, protecting data integrity during purge or cleanup activity.

All three procedures follow a consistent naming convention that reflects their role as pre-operation gates. No parameter lists are documented in the ETRM metadata, so invocation signatures should be confirmed against the deployed source before use in custom code.

Tables Accessed

IRC_IDP_BUS references four tables through APPS synonyms:

  • HR_ALL_ORGANIZATION_UNITS — Supplies organization definitions, used to validate that a posting or candidate record is tied to a valid organizational unit.
  • HR_ALL_POSITIONS_F — Provides position data, enabling validation of positional assignments against current position definitions.
  • IRC_DEFAULT_POSTINGS — The iRecruitment table of default postings; the package validates posting-related attributes against this table.
  • PER_JOBS — Supplies job definitions, used to confirm that referenced jobs exist and are active for the validation context.

Beyond these tables, the package references the shadow table IRC_IDP_SHD, which typically holds staged or transient data during processing.

Usage Notes

IRC_IDP_BUS is not an end-user entry point; it is invoked programmatically. The primary consumers are IRC_IDP_INS, IRC_IDP_UPD, and IRC_IDP_DEL, which call the corresponding validation routines before performing their own DML. This design centralizes business rule checking so that insert, update, and delete paths share identical validation logic.

Customizations should avoid calling these procedures directly unless the calling module already manages transaction boundaries and error handling consistent with the standard iRecruitment flow. The package is also referenced by itself, which may indicate internal recursive validation or overloaded helper logic. When troubleshooting iRecruitment data movement errors, tracing calls into IRC_IDP_BUS often reveals the precise validation rule that blocked an operation.