Search Results hrdpp_create_us_applicant




Overview
Explore in AI Chat

Overview

HRDPP_CREATE_US_APPLICANT is an Oracle EBS PL/SQL package owned by the APPS schema that supports the Oracle iRecruitment and Human Resources applicant-processing pipeline. The prefix HRDPP identifies the package as part of the HR Data Pump Processing family, a set of utilities used to stage, validate, and load external data into the HRMS tables through the HR_PUMP_BATCH mechanism. The package is classified under the ETRM as OTHER, indicating that it is not a published, officially supported public API but rather an internal processing routine invoked by other EBS components.

Its business function is to create and stage United States applicant records — including candidate, assignment, and related detail rows — into the HR data pump batch tables before those rows are validated and transferred to the production applicant tables. This staging approach isolates external or bulk applicant data from live HRMS records until it has passed consistency and lookup validation.

Key Procedures and Functions

The ETRM metadata documents seven callable units within the package. Their roles, consistent with the HR Data Pump naming conventions, are as follows:

  • CALL — The primary entry point that orchestrates the applicant creation process, coordinating the remaining subprograms and sequencing the staging and load steps.
  • INSERT_BATCH_LINES — Inserts the staged applicant and assignment data into the HR_PUMP_BATCH_LINES and HR_PUMP_BATCH_LINE_USER_KEYS tables.
  • N (New) — Handles new-record processing, preparing rows for applicants that do not yet exist in the target HRMS tables.
  • D (Delete) — Handles deletion processing, removing or marking staged rows as deleted.
  • ND (New/Delete) — A combined handler for records requiring both new and delete processing semantics.
  • DC (Delete/Change) — Processes staged rows where an existing record must be deleted and a replacement created.
  • DD (Delete/Delete) — Processes rows where multiple deletions or duplicate-removal logic applies.

The precise parameter lists for these procedures are not published in the ETRM metadata and therefore should be confirmed against the package specification in the target instance before use.

Tables Accessed

The package references five HR_PUMP batch objects through APPS synonyms:

  • HR_PUMP_BATCH_LINES — The core staging table holding individual applicant data rows awaiting validation and load.
  • HR_PUMP_BATCH_LINES_S — The sequence used to generate unique batch line identifiers.
  • HR_PUMP_BATCH_EXCEPTIONS — Captures rows that fail validation, allowing erroneous records to be reported without aborting the entire batch.
  • HR_PUMP_BATCH_LINE_USER_KEYS — Stores user-defined key values associated with each staged line, used to map external identifiers to EBS records.
  • HR_PUMP_BATCH_LINE_USER_KEYS_S — The sequence supporting the user key table.

No direct references to the production applicant tables (PER_ALL_PEOPLE_F, IRC_APPLICANTS, and related objects) appear in the dependency metadata; those tables are reached by the standard data pump load procedures rather than by this package directly.

Usage Notes

Because HRDPP_CREATE_US_APPLICANT is not a documented public API and is referenced by zero other packages per the ETRM dependency report, it is best treated as an internal implementation routine. It is normally invoked indirectly — through Oracle iRecruitment applicant-import flows, the HR data pump concurrent programs, or seeded forms that populate the HR_PUMP_BATCH tables — rather than called directly from custom code. Developers who encounter this package while tracing an applicant-import error should inspect HR_PUMP_BATCH_EXCEPTIONS for validation failures and review the batch line rows for incomplete key mappings. If a custom integration must call the package, invoke it under a properly initialized APPS session with HR security context established, and validate the package specification in the exact instance (12.1.1 or 12.2.2) because signatures can differ between releases. Direct modification of package source is not supported.