Search Results create_registered_user

Overview

The APPS.IRC_PARTY_BK1 package body is a generated PL/SQL API hook belonging to the Oracle iRecruitment (IRC) product family. It is produced by the Oracle HRMS API Hook Pre-processor, as indicated by the generated header comments, and its source revision (irhzpapi.pkb 120.65, dated 2011/12/06) places it within the standard Oracle E-Business Suite 12.1.1 and 12.2.2 code line. The package provides the "Before Process" (_BK1) hook layer for the party registration business flow — the entry point used to create a registered user record associated with a party in iRecruitment. Its business role is to expose pre-processing hooks that Oracle Forms and the HRMS API framework can call to customise or validate data before the core registration logic executes. In the ETRM classification this object is registered as API classification "OTHER".

Key Procedures and Functions

Two documented procedures are exposed by this package body:

• CREATE_REGISTERED_USER_A — The primary hook procedure for the create-registered-user flow. It accepts the full set of party and person attributes being supplied during registration, including name fields (last name, first name, middle name, maiden/previous last name, suffix, known-as, phonetic names), personal details (date of birth, gender, marital status, title), contact information (e-mail address), descriptive flexfield columns (P_ATTRIBUTE_CATEGORY and P_ATTRIBUTE1 through P_ATTRIBUTE30), and the person information flexfield columns (P_PER_INFORMATION_CATEGORY and P_PER_INFORMATION1 onward). The procedure signature is deliberately wide to mirror the person/party API payload; user hook code is placed here to validate or default these values before the main API processing continues.
• CREATE_REGISTERED_USER_B — The companion hook procedure for the same registration event. In the HRMS API Hook pattern, the _A and _B variants represent the two standard pre-processing hook points invoked at defined stages of the calling API; both are stubs intended to be overridden by customer extensions.

Tables Accessed

The ETRM metadata for this package lists no directly referenced tables via APPS synonyms. This is consistent with its role as a generated hook body: it does not itself perform DML against party or person tables, but rather passes parameter values through to the underlying HRMS and iRecruitment registration APIs that perform the actual inserts and updates into the party, person, and contact tables. Any table interaction occurs in the calling API, not within this hook package.

Usage Notes

IRC_PARTY_BK1 is invoked indirectly rather than being called directly by end users. The iRecruitment registration form and the underlying HRMS party/person API call the hook procedures at the designated pre-processing points during user registration, giving implementers a supported extension surface for site-specific validation, defaulting, or derivation of party attributes without modifying Oracle seeded code. The metadata records that this package is referenced by one other package, confirming it is consumed within the iRecruitment API call stack. Custom developers should treat the bodies of CREATE_REGISTERED_USER_A and CREATE_REGISTERED_USER_B as the extension points, adding logic between the generated begin and end markers while preserving the procedure signatures. Because the package is regenerated by the HRMS API Hook Pre-processor during patching, customisations should follow Oracle's documented hook-customisation methodology so they survive upgrades across 12.1.1 and 12.2.2.