Search Results irc_party_bk6




Overview
Explore in AI Chat

Overview

IRC_PARTY_BK6 is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified in the ETRM repository as an "Other" API, meaning it is not a public, flagship application programming interface but rather an internal or generated hook package that participates in the HRMS/iRecruitment API Hook Pre-processor framework. The source header (irhzpapi.pkb, revision 120.30.12010000.4) and the generated comment block confirm that the package body was machine-generated by the Oracle HRMS API Hook Pre-processor on 2009/03/30, which is characteristic of the paired "BK" (Before/Pre-hook) packages that wrap the corresponding "BE" (Business Entity) packages.

Its central business function is to support the self-registration flow for external users — typically candidates, applicants, or contingent workers entering the iRecruitment or Talent Acquisition landscape — by exposing a pre-processing hook around the SELF_REGISTER_USER operation. Before the core business logic executes, the BK package allows customer-specific or seeded application logic (the "app hooks") to validate, enrich, or transform the incoming registration attributes.

Key Procedures and Functions

The ETRM documentation records two documented procedures:

Tables Accessed

The ETRM metadata does not list any tables accessed directly through APPS synonyms; the package itself contains no explicit SQL against base tables. All persistence occurs indirectly through the delegated call to irc_party_be6, which in turn invokes the underlying iRecruitment/HRMS party and user-account APIs (such as fnd_user and the per_all_people_f family) to create or update the registration record. Because no direct DML is documented, the BK package should be regarded as a pass-through hook layer rather than a data-access module.

Usage Notes

IRC_PARTY_BK6 is not intended to be called directly by end users or by custom forms. It is invoked automatically by the HRMS API Hook framework whenever the self-registration operation is executed — for example from the iRecruitment external candidate self-service pages or from concurrent processes that create user accounts. The metadata notes it is referenced by one other package, which is consistent with the generated hook mechanism.

Customers extending self-registration behavior typically implement their logic in the corresponding _BE or custom hook package rather than modifying this generated body, since the header records it as "generated ship" code that can be regenerated during patching. Because the package exposes P_MIDDLE_NAMES as a first-class registration parameter, it is the appropriate integration point when middle-name capture or transformation must occur before the user record is written.