Search Results per_vacancy_bk3




Overview
Explore in AI Chat

Overview

The APPS.PER_VACANCY_BK3 package body is an Oracle HRMS API Hook pre-processor generated artifact that forms part of the PL/SQL API infrastructure supporting the Vacancy business object within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its header signature (pevacapi.pkb 120.5, dated 2010/12/24) and its internal delegation to PER_VACANCY_BE3 identify it as one of the layered components of the HRMS Vacancy API stack: the _BK3 "before" hook layer that executes prior to the business-entity implementation, allowing customer or product extensions to intercept the operation.

Functionally, the package exposes the pre-processing entry point for deleting a vacancy record. It is not a user-facing API; rather, it is invoked by the HRMS API framework as part of the standard DELETE_VACANCY flow so that registered application hooks can run before the actual delete logic in PER_VACANCY_BE3 is performed.

Key Procedures and Functions

Two documented procedures are exposed, both private-style hooks corresponding to the same vacancy deletion operation across two API phases:

  • DELETE_VACANCY_A — The primary pre-processor hook. It sets a location marker for tracing, captures the current commit unit via hr_api.return_commit_unit, and, when hr_api.call_app_hooks returns true, invokes the corresponding procedure in PER_VACANCY_BE3 to run any registered application hooks. It then finalises the multi-message validation set with hr_multi_message.end_validation_set and validates the commit unit against the identifier 'DELETE_VACANCY' for the 'AP' (application) context. Its parameters carry an object version number and a vacancy identifier, enabling optimistic locking and record selection.
  • DELETE_VACANCY_B — A companion hook that in the shipped body contains only entry and exit location markers, with no substantive logic. It serves as a placeholder/stub in the generated hook framework, typically reserved for a secondary phase of the delete lifecycle where no product code is currently required.

No parameter lists are reproduced here beyond what the source shows; both procedures are documented as accepting an object version number and a vacancy identifier.

Tables Accessed

The ETRM metadata records no direct table references (via APPS synonyms) for this package body. This is consistent with its role as a thin hook layer: all persistent reads and writes against the underlying vacancy tables are performed by the business-entity package PER_VACANCY_BE3, which this package delegates to. Any DML therefore occurs indirectly through that downstream component rather than within PER_VACANCY_BK3 itself.

Usage Notes

This package is not intended for direct invocation by end users or custom code. It is called automatically by the Oracle HRMS API Hook framework when the DELETE_VACANCY API is executed—typically triggered from the Vacancy management forms, from the Recruiting/HRMS business flows, or from custom PL/SQL that calls the published vacancy API. The metadata notes that it is referenced by one other package, confirming its position as a dependent component in the API call chain rather than an entry point. Developers extending vacancy deletion behaviour should implement their logic in a registered application hook invoked through hr_api.call_app_hooks, not by modifying this generated package body.