Search Results hr_dm_migration_requests




Overview
Explore in AI Chat

Overview

The HR.HR_DM_MIGRATION_REQUESTS table is a core Data Migration (DM) infrastructure object within the Oracle E-Business Suite PER — Human Resources product family. It records the association between a migration request and the concurrent program (identified by its Oracle Applications request ID) that issued it. In practical terms, the table acts as the operational bridge between the Oracle Workflow / Concurrent Manager execution layer and the HR Data Migration framework, allowing each migration run to be traced back to the specific concurrent request that spawned it.

Within the HR Data Migration subsystem, migrations are decomposed into Migrations, Phases, and Phase Items, with each item executed under a concurrent request. This table preserves that request-to-migration lineage. Based on the foreign-key topology mined from the ETRM relationship data — the object references three parent tables (HR_DM_PHASES, HR_DM_MIGRATIONS, HR_DM_PHASE_ITEMS) and is referenced by none — the heuristic Data Vault classification is a link table. This classification is a modeling suggestion: the table connects migration entities to execution requests rather than describing a single business entity.

Key Information Stored

The table contains 13 documented columns under the HR schema in ETRM 12.2.2. The most significant are:

The surrogate key MIGRATION_REQUEST_ID should be distinguished from the natural identifiers (REQUEST_ID, PHASE_ITEM_ID) that carry business meaning. No additional unique business-key index beyond the primary key is documented.

Common Use Cases and Queries

Typical scenarios include tracing which concurrent request executed a given migration phase item, diagnosing failed or re-run migrations, and reporting migration throughput by phase.

  • Trace a concurrent request to its migration: 
    SELECT mr.migration_request_id, mr.request_id, m.migration_name, p.phase_name
FROM   hr.hr_dm_migration_requests mr,
       hr.hr_dm_migrations m,
       hr.hr_dm_phases p
WHERE  mr.migration_id = m.migration_id
AND    mr.phase_id = p.phase_id
AND    mr.request_id = :req_id;
  • List all requests for a migration: filter by MIGRATION_ID and ENABLED_FLAG = 'Y'.
  • Join to FND_CONCURRENT_REQUESTS on REQUEST_ID to obtain execution status, completion date, and output.
  • Audit re-executions by counting records per PHASE_ITEM_ID.

Related Objects

  • HR_DM_MIGRATIONS — parent migration definition, joined via MIGRATION_ID.
  • HR_DM_PHASES — phase definition, joined via PHASE_ID.
  • HR_DM_PHASE_ITEMS — phase item executed, joined via PHASE_ITEM_ID.
  • FND_SECURITY_GROUPS — security group partitioning, joined via SECURITY_GROUP_ID.
  • FND_CONCURRENT_REQUESTS — concurrent program execution metadata, joined via REQUEST_ID.
  • FND_CONCURRENT_PROGRAMS — the issuing program definition.

Together these objects form the HR Data Migration execution graph, with HR_DM_MIGRATION_REQUESTS serving as the link layer that binds migration structure to Oracle Concurrent Manager execution history.