Search Results create_applicant

Overview

GHR_APPLICANT_API is a public PL/SQL API belonging to the Oracle Human Resources (HRMS) product family, owned by the APPS schema. It exposes a supported programmatic interface for creating and validating external applicant records within Oracle E-Business Suite Release 12.1.1 and 12.2.2. The package body header (ghappapi.pkb 120.0.12010000.1) indicates a long-standing, stable interface that has remained largely unchanged across the 12.x code line. Its principal purpose is to encapsulate the business rules, validation logic, and multi-table insert sequence required to register a new applicant against a business group, thereby shielding callers from the internal structure of the underlying recruitment data model. Because it is classified as an API in the EBS Technical Reference Manual, it is intended for direct invocation by forms, concurrent programs, and custom extensions rather than being treated as an internal implementation detail.

Key Procedures and Functions

The package body documents a single public procedure:

• CREATE_APPLICANT — Inserts a new applicant into the recruitment schema, deriving the applicant's core person record and applications row. It accepts a validation flag plus the mandatory date received, business group, and last name, along with a substantial set of optional demographic, contact, and descriptive-flexfield parameters. Notably, the p_applicant_number parameter is declared IN OUT NOCOPY, reflecting that Oracle may generate an applicant number internally and return it to the caller when one is not supplied. The procedure is defaulted to no-validation mode unless explicitly invoked with validation enabled, allowing callers to pre-validate before committing.

No other procedures or functions are documented for this package in the ETRM metadata, confirming that CREATE_APPLICANT is the sole supported entry point.

Tables Accessed

The documented table reference is PER_APPLICATIONS (accessed through the APPS synonym). This is the primary recruitment table in which the newly created applicant record is stored. The package reads and writes PER_APPLICATIONS to persist the applicant header information — applicant number, date received, business group, and the associated person reference — and to enforce uniqueness and business-group validation. Although the ETRM extract lists only PER_APPLICATIONS, the procedure's parameter set (name, date of birth, sex, nationality, national identifier) implies that the corresponding HR person record is also created as part of the same logical transaction, consistent with the standard Oracle HR applicant model.

Usage Notes

Typical invocation occurs from the Oracle iRecruitment and Human Resources forms, where applicant entry is captured, and from custom PL/SQL that requires bulk or automated applicant registration. Best practice is to call CREATE_APPLICANT first with p_validate = TRUE to confirm business rules, then re-invoke with p_validate = FALSE to perform the actual insert within the application's transaction control. The package is referenced by one other documented package, confirming its role as a foundational dependency in the recruitment API stack. Because it is an APPS-owned public API, customizations should call it directly rather than writing to PER_APPLICATIONS, ensuring validation logic and future upgrades are respected.