Search Results terminate_applicant

Overview

APPS.HR_APPLICANT_BK3 is a generated PL/SQL package body that forms part of the Oracle HRMS Applicant API architecture within Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the family of "BK" (backup or bridge) packages produced by the Oracle HRMS API Hook Pre-processor, whose purpose is to provide a stable and extensible invocation point for business events surrounding the termination of applicants. The package encapsulates the pre-processing and post-processing logic associated with the TERMINATE_APPLICANT API, allowing customers and Oracle development teams to attach custom business rules without modifying the core HR_APPLICANT_API implementation. It is classified as an "OTHER" API in the documented metadata, indicating that it is an internal supporting object rather than a public, callable business API. The header comment peappapi.pkb 120.39.12020000.6 confirms that it is generated from the applicant API source and shipped with the EBS release.

Key Procedures and Functions

• TERMINATE_APPLICANT_A — The primary procedure within this package body. It implements the hook-enabled variant of the applicant termination operation. It accepts the full set of termination attributes, including effective date, person identifier, object version number, person type, termination reason, effective start and end dates, and a boolean flag controlling the removal of future assignment warnings. The procedure records its entry point through HR_UTILITY.SET_LOCATION, captures the current commit unit number via HR_API.RETURN_COMMIT_UNIT, and conditionally invokes the corresponding hook procedure in HR_APPLICANT_BE3 when business event hooks are enabled. Upon completion it closes the validation set through HR_MULTI_MESSAGE.END_VALIDATION_SET and validates the commit unit using HR_API.VALIDATE_COMMIT_UNIT with the identifiers 'TERMINATE_APPLICANT' and 'AP'.
• TERMINATE_APPLICANT_B — A companion procedure that mirrors the termination signature with a reduced parameter set (effective date, person identifier, object version number, person type, and termination reason). In the documented source it contains only location tracing calls, serving as a placeholder or hook stub within the generated package body.

Tables Accessed

The documented package metadata does not list any base tables referenced directly through APPS synonyms. This is consistent with the design of hook packages: all persistent data manipulation is delegated to the underlying HR_APPLICANT_API and HR_APPLICANT_BE3 packages, which in turn operate against the PER_ALL_PEOPLE_F, PER_PERSON_TYPES, and related applicant/termination tables. HR_APPLICANT_BK3 itself performs no direct DML; its role is limited to orchestrating hook invocation, validation set management, and commit unit integrity checks.

Usage Notes

This package is not intended for direct invocation by end users or external integrations. It is called indirectly whenever the TERMINATE_APPLICANT business API is executed, typically from the Oracle HRMS applicant termination form, from concurrent programs processing applicant records, or from custom code that invokes the public applicant API. The referenced-by count of one package indicates a single internal consumer, most likely the main HR_APPLICANT_API or its wrapper. Developers extending applicant termination behavior should implement their logic in the corresponding hook procedure exposed by HR_APPLICANT_BE3 rather than modifying HR_APPLICANT_BK3, since the latter is regenerated by the API Hook Pre-processor during patching and upgrades. Any customization placed directly in the generated package body will be overwritten.