Search Results create_gb_applicant

Overview

The APPS.HR_NZ_APPLICANT_API package body provides the New Zealand‑specific localisation logic for creating and maintaining external applicant records within Oracle Human Resources. In Oracle EBS 12.1.1 and 12.2.2, the global HR_APPLICANT_API handles the multi‑national core of applicant registration, while country‑specific packages such as this one wrap the core API and supply region‑mandated fields — for New Zealand, notably the IRD number (Inland Revenue Department tax identifier). The package is owned by APPS, classified as an API in the ETRM repository, and its header identifies it as a localisation wrapper (hrnzwrap.pkb, version 120.2). Its principal business purpose is to allow recruitment and HR users, and any integrated external systems, to register a New Zealand applicant through a single supported programmatic entry point that ultimately populates the base HR applicant and person tables.

The package exposes only public procedures; no private helper procedures or functions are declared in the documented body beyond the package variable g_package, which is used to prefix error messages raised by the API.

Key Procedures and Functions

• CREATE_NZ_APPLICANT — the single documented public procedure. It creates a New Zealand applicant record and accepts a standardised set of applicant attributes. The signature uses a p_validate flag that defaults to FALSE, enabling callers to perform a rolling‑back validation before committing real data. Mandatory and near‑mandatory inputs include the date the application was received, the business group that owns the record, the applicant’s last name, sex and person type. It also accepts a wide range of optional personal, contact and tax attributes — first and middle names, known‑as name, previous last name, title, date of birth, marital status, nationality, email address, work telephone, registered‑disabled indicator, the New Zealand p_ird_number, an expense cheque send‑to address, and descriptive flexfield segments via p_attribute_category and p_attribute1 … p_attribute3. The p_applicant_number parameter is declared IN OUT NOCOPY, so the procedure generates and returns the applicant number (or validates a caller‑supplied one) without a redundant copy of the string.

Tables Accessed

Per the documented metadata, the package references the APPS synonym HR_COMMENTS. This table stores free‑text comments attached to the resulting person or applicant record, so the procedure writes (or validates) comment rows associated with the applicant it creates. The remaining base table activity — inserts into PER_PEOPLE_F, PER_ALL_PEOPLE_F, PER_PERSON_TYPES, applicant and applicant‑assignment tables, and the various PER_ address and phone structures — is performed indirectly through the core HR applicant API that this localisation package wraps, which is why those tables are not enumerated separately in the ETRM object listing.

Usage Notes

Because it is an API‑class package, HR_NZ_APPLICANT_API is intended to be called programmatically rather than through direct table manipulation. Typical invocations include:

• The Oracle iRecruitment and external applicant registration flows for a New Zealand business group, which call the localisation wrapper so that IRD number and NZ statutory fields are captured.
• Custom PL/SQL, database triggers or concurrent programs that bulk‑load applicants from external recruitment agencies or legacy systems, using p_validate = TRUE first to dry‑run the data and surface errors before committing.
• Country‑specific forms customisations or personalisations that need to validate an applicant number or create an applicant on behalf of a user.

Callers must supply a valid p_business_group_id and observe the standard HR API error‑handling convention: the procedure raises exceptions prefixed with the package variable g_package, and the p_applicant_number may be passed back to the caller after creation. No other packages are documented as calling this one, so it should be treated as a leaf‑level localisation API invoked directly by forms, concurrent processes or custom code.