Search Results hr_dm_migrations_pk

Overview

HR_DM_MIGRATIONS is a core Human Resources (PER) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the metadata and state information for data migration operations performed through the HR Data Migration (DM) framework. The table is owned by the HR schema and currently holds a VALID status. Each row represents a single migration in progress, meaning that the table acts as the master registry for the discrete migration jobs that move or transform person-related data across database instances, business groups, or security boundaries.

The table is central to the Oracle HR Data Migration utility, which is used during implementations, consolidations, upgrades, and multi-org rollouts to transport workforce data in a controlled, auditable fashion. Because it tracks both source and destination context, the table serves as the control record that phases, requests, and dependent migration processes reference throughout their lifecycle. Applying the Data Vault classification heuristic mined from its foreign-key structure, HR_DM_MIGRATIONS is best modeled as a hub-leaning entity: MIGRATION_ID is a stable business key around which descriptive status, timing, and configuration attributes cluster. Under a Data Vault design this would suggest a hub for the migration identity, with satellites capturing the mutable descriptive fields such as STATUS and MIGRATION_START_DATE.

Key Information Stored

Although the documented physical schema contains 22 columns, the following are the most operationally significant:

• MIGRATION_ID — the surrogate primary key defined by the unique index HR_DM_MIGRATIONS_PK; the canonical business-key candidate for the migration record and the join column used by all dependent tables.
• SOURCE_DATABASE_INSTANCE and DESTINATION_DATABASE_INSTANCE — identify where the migration originates and where it lands, essential for troubleshooting connectivity and data lineage.
• MIGRATION_TYPE — classifies the nature of the migration (for example, full versus incremental, or business-group-scoped transfers), driving which processes execute.
• APPLICATION_ID, BUSINESS_GROUP_ID, and BUSINESS_GROUP_NAME — define the owning application and business group scope; BUSINESS_GROUP_CREATED records whether the target group was instantiated by the migration itself.
• MIGRATION_START_DATE and MIGRATION_END_DATE — bound the execution window and support duration and SLA reporting.
• STATUS and MIGRATION_PROCESS — the real-time state of the run and the process stage currently executing.
• MIGRATION_COUNT and SELECTIVE_MIGRATION_CRITERIA — record volumes processed and any filtering applied to restrict records.
• EFFECTIVE_DATE and ACTIVE_GROUP — date-effective context and grouping flags.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing row-level access through Oracle Application Object Library security.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS who-did-what tracking.

The surrogate MIGRATION_ID is distinct from any business attribute; no alternate unique business key beyond the primary key is documented, so MIGRATION_ID functions as both surrogate and business identifier.

Common Use Cases and Queries

Typical scenarios include monitoring active migrations, auditing completed runs, and reconciling failures. A simple status query is:

• SELECT migration_id, status, migration_start_date, migration_end_date FROM hr.hr_dm_migrations WHERE status = 'IN PROGRESS';
• Join to phases to inspect progress: SELECT m.migration_id, p.phase_name FROM hr.hr_dm_migrations m, hr.hr_dm_phases p WHERE m.migration_id = p.migration_id;
• Reporting duration and throughput by business group uses MIGRATION_START_DATE, MIGRATION_END_DATE, MIGRATION_COUNT, and BUSINESS_GROUP_ID.
• Security-filtered reporting joins SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Oracle HRMS Data Migration APIs and concurrent programs read and write these records, so direct DML should be avoided; use the delivered migration processes instead.

Related Objects

• HR_DM_MIGRATION_REQUESTS — references HR_DM_MIGRATIONS via MIGRATION_ID; stores individual request items.
• HR_DM_PHASES — references HR_DM_MIGRATIONS via MIGRATION_ID; tracks phase-level execution detail.
• GMD_MIGRATION — references HR_DM_MIGRATIONS via MIGRATION_ID, linking process manufacturing migration data.
• FND_SECURITY_GROUPS — referenced by HR_DM_MIGRATIONS.SECURITY_GROUP_ID for row-level security.
• FND_APPLICATION — resolves APPLICATION_ID to an application name.
• HR_ALL_ORGANIZATION_UNITS — resolves BUSINESS_GROUP_ID to the business group definition.