Search Results hr_dm_migration_requests_s

Overview

APPS.HR_DM_MASTER is the coordinating package body for the Oracle E-Business Suite Human Resources Data Migration (HR_DM) subsystem. Its role is to orchestrate the master/slave processing model that drives bulk migration of HR data between source and target environments. Rather than performing extraction, transformation, or loading directly, HR_DM_MASTER manages the lifecycle of a migration run: it initializes controller state, determines whether work remains, spawns concurrent worker requests, monitors slave completion, and reports errors back to the initiating session.

The package is registered as VALID in the APPS schema and is classified under ETRM as OTHER rather than a public API. It is a subsystem-internal controller, not a general-purpose interface, and it operates against the HR_DM_* repository tables that persist migration definitions, ranges, and request state. In the 12.1.1 and 12.2.2 code lines the package body is unchanged in its dependency profile, referencing the same HR_DM component packages (HR_DM_AOL_UP, HR_DM_BUSINESS, HR_DM_CLEANUP, HR_DM_COPY, HR_DM_DELETE, HR_DM_GEN_MAIN, HR_DM_INIT, HR_DM_LIBRARY, HR_DM_MIGRATIONS, HR_DM_UTILITY) plus FND_CONCURRENT, FND_CONC_GLOBAL, FND_REQUEST, HR_GENERAL, V$DATABASE, DUAL, and STANDARD.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions within this package body:

• MASTER — the primary entry point that establishes the master controller context for a migration run.
• CONTROLLER_INIT — initializes controller state prior to submitting or processing migration work.
• MAIN_CONTROLLER — the principal control loop that drives processing across the run until completion.
• SPAWN_SLAVES — submits concurrent slave worker requests, typically through FND_REQUEST, to parallelize migration work.
• SLAVE_STATUS — evaluates the completion state of spawned slave requests.
• WORK_REQUIRED — determines whether additional units of migration work remain to be processed.
• INSERT_REQUEST — records a migration request row, maintaining the audit trail in the HR_DM request tables.
• REPORT_ERROR — surfaces error conditions encountered during controller or slave processing.

These procedures collectively implement a divide-and-conquer controller: WORK_REQUIRED gates entry into the loop, SPAWN_SLAVES launches parallel workers, SLAVE_STATUS and MAIN_CONTROLLER track progress, and REPORT_ERROR captures failures.

Tables Accessed

HR_DM_MASTER reads and writes the migration repository through APPS synonyms:

• HR_DM_MIGRATION_REQUESTS — the core request record for each migration run; INSERT_REQUEST writes here.
• HR_DM_MIGRATION_REQUESTS_S — the sequence backing request identifiers; referenced by the package and directly relevant to the search term hr_dm_migration_requests_s.
• HR_DM_MIGRATIONS — migration definitions that scope what the run processes.
• HR_DM_MIGRATION_RANGES — the range partitioning used to distribute work to slaves.
• HR_DM_PHASE_ITEMS and HR_DM_PHASE_RULES — phase-level item and rule definitions that determine execution order.
• V$DATABASE — queried for database identity, commonly used to validate that the controller is running against the intended target.

Usage Notes

HR_DM_MASTER is not referenced by any database object and is therefore invoked from application-layer entry points rather than from triggers or views. Typical invocation paths are HR Data Migration concurrent programs and the associated HR_DM setup forms, where a user submits a migration run and the controller then spawns slave requests via FND_REQUEST. The package exposes an ETRM classification of OTHER, indicating it should be treated as internal orchestration code; custom code should not call it directly in preference to the supported HR_DM migration interfaces. When diagnosing stalled or failed migrations, administrators should inspect HR_DM_MIGRATION_REQUESTS and its sequence HR_DM_MIGRATION_REQUESTS_S alongside concurrent request status, since these record the controller's state transitions and surfacing of errors via REPORT_ERROR.