Search Results per_vacancy_api




Overview

PER_VACANCY_API is a public PL/SQL API owned by the APPS schema in Oracle E-Business Suite (validated across 12.1.1 and 12.2.2). It is the programmatic interface for creating, maintaining, and removing vacancy records within Oracle Human Resources, part of the Oracle iRecruitment and HR vacancy management infrastructure. Vacancies represent authorized, unfilled positions that can be published for recruitment and later linked to requisitions and applicants.

The package is classified as a business API and depends on the HR_API utility package (for row-handling, validation, and WHO-column derivation logic) and the SYS.STANDARD package. It is referenced by the higher-level PER_VACANCY_SWI (Server-side Wrapper Interface) package, which is the layer typically invoked by forms and concurrent processes rather than the API directly.

Key Procedures and Functions

The package exposes three documented procedures:

  • CREATE_VACANCY — Inserts a new vacancy record. The procedure accepts the vacancy attributes (such as vacancy name, organization, status, and related descriptive fields) and performs the required validation and defaulting through HR_API before committing the row to PER_ALL_VACANCIES.
  • UPDATE_VACANCY — Modifies an existing vacancy. It locates the target vacancy and applies the changed attributes, preserving audit columns and enforcing business rules such as permissible status transitions.
  • DELETE_VACANCY — Removes or logically terminates a vacancy record. As with other HR APIs, deletion is normally a logical operation governed by the assignment status and date-tracking model rather than a physical row delete.

No parameter lists are documented in the ETRM metadata, so exact signatures should be confirmed against the package specification in the target instance. All three follow the standard HR API calling convention, including the p_validate flag that allows a call to run in validation-only mode without committing data.

Tables Accessed

The package reads and writes the following tables via APPS synonyms:

  • PER_ALL_VACANCIES — The primary vacancy entity table. CREATE_VACANCY inserts here; UPDATE_VACANCY and DELETE_VACANCY modify existing rows.
  • PER_ALL_ASSIGNMENTS_F — The date-tracked assignment table, used to associate vacancies with positions/assignments and to respect the effective-dating model when vacancy status affects assignment data.
  • PER_ASSIGNMENT_STATUS_TYPES — The assignment status lookup, consulted for validation of status values applied to vacancy-related assignments.

The inclusion of date-tracked tables reflects the effective-dating discipline inherent in Oracle HR, ensuring vacancy changes are correctly recorded against the appropriate date range.

Usage Notes

PER_VACANCY_API is not normally called directly by end users. It is invoked through the PER_VACANCY_SWI wrapper from the Oracle HR/iRecruitment forms, and it may be called from concurrent programs that bulk-create or maintain vacancies, or from custom PL/SQL that needs to manage vacancy data programmatically. Developers should call the SWI layer where available and use the API only for direct, controlled integration.

Because the package participates in the HR date-tracked model, calls should supply correct effective dates and run with p_validate set to true first to surface validation errors before committing. As PER_VACANCY_API is a documented, supported public interface, it is the preferred integration point over direct DML against PER_ALL_VACANCIES, which bypasses security, WHO-column, and business-rule enforcement provided by HR_API.