Search Results per_vacancy

Overview

The APPS.IRC_VARIABLE_COMP_ELEMENT_API package is a public iRecruitment API that manages variable compensation elements associated with a vacancy. In Oracle EBS 12.1.1 and 12.2.2, variable compensation elements represent components of a candidate's or employee's total compensation that vary based on performance, such as bonuses, incentives, commissions, or other discretionary pay. This package allows integrators and developers to attach such elements to a specific vacancy during the recruitment or requisition lifecycle, enabling accurate representation of the complete compensation package offered for a position.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer. The header comment explicitly scopes the object as public and identifies product IRC (iRecruitment) as the owning application. The API is licensed for use with iRecruitment, so usage outside a properly licensed environment is not permitted.

Key Procedures and Functions

The package exposes two documented procedures:

• CREATE_VARIABLE_COMPENSATION — Creates a variable compensation element for a vacancy. The vacancy must already exist prior to invocation. On success, the variable compensation element is created for the vacancy; on failure, no record is created and an error is raised. Documented parameters include p_validate (validate-only mode that leaves the database unchanged when true), p_vacancy_id (identifies the vacancy the element applies to), p_variable_comp_lookup (the type of variable compensation element, validated against the IRC_VARIABLE_COMP_ELEMENT lookup type), p_effective_date (reference date used to validate that lookup values fall within their active date range; it does not determine when changes take effect), and p_object_version_number (set to the version number of the created record when p_validate is false).
• DELETE_VARIABLE_COMPENSATION — Removes a previously created variable compensation element from a vacancy, typically requiring the object version number for optimistic locking consistent with Oracle EBS API conventions.

Tables Accessed

The package operates through APPS synonyms on the underlying iRecruitment tables that store vacancy variable compensation data. The primary target table is the base table behind the variable compensation element entity, keyed by vacancy_id and validated against the IRC_VARIABLE_COMP_ELEMENT lookup type maintained in the standard Oracle lookup infrastructure (FND_LOOKUP_VALUES). Writes are performed during create and delete operations, while reads support validation of the vacancy's existence, lookup validity, and effective dating. The documented metadata does not enumerate specific table names, and the package is referenced by one other package within the application, indicating its role as a shared dependency for higher-level iRecruitment logic.

Usage Notes

This API is typically invoked from iRecruitment forms or custom PL/SQL code when a recruiter or administrator defines or modifies the compensation structure of a vacancy. It follows the standard Oracle EBS API pattern: callers should first invoke with p_validate = TRUE to confirm all business rules pass without modifying data, then re-invoke with p_validate = FALSE to commit the change and capture the returned object version number for subsequent updates or deletes. Because a valid vacancy and a valid lookup code are prerequisites, calling code must ensure the vacancy exists and the lookup value is active for the supplied p_effective_date. Concurrent programs and integration scripts loading vacancy compensation data from external HR or compensation systems are common consumers. Error handling should follow the standard FND_MSG_PUB message stack conventions, as failures raise exceptions rather than returning status codes.