Search Results hr_applicant_bk4




Overview
Explore in AI Chat

Overview

HR_APPLICANT_BK4 is an Oracle EBS PL/SQL package body owned by the APPS schema that participates in the Oracle HRMS (Human Resources Management System) applicant tracking infrastructure. It is a generated "B" (Before/Book) hook package produced by the Oracle HRMS API Hook Pre-processor, as confirmed by the header comment "Code generated by the Oracle HRMS API Hook Pre-processor" and the underlying source reference peappapi.pkb. Its business purpose is to expose the public, hookable entry point for converting an existing person record into an applicant within the HRMS data model. When an organization hires or transitions an individual, the conversion of a person to an applicant (and vice versa) is a core HRMS operation; this package provides the wrapper procedure that fires the customizable business event hooks before the core applicant entity processing (in the corresponding BE4 package) executes.

Key Procedures and Functions

The ETRM metadata documents two procedures in this package:

  • CONVERT_TO_APPLICANT_A — The primary public API procedure for the convert-to-applicant operation. It accepts the effective date, person identifier, business group context, object version number, applicant number, person type, effective start and end dates, and an override warning indicator. Inside the body it captures the current commit unit, invokes the HR hook mechanism via hr_api.call_app_hooks, delegates to the corresponding business event implementation hr_applicant_be4.CONVERT_TO_APPLICANT_A, finalizes the validation set through hr_multi_message.end_validation_set, validates the commit unit, and returns. This is the version-aware ("A") entry point.
  • CONVERT_TO_APPLICANT_B — A companion procedure sharing the same conversion semantics but with a reduced parameter surface (effective date, person id, business group id, object version number, applicant number, and person type id). The "B" designation typically represents the base or simplified variant used in the hook-processing sequence.

Both procedures are thin orchestration wrappers rather than substantive business logic; the real conversion work is pushed into the BE4 package and Oracle's hook framework.

Tables Accessed

The ETRM metadata lists no directly referenced tables via APPS synonyms for this package. This is consistent with its role as a hook/bridge package: data manipulation against the applicant and person entities (such as PER_ALL_PEOPLE_F and PER_APPLICANTS) occurs within the delegated BE4 implementation and the underlying HRMS API layers rather than in this wrapper. Any persistent writes are therefore indirect, mediated by the called APIs.

Usage Notes

This package is not intended to be called directly by end users or custom code. It is invoked by the Oracle HRMS API framework when a form, concurrent program, or higher-level API triggers the convert-to-applicant business event, and it is referenced by one other package according to the metadata. Its generated nature means it should not be modified; any business customization must be implemented through the supported hook mechanism that hr_api.call_app_hooks activates. Because the procedures are hook entry points rather than standalone utilities, effective behavior depends on the environment's configured hooks and the presence of the corresponding BE4 business-event package. Developers troubleshooting conversion issues should trace from this wrapper into HR_APPLICANT_BE4 rather than expecting logic here. Standard HRMS validation, message collection, and commit-unit handling are performed inline, ensuring consistency with the broader Oracle HR API contract.