Search Results create_candidate_internal

Overview

APPS.IRC_PARTY_BK5 is a generated PL/SQL package body in the Oracle E-Business Suite iRecruitment module (the IRC product prefix). It functions as an API hook pre-processor stub — a bridge layer that sits between date-effective business logic and the underlying HRMS person/party APIs. The package was produced automatically by the Oracle HRMS API Hook Pre-processor and carries the header irhzpapi.pkb 120.30.12010000.4, dating the shipped source to 2008, with generation timestamped 2009/03/30.

Its business purpose is to support the creation of internal candidates — that is, existing employees or applicants within the enterprise who are applying for requisitions through iRecruitment. Rather than writing directly to HR person tables, the API hook layer collects the full set of person attributes and forwards them to the standard date-tracked party creation routine. This design allows Oracle to extend person creation logic (new columns, validations, or derived attributes) without breaking customer or internal callers.

Key Procedures and Functions

The package exposes two documented procedures, both of which are variants of the same internal candidate creation entry point:

• CREATE_CANDIDATE_INTERNAL_A — The primary documented signature. This procedure accepts the complete set of person attributes required to build a candidate record: business group, name components (last, first, middle, previous, suffix, known-as, phonetic forms), personal details (date of birth, gender, marital status, e-mail, title), thirty generic descriptive flexfield attributes, and a PER_INFORMATION_CATEGORY container with eight PER_INFORMATION slots for person extra information types. It performs the pre-processing step that validates and normalizes these inputs before handing control to the date-effective person API layer.
• CREATE_CANDIDATE_INTERNAL_B — The companion hook procedure generated as the second half of the pre-processor pattern. Where the _A variant gathers and prepares the attribute set, the _B variant completes the hook chain that the HRMS date-tracked framework calls during the create operation, ensuring the iRecruitment-specific attributes are persisted alongside the core person record.

The naming convention — a fixed name with _A/_B suffixes — is characteristic of generated hook packages and is not intended for direct customer invocation.

Tables Accessed

The package operates through APPS synonyms rather than direct schema references. Although the ETRM metadata does not enumerate specific tables, the parameter set maps directly onto the standard HR person structures: PER_ALL_PEOPLE_F for the person record and its date-effective attributes, PER_PERSON_NAMES_F for the multi-part name, PER_ALL_PEOPLE_DETAILS or associated person detail entities, and PER_PERSON_INFO_TYPES / PER_PERSON_EXTRA_INFO for the PER_INFORMATION and descriptive flexfield values. The DFF attribute parameters (ATTRIBUTE1 through ATTRIBUTE30) correspond to attribute columns on the person entity, while the PER_INFORMATION category/value pairs correspond to person extra information type rows.

Usage Notes

IRC_PARTY_BK5 is referenced by one other package in the ETRM metadata, meaning it is invoked internally rather than exposed as a public API endpoint. It is not a candidate for direct calls from forms, concurrent programs, or custom extensions. The supported integration path for creating internal candidates is the IRC_API or the underlying HR_EMPLOYEE_API / HR_PERSON_API public interfaces, which in turn drive this hook package during the date-tracked save.

Because the object is generated code prefixed with the generated ship header, any customizations applied directly to this package body would be overwritten by Oracle patches. Custom attribute capture should instead be routed through the descriptive flexfield and extra information type parameters already surfaced in the API signature. This package is therefore best understood as an internal implementation detail of the iRecruitment candidate creation flow, not a documented customization point.