Search Results hr_dm_migration_type




Overview
Explore in AI Chat

Overview

APPS.HR_DM_MIGRATIONS_V is a reporting and inquiry view exposed in the APPS schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the header-level records of the Human Resources Data Migration (HR_DM) framework, which is used to move data extract definitions, business group content, and related configuration between source and destination database instances during implementation, cloning, consolidation, or upgrade activities. The view consolidates migration metadata maintained in the base migration tables with descriptive lookup meanings and the latest concurrent request information, allowing administrators and integrators to track migration activities without joining multiple objects manually.

The identifier most commonly used to query this view is migration_id, which uniquely identifies a single migration event and serves as the primary correlation key across the view and its underlying objects. The view is especially relevant to functional consultants and technical teams performing business group data migration in multi-organization HRMS deployments.

Underlying Base Objects

The ETRM metadata documents four referenced base objects:

  • HR_DM_MIGRATIONS (SYNONYM) — the primary driving table, aliased h1, supplying migration header attributes such as source and destination instance, migration type, business group, status, dates, and audit columns.
  • HR_DM_MIGRATION_REQUESTS (SYNONYM) — aliased h2, providing the concurrent request_id associated with the migration. It is outer-joined to the header on migration_id, filtered to the master record (master_slave = 'M'), and further restricted to the maximum request_id for each migration via a correlated subquery.
  • FND_APPLICATION_VL (VIEW) — aliased f1, supplying the application_name for the application_id recorded on the migration header.
  • HR_GENERAL (PACKAGE) — invoked through HR_GENERAL.DECODE_LOOKUP to translate the status and migration_type codes into descriptive meanings.

The outer join and MAX(request_id) logic ensure that exactly one row is returned per migration, reflecting the most recent master request rather than every historical submission.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing migration history for a business group, monitoring in-progress migrations, and retrieving the request_id for concurrent program troubleshooting.

  • Inspect a specific migration: SELECT migration_id, source_database_instance, destination_database_instance, status_meaning, migration_start_date, migration_end_date FROM apps.hr_dm_migrations_v WHERE migration_id = :migration_id;
  • List migrations by business group and status: SELECT migration_id, business_group_name, migration_type_meaning, status_meaning FROM apps.hr_dm_migrations_v WHERE business_group_id = :p_bg_id AND status <> 'COMPLETE' ORDER BY creation_date DESC;
  • Obtain the latest concurrent request for reporting: SELECT migration_id, request_id, application_name FROM apps.hr_dm_migrations_v WHERE migration_id = :migration_id;
  • Audit recent activity: SELECT migration_id, created_by, creation_date, status_meaning FROM apps.hr_dm_migrations_v WHERE creation_date > SYSDATE - 30;

Because the view resolves lookup meanings and the latest master request internally, it is well suited to custom reports, BLOCK-based forms, and integration extracts that require a single-row-per-migration representation without direct joins to HR_DM_MIGRATION_REQUESTS.