Search Results hr_pump_get




Overview

APPS.HR_PUMP_GET is a core lookup and resolution utility within the Oracle E-Business Suite HR Data Pump architecture. In Oracle EBS 12.1.1 and 12.2.2, the HR Data Pump (HR_DATA_PUMP) is the batch extraction and loading framework used to migrate, copy, and transform HR and payroll data between business groups, environments, and statutory contexts. While HR_DATA_PUMP performs the orchestration, validation, and write operations, HR_PUMP_GET acts as the read-side counterpart: it resolves incoming external user keys into the internal primary keys required by the pump's downstream insert and update logic.

The package body is owned by APPS and holds a VALID status. It exposes an extensive library of GET_* resolution functions—258 documented procedures and functions in total—that translate business-meaningful identifiers (names, codes, flex values) into row identifiers across the HR, Payroll, Benefit, and Person data model. It is one of the most heavily reused utilities in the Oracle HRMS schema, with 229 dependent packages referencing it, underscoring its role as a foundational component rather than an application-layer API.

Key Procedures and Functions

The documented procedures are uniformly identifier-resolution functions, each mapping a user key or descriptive attribute to a surrogate primary key. Representative examples include:

These functions are designed to be invoked in sequence by the pump to translate an externally supplied user key into the internal PK, then pass that PK to dependent write APIs.

Tables Accessed

The package reads from a broad set of HRMS base tables, all accessed through APPS synonyms. The documented dependencies fall into four groupings:

The consistent use of _F (date-tracked) tables reflects the package's need to return current-effective identifiers.

Usage Notes

HR_PUMP_GET is not exposed through a standalone form. It is invoked programmatically from other PL/SQL packages—documented as referenced by 229 packages—and from the HR Data Pump concurrent programs and batch loading routines. It is also called from custom migration and integration code that relies on the Data Pump framework to move HR and Payroll data.

Typical invocation patterns include: resolving user keys read from HR_PUMP_BATCH_LINE_USER_KEYS into internal PKs; supplying identifiers to HR_DATA_PUMP and HR_API for downstream inserts; and feeding benefit and payroll resolution logic invoked during life-event or enrolment extraction. Because the functions are pure resolution lookups without DML, they are safe to call inside larger transactions. In 12.2.2 the same behavior and dependencies apply, so it remains the standard mechanism for key translation across HRMS batch processing.

Custom code should treat HR_PUMP_GET as an internal implementation utility: it is version-sensitive across EBS releases and should be invoked only where the standard Data Pump flow requires a user-key-to-PK resolution.