Search Results per_vac_del




Overview
Explore in AI Chat

Overview

PER_VAC_DEL is a PL/SQL package owned by the APPS schema that operates within the Oracle Human Resources (HR) and Oracle iRecruitment foundation of Oracle E-Business Suite. Its specific purpose is the controlled removal of vacancy records held in Oracle HRMS. A vacancy in EBS represents an authorized, unfilled position or opening that can be published for recruiting, tracked against requisitions, and linked to applicant and offer activity. Because vacancies are referenced by other HR objects, deletion is treated as a specialized housekeeping operation rather than a casual DML activity, and PER_VAC_DEL encapsulates that operation.

The package is classified in the ETRM repository as an "OTHER" API type, meaning it is an internal utility package rather than a public, seeded business API. This classification is significant: the package is not intended to be the primary interface for vacancy maintenance. Oracle's recommended entry point for vacancy transaction processing is PER_VACANCY_API, which is documented as referencing PER_VAC_DEL. This indicates that PER_VAC_DEL is a subordinate, low-level routine invoked by the higher-level vacancy API to complete the physical or logical removal of vacancy data.

Key Procedures and Functions

The documented package metadata lists a single procedure for PER_VAC_DEL:

  • DEL — The sole documented program unit in the package. Consistent with the naming convention observed across the PER schema, DEL performs the deletion processing for one or more vacancy records. It serves as the internal mechanism by which a vacancy is removed after the calling layer has completed validation and any required dependent-record handling. The metadata does not document a public parameter list, and the exact arguments should not be assumed; callers should inspect the installed source or the wrapper routine in PER_VACANCY_API to determine the required inputs.

No functions are documented for the package. The absence of a documented return value further supports its characterization as a procedural housekeeping routine whose success or failure is communicated through the normal PL/SQL exception mechanism rather than a status return.

Tables Accessed

The documented table reference for PER_VAC_DEL is:

  • PER_ALL_VACANCIES — The base table in Oracle HRMS that stores vacancy definitions, accessed through an APPS synonym. This is the primary target of the DEL procedure, as it holds the vacancy rows being removed.

In addition, the dependency information shows that the package references PER_VAC_SHD, the shadow (audit) table associated with the PER_ALL_VACANCIES family of tables. Oracle HRMS maintains parallel shadow tables to capture historical or audited versions of dated/controlled records; interaction with PER_VAC_SHD indicates that deletion activity is reflected in the audit trail alongside the base table.

Usage Notes

PER_VAC_DEL is not normally invoked directly from forms, concurrent programs, or custom code. Its documented reference by PER_VACANCY_API establishes the intended invocation path: the vacancy API orchestrates validation, date-track and audit handling, and then calls into PER_VAC_DEL for the actual removal step. Customizations that need to delete vacancies should call PER_VACANCY_API rather than PER_VAC_DEL, because bypassing the API layer risks inconsistent data across PER_ALL_VACANCIES, PER_VAC_SHD, and any dependent HR or recruiting records.

The package is marked VALID in the APPS schema, confirming that it is correctly compiled and available on both Oracle EBS 12.1.1 and 12.2.2 where the HRMS product family is installed. Because it is an internal "OTHER" object rather than a certified public API, Oracle does not guarantee its signature across patches or upgrades. Customers should avoid binding custom code to the DEL procedure directly. Where an inspection of the source is required for troubleshooting, DBMS_METADATA or ALL_SOURCE queries against the APPS schema remain the appropriate method, and any recompilation should be performed only in coordination with the standard AD patching process.