Search Results per_people3_pkg




Overview
Explore in AI Chat

Overview

APPS.HR_EMPLOYEE_APPLICANT_API is a public Oracle E-Business Suite PL/SQL API classified as an API within the Human Resources (HR) product family. Its primary business function is to support the hire and re-hire lifecycle by enabling conversion of an applicant record into an employee record within the PER schema, and by supplying supporting utilities required to complete that conversion. The package therefore sits at the boundary between Oracle iRecruitment / applicant tracking data and core HR person and assignment data, allowing a candidate’s applicant rows to be promoted to a full employee with associated assignment, period of service, pay proposal, and person type usage records.

The package is documented as VALID and owned by the APPS schema. It depends on the APPS.HR_API library and on core person model tables, and it is referenced by eleven other packages, including PER_PEOPLE3_PKG, PER_PEOPLE4_PKG, PER_PEOPLE12_PKG, PER_PEOPLE_PKG, and HR_MX_EMPLOYEE_APPLICANT_API. This places it on the standard code path used by Oracle’s own person-maintenance and hire processing logic, meaning it is exercised by seeded forms, business process flows, and concurrent processes rather than being an isolated utility.

Key Procedures and Functions

The ETRM metadata documents 18 procedures and functions. The principal entry points are:

  • HIRE_TO_EMPLOYEE_APPLICANT — Performs the core action of hiring an applicant into an employee applicant state, orchestrating the validation and insertion of the underlying person, assignment, and supporting records.
  • HIRE_EMPLOYEE_APPLICANT — Completes the hire of an employee applicant, finalising the applicant-to-employee transition.
  • LOCATE_ELEMENT — Locates a payroll element applicable to the hire so that element entries can be created for the new employee.
  • LOCATE_VALUE — Resolves the appropriate value for a located element or related input, supporting element entry creation.
  • IS_CONVERT — Determines whether the current operation constitutes an applicant-to-employee conversion, gating the conversion-specific logic.
  • CONVERT_FLAG — Returns or manages the conversion flag used to signal conversion processing.
  • END_DATE_EXISTS — Checks for the presence of an end date on relevant records, validating whether a dated record already terminates.
  • END_DATE_FLAG — Returns or manages the flag governing end-date handling during hire or conversion.
  • RETAIN_EXISTS — Determines whether retainable data exists that must be carried forward from the applicant record.
  • RETAIN_FLAG — Returns or manages the retain flag used to govern retention of applicant data during the hire.
  • TAB_IS_EMPTY — Utility that tests whether a supplied PL/SQL table or collection is empty before processing.
  • EMPTY_TABLE — Utility that empties or initialises a PL/SQL table used by the API.

These routines are typical of a date-tracked HR API: the flag-returning functions (IS_CONVERT, CONVERT_FLAG, END_DATE_FLAG, RETAIN_FLAG) and existence checks (END_DATE_EXISTS, RETAIN_EXISTS) provide the conditional branching that governs how the hire or conversion is written.

Tables Accessed

The package reads and writes the following tables through APPS synonyms, which represent the core of the Oracle HR person model:

Usage Notes

Because HR_EMPLOYEE_APPLICANT_API is invoked by PER_PEOPLE3_PKG, PER_PEOPLE4_PKG, PER_PEOPLE12_PKG, and PER_PEOPLE_PKG, it is normally executed indirectly through standard Oracle person and hire processing rather than called directly. It is also referenced by PQP_HROSS_INTEGRATION and PQP_PERASGADD_RIW, indicating use from Oracle Advanced Benefits integration and Assignment Addition business process (BPEL) flows. The HR_MX_EMPLOYEE_APPLICANT_API reference confirms a Mexican localisation wrapper exists. Custom code should invoke the supported public entry points (HIRE_EMPLOYEE_APPLICANT and HIRE_TO_EMPLOYEE_APPLICANT) rather than manipulating the underlying tables directly, and should respect the flag and date-checking routines to maintain date-tracked integrity.