Search Results update_registered_user_b

Overview

IRC_PARTY_BK2 is a generated PL/SQL package body residing in the APPS schema within Oracle E-Business Suite, classified under the Info Router / iRecruitment product family (IRC). It functions as an API hook pre-processor component for the party update flow, specifically the "Back2" (BK2) implementation of the registered user party API. The body is auto-generated by the Oracle HRMS API Hook Pre-processor and carries the header signature irhzpapi.pkb 120.30.12010000.4, with generation traced to 2009/03/30. Its purpose is to expose the pre-processing hook logic invoked before the core party update logic executes, allowing customer-specific or product-specific validation and derivation logic to run against the incoming party attributes for a registered user (an iRecruitment-registered external person).

Key Procedures and Functions

• UPDATE_REGISTERED_USER_A — The primary documented hook procedure. It receives the effective date, person identifier, and the full set of registered user name and personal attributes (first name, last name, date of birth, title, gender, marital status, previous last name, middle name, name suffix, known-as name, and phonetic derivations), together with the descriptive flexfield attribute columns (ATTRIBUTE_CATEGORY through ATTRIBUTE30) and the PER_INFORMATION flexible column set (PER_INFORMATION_CATEGORY and PER_INFORMATION1..N). Its role is to execute the "A" (pre-process) phase of the party update hook chain.
• UPDATE_REGISTERED_USER_B — The companion documented procedure, typically representing the post-process ("B") phase of the same hook pipeline for the registered user update. Both procedures are signature-aligned so that the framework can invoke the before and after hook steps consistently.

These are the two documented procedures in the package; the parameter lists mirror the underlying HR party update API and should not be assumed to differ from the generated stub described in the source excerpt.

Tables Accessed

The ETRM metadata does not enumerate directly referenced tables for this package body. As a generated hook pre-processor, IRC_PARTY_BK2 does not perform direct DML against base tables in the standard case; instead it operates on the inbound attribute values and passes control to the underlying party API. Where customization is layered, hook bodies may read from or write to the flexible attribute columns belonging to PER_ALL_PEOPLE_F and PER_PERSON_TYPE_USAGES-style party records via the owning API, but such access is mediated by the base API rather than executed explicitly here.

Usage Notes

• The package is invoked indirectly by the HRMS API Hook mechanism whenever a registered user's party record is updated, rather than being called directly by end users.
• It is most commonly triggered from the iRecruitment "Update Registered User" / personal information self-service flows and from any forms or concurrent process that calls the underlying UPDATE_REGISTERED_USER party API.
• Referenced by at least one other package in the APPS schema, consistent with its role as a hook participant in a larger call chain.
• Because the body is auto-generated, customizations should be applied only through the supported hook extension points; direct edits to the generated stub risk being overwritten on patching.
• The "_A" and "_B" suffixes denote the pre- and post- hook phases and are the only extension surface exposed by this body.