Search Results hr_pump_batch

Overview

APPS.HR_DM_COPY is a Data Migration (DM) utility package body belonging to the Oracle Human Resources (PER) product schema. Its role is to manage the infrastructure that supports bulk extraction and loading of HR data between source and target environments. The package provides the operational scaffolding required by the HR Data Migration process, including schema resolution, cleanup of staging tables, and orchestration of copy activity between a source database and a destination database. The package body header (perdmcp.pkb) indicates a long-standing shipped component of the HR Data Migration toolkit, and Oracle EBS 12.1.1 and 12.2.2 both retain this object under the APPS schema.

The package is classified as OTHER and is referenced by two other packages, confirming it operates as a shared utility layer within the HR_DM_* family rather than as a standalone business API. It is not exposed to end users through standard HR forms and is intended for use during migration and data-pump operations.

Key Procedures and Functions

Three documented procedures/functions constitute the functional surface of this package:

• DELETE_DATAPUMP_TABLES — Truncates the Data Pump staging tables used by the migration process. Per the source excerpt, this includes HR_PUMP_BATCH_LINE_USER_KEYS, HR_PUMP_BATCH_LINES, HR_PUMP_BATCH_HEADERS, HR_PUMP_REQUESTS, HR_PUMP_RANGES, and HR_PUMP_BATCH_EXCEPTIONS. The procedure first resolves the PER schema via GET_SCHEMA, then issues dynamic ALTER TABLE ... DISABLE CONSTRAINT statements against foreign keys (for example HR_PUMP_BATCH_LINE_USER_KE_FK1) so that truncation can proceed. Errors during constraint disablement are logged via HR_DM_UTILITY.MESSAGE rather than raised.
• SOURCE_COPY — Handles the source-side extraction of Data Pump content, preparing and moving data from the originating environment.
• DESTINATION_COPY — Handles the destination-side loading of Data Pump content into the target environment.

A helper function, GET_SCHEMA, is also present in the source. It wraps FND_INSTALLATION.GET_APP_INFO to return the Oracle schema name associated with a given product, and it propagates exceptions with RAISE.

Tables Accessed

The package references a broad set of HR and Data Migration tables through APPS synonyms. The HR Data Migration repository tables — HR_DM_MIGRATIONS, HR_DM_MIGRATIONS_S, HR_DM_EXP_IMPS_S, and HR_DM_PHASE_RULES — supply migration definition, sequence, and phase-rule information that governs copy behavior. Organization and location data is read from HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL, HR_LOCATIONS_ALL_TL, and HR_ORGANIZATION_INFORMATION. HR_API_MODULES and BEN_BATCH_PARAMETER provide API/process metadata and batch parameter context. DUAL supports simple lookups, and V$DATABASE is queried for database-level identification during copy operations.

Usage Notes

HR_DM_COPY is invoked internally by the HR Data Migration framework rather than directly by end users. It is most relevant to the hr_pump_batch search context: DELETE_DATAPUMP_TABLES clears the HR_PUMP_BATCH_* staging structures before a fresh Data Pump batch is run, while SOURCE_COPY and DESTINATION_COPY drive the movement of data between environments. Custom code or concurrent programs that extend the HR Data Migration process may call these procedures when resetting staging state or initiating an environment-to-environment transfer. Because the package disables foreign key constraints during truncation, it should be invoked only within a controlled migration window, and callers should verify that constraints are re-established after execution. The package emits progress and diagnostic messages through HR_DM_UTILITY.MESSAGE using ROUT and INFO categories.