Search Results hr_dm_copy




Overview
Explore in AI Chat

Overview

APPS.HR_DM_COPY is a PL/SQL package belonging to the Oracle Human Resources Data Migrator (HR_DM) infrastructure in Oracle E-Business Suite. Its declared purpose is to support the Copy phase of a data migration performed between a source database and a destination database. The package is defined with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking user rather than the package owner, a common convention for packages that operate on session-specific or staging objects.

The package is not an end-user business component. It is a technical utility within the migration toolchain, responsible for staging migration metadata (data migrator API modules and migration definitions) into export views in the source database and for materializing that metadata into the destination database after transport. It also provides the housekeeping routine that clears Oracle Data Pump staging tables before a migration run. Within the documented object set it is referenced by two other packages, confirming its role as a shared utility in the HR_DM migration flow.

Key Procedures and Functions

  • DELETE_DATAPUMP_TABLES — Truncates the Data Pump staging tables used by the migration: HR_PUMP_BATCH_HEADER, HR_PUMP_BATCH_LINES, HR_PUMP_REQUESTS, HR_PUMP_RANGES, and HR_PUMP_BATCH_EXCEPTIONS. This procedure performs no inserts or updates; it exists to guarantee that each migration cycle begins with empty pump tables, preventing residual rows from a prior run from contaminating the current extract. This is the procedure most commonly located by the search term delete_datapump_tables.
  • SOURCE_COPY — Executes the source-side portion of the Copy phase. It inserts data migrator package rows from HR_API_MODULES into the HR_DM_EXP_API_MODULES_V view, filtered according to HR_DM_EXP_IMP, and inserts the current migration row from HR_DM_MIGRATIONS into the HR_DM_EXP_MIGRATIONS_V view. It accepts input parameters identifying the current migration and the last migration date; the migration identifier is the primary key of HR_DM_MIGRATIONS. It is called by the main controller process in the source database.
  • DESTINATION_COPY — Executes the destination-side portion of the Copy phase. It first invokes DELETE_DATAPUMP_TABLES to truncate the Data Pump tables at the destination, then removes existing data migrator rows from HR_API_MODULES where API_MODULE_TYPE = 'DM', and finally repopulates HR_API_MODULES from HR_DM_EXP_API_MODULES_V and HR_DM_MIGRATIONS from HR_DM_EXP_MIGRATIONS_V. This ordering ensures the destination reflects exactly the module and migration metadata exported from the source.

Tables Accessed

The package reads and writes migration control and HR reference data. HR_API_MODULES is the central metadata store for API module registrations and is both queried and modified during the copy; HR_DM_MIGRATIONS and its sequence HR_DM_MIGRATIONS_S hold migration definitions and identifiers; HR_DM_EXP_IMPS_S supports the export implementation records; and HR_DM_PHASE_RULES governs phase behavior during the migration. organization and location information is drawn from HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL, HR_LOCATIONS_ALL_TL, and HR_ORGANIZATION_INFORMATION, while BEN_BATCH_PARAMETER supplies benefits batch context. DUAL is used for trivial single-row evaluation, and V$DATABASE is consulted to identify the current database, which is essential when the same code must behave differently on the source versus the destination instance.

Usage Notes

HR_DM_COPY is invoked programmatically rather than from a standard Oracle Forms interface. SOURCE_COPY is driven by the main migration controller on the source database, and DESTINATION_COPY is driven by the corresponding controller on the destination database after the Data Pump export files have been transported and imported. DELETE_DATAPUMP_TABLES may be called directly by administrators or by custom migration scripts when the pump tables must be cleared independently, for example after a failed or aborted run.

Because the package manipulates HR_API_MODULES, which underpins seeded HR APIs, any custom invocation of DESTINATION_COPY carries inherent risk: the procedure deletes all rows with API_MODULE_TYPE = 'DM' before reinserting from the export views. Customizations should avoid modifying this package and should instead use the supported Data Migrator concurrent programs and controllers. When troubleshooting migrations in EBS 12.1.1 or 12.2.2, verify that SOURCE_COPY completed successfully before transport; otherwise the destination views will lack the migration and API module rows required by DESTINATION_COPY. Note that the package header references an early file version (perdmcp.pkh), indicating a long-standing, stable component of the HR data migration architecture.