Search Results convert_to_applicant_b

Overview

The APPS.HR_APPLICANT_BK4 package is a private PL/SQL body stub belonging to the Oracle E-Business Suite Human Resources (HR) and iRecruitment applicant API layer. It is one of the generated "BK" (book/body) packages derived from the public HR_APPLICANT_API specification, and its primary purpose is to expose the low-level implementation entry points that the public applicant API uses to convert a non-applicant person record into an applicant record within Oracle EBS 12.1.1 and 12.2.2.

In business terms, this package underpins the "Convert to Applicant" functionality used by HR and iRecruitment administrators when an existing employee or contingent worker must be registered as a candidate for one or more recruitment activities. The conversion links the person's PER_PEOPLE_F record to the applicant data model (including PER_APPLICANTS / PER_APPLICANT_ENTRIES), assigns an applicant number, and sets the applicant person type, thereby making the individual visible to recruiter searches, vacancy applications, and the iRecruitment pipeline. The package name is frequently surfaced in ETRM searches because customers report it when diagnosing conversion failures, so understanding its role is important for troubleshooting the applicant-creation flow.

Key Procedures and Functions

• convert_to_applicant_b — The "before" or business-layer procedure that performs the substantive conversion logic. It accepts the effective date, person identifier, business group, object version number, applicant number, and person type identifier, and is responsible for validating input, deriving the applicant record, and preparing the data for the underlying DML.
• convert_to_applicant_a — The "after" or API-layer procedure associated with the same conversion. In addition to the parameters of the "_b" variant, it returns the effective start and end dates of the new applicant record and an p_appl_override_warning flag that signals whether the conversion produced a business-rule warning that the caller may need to acknowledge or present to the user.

The "_a" and "_b" naming convention follows the standard Oracle HRMS API pattern, where the "_b" procedure encapsulates business logic and the "_a" procedure completes the API contract and exposes out parameters. Only these two procedures are documented in the ETRM metadata; the package contains no additional public functions.

Tables Accessed

The ETRM metadata for this object does not enumerate the base tables directly, as access is performed through APPS synonyms and via the parent public API. In practice, the conversion logic reads and writes the core Oracle HRMS person and applicant tables, including PER_ALL_PEOPLE_F for the person record, PER_APPLICANTS and PER_APPLICANT_ENTRIES for the applicant entity and its effective-dated attributes, and the person-type and applicant-numbering setup tables that supply the p_person_type_id and p_applicant_number values. Because the metadata lists no explicitly referenced tables, this section should be treated as functional guidance rather than a definitive object-level inventory.

Usage Notes

This package is not intended for direct invocation by end users. It is called by the public HR_APPLICANT_API and is referenced by at least one other package in the APPS schema. In Oracle EBS 12.1.1 and 12.2.2, the conversion is typically triggered from iRecruitment or HR forms (for example, applicant-creation and "convert to applicant" UI actions) and may also be reached through concurrent programs or custom integrations that call the public applicant API. When diagnosing errors that cite HR_APPLICANT_BK4, the root cause usually lies in invalid person type, applicant-numbering setup, or business-group configuration rather than in the private body itself; developers should always code against the public HR_APPLICANT_API rather than the "_BK" body, as the latter is subject to change without notice and is not a supported integration surface.