Search Results hr_dm_migration_ranges_fk1

Overview

HR.HR_DM_MIGRATION_RANGES is a transactional control table used by the Oracle E-Business Suite Data Migration (DM) framework within the Human Resources (HR) product family. Its documented purpose is to hold the allocated ranges assigned to each slave process during the Download Application/Participant data phase of a migration. When the migration engine parallelizes extraction work, it partitions the source data into discrete sequence ranges and records each allocation in this table, enabling slave workers to process independently without overlap and allowing the framework to track progress, timing, and volume per range.

The object is owned by the HR schema, is registered under FND Design Data as PER.HR_DM_MIGRATION_RANGES, and resides in the APPS_TS_INTERFACE tablespace with a PCT Free of 10. This tablespace placement confirms its role as an interface/staging construct rather than a permanent transactional store; rows are typically transient and exist only for the duration of a migration run. From a heuristic Data Vault modeling perspective, the table is satellite-leaning: it carries descriptive, time-stamped attributes (status, start and end times, row counts) attached to a parent migration phase item, rather than representing an independent business entity or an association between two hubs.

Key Information Stored

The table contains 14 documented columns. The most operationally significant are:

• RANGE_ID — System-generated primary key column and the sole column of the unique index HR_DM_MIGRATION_RANGES_PK. This surrogate key uniquely identifies each allocated range and is the business-key candidate for the table.
• PHASE_ITEM_ID — Foreign key to HR_DM_PHASE_ITEMS.PHASE_ITEM_ID, linking the range to the specific phase item being migrated. This is the principal business relationship in the table and is indexed non-uniquely by HR_DM_MIGRATION_RANGES_FK1.
• STARTING_PROCESS_SEQUENCE and ENDING_PROCESS_SEQUENCE — The initial and end values of the sequence range assigned to a slave process. Together they define the boundary of work owned by one worker.
• STATUS — Current status of the range processing. The value is drawn from the lookup type HR_DM_STATUS, defined in FND_LOOKUP_TYPES, FND_LOOKUP_TYPES_TL, and FND_LOOKUP_VALUES.
• START_TIME and END_TIME — Timestamps marking when range processing began and completed, supporting elapsed-time measurement.
• ROW_COUNT — The number of physical records existing within the sequence range to be migrated, used for load balancing and throughput reporting.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data partitioning conventions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard Who columns providing audit lineage for each row.

Common Use Cases and Queries

Typical usage centers on monitoring, troubleshooting, and reporting on an active or completed migration. A common pattern joins ranges to their parent phase item to report per-phase progress:

SELECT r.RANGE_ID, r.PHASE_ITEM_ID, r.STARTING_PROCESS_SEQUENCE, r.ENDING_PROCESS_SEQUENCE, r.STATUS, r.ROW_COUNT, r.START_TIME, r.END_TIME FROM HR.HR_DM_MIGRATION_RANGES r WHERE r.PHASE_ITEM_ID = :phase_item_id ORDER BY r.STARTING_PROCESS_SEQUENCE;

To identify stalled or long-running ranges, filter on STATUS combined with elapsed time between START_TIME and END_TIME. To measure worker throughput, aggregate ROW_COUNT and compute the difference between END_TIME and START_TIME per range. Decoding STATUS against the HR_DM_STATUS lookup provides readable labels for status dashboards.

Related Objects

• HR.HR_DM_PHASE_ITEMS — Parent table referenced via PHASE_ITEM_ID; defines the migration phase item each range belongs to.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for security group partitioning.
• FND_LOOKUP_TYPES, FND_LOOKUP_TYPES_TL, FND_LOOKUP_VALUES — Define the HR_DM_STATUS lookup codes used by the STATUS column.