Search Results hr_dm_migration_requests_fk1

Overview

HR.HR_DM_MIGRATION_REQUESTS is a transactional interface table in the Oracle EBS HR (Human Resources) schema, registered under FND Design Data as PER.HR_DM_MIGRATION_REQUESTS and delivered in both Oracle EBS 12.1.1 and 12.2.2. The table records the association between a specific migration execution and the concurrent program request that issued it. Each row captures the request id of the corresponding concurrent program as stored in FND_CONCURRENT_REQUESTS, together with the migration, phase, and phase item definitions that govern the run. The table is delivered with a status of VALID and resides in the APPS_TS_INTERFACE tablespace with a PCT Free of 10, reflecting its role as a transient, high-volume interface object driven by Data Migration (DM) concurrent processing rather than a master reference table.

Within the Data Migration framework, HR_DM_MIGRATION_REQUESTS functions as the operative control record: the ENABLED_FLAG and MASTER_SLAVE columns allow the framework to identify the currently active run and to distinguish a master request from its slaves, which is essential when a migration is distributed across multiple concurrent requests or parallel workers. Because the table stores only the request id and the associated migration coordinates — not the migrated business data itself — the heuristic Data Vault classification supplied by the metadata is link: it is best modeled as an associative entity connecting migrations, phases, phase items, and concurrent requests. This is a modeling suggestion rather than a physical constraint.

Key Information Stored

The table contains thirteen documented columns, of which the following are the most significant:

• MIGRATION_REQUEST_ID — NUMBER(15), mandatory, the system-generated surrogate primary key (HR_DM_MIGRATION_REQUESTS_PK). It is the sole unique index/business-key candidate documented; no alternate unique key exists.
• MIGRATION_ID — NUMBER(15), foreign key to HR_DM_MIGRATIONS.MIGRATION_ID; identifies the migration definition being executed.
• PHASE_ID — NUMBER(15), foreign key to HR_DM_PHASES.PHASE_ID; identifies the phase within the migration that the request covers.
• PHASE_ITEM_ID — NUMBER(15), foreign key to HR_DM_PHASE_ITEMS.PHASE_ITEM_ID; identifies the specific unit of work.
• REQUEST_ID — NUMBER(15); the concurrent program request id resolvable against FND_CONCURRENT_REQUESTS, enabling direct linkage to concurrent manager status and output.
• ENABLED_FLAG — VARCHAR2; set to Y for the current run, with all other runs set to N. This is the framework's mechanism for selecting the active migration request.
• MASTER_SLAVE — VARCHAR2; set to M for a master request and S for a slave.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and SECURITY_GROUP_ID (foreign key to FND_SECURITY_GROUPS) provide auditability and Multi-Org security partitioning.

Common Use Cases and Queries

Typical usage centers on monitoring and troubleshooting Data Migration concurrent runs. Administrators identify the active request for a migration, trace a failed concurrent request back to its phase item, or list master and slave requests for a parallel run. Common patterns include:

• Resolving the active run: SELECT MIGRATION_REQUEST_ID, MIGRATION_ID, PHASE_ID, PHASE_ITEM_ID, REQUEST_ID FROM HR.HR_DM_MIGRATION_REQUESTS WHERE ENABLED_FLAG = 'Y' AND MASTER_SLAVE = 'M';
• Joining to FND_CONCURRENT_REQUESTS on REQUEST_ID to obtain phase, status, and completion text for each migration request.
• Grouping by MIGRATION_ID and MASTER_SLAVE to report master/slave distribution and throughput per migration.
• Filtering by SECURITY_GROUP_ID when operating in a Multi-Org environment.

Related Objects

The table participates in a well-defined foreign key network:

• HR_DM_MIGRATIONS — joined on MIGRATION_ID; the parent migration definition.
• HR_DM_PHASES — joined on PHASE_ID; indexed by HR_DM_MIGRATION_REQUESTS_FK1 (non-unique).
• HR_DM_PHASE_ITEMS — joined on PHASE_ITEM_ID; the granular unit of migration work.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs Multi-Org security.
• FND_CONCURRENT_REQUESTS — related logically (not by enforced foreign key) via REQUEST_ID; supplies concurrent program status and diagnostics.

Together these objects form the control and audit backbone of the Oracle HR Data Migration facility, with HR_DM_MIGRATION_REQUESTS acting as the link that binds a migration execution to its concurrent request.