Results for “hr_dm_migration_summary_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The HR_DM_MIGRATION_SUMMARY_V view is a reporting object owned by the APPS schema within the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM with a status of VALID and a concise description: "View to support DM UI." In this context, "DM" refers to the Data Migration / Data Mover framework used by Oracle HRMS to move legacy or third-party HR data into the EBS repository. The view aggregates progress information across the phases, phase items, migration ranges, and concurrent request executions that together constitute a data migration run.

Rather than exposing raw transaction rows, the view presents a consolidated, phase-oriented status summary. Each row corresponds to one phase (identified by PHASE_ID) and reports counts of phase items and migration ranges at each workflow state, along with counts of completed concurrent requests. This makes the view a natural source for dashboards and forms within the DM user interface, where administrators monitor how far a migration has progressed and whether anything is stalled, errored, or successful.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through APPS synonyms:

• HR_DM_PHASES — the driving table, supplying PHASE_ID, PHASE_NAME, and MIGRATION_ID.
• HR_DM_PHASE_ITEMS — the individual work units within each phase, joined on PHASE_ID and filtered by STATUS.
• HR_DM_MIGRATION_RANGES — the data ranges processed during migration, joined via PHASE_ITEM_ID to the range phase.
• HR_DM_MIGRATION_REQUESTS — request records associated with phases, keyed by PHASE_ID and REQUEST_ID.
• FND_CONCURRENT_REQUESTS — the standard concurrent manager request table, joined on REQUEST_ID to determine completion.

The view correlates phase items and migration ranges by looking up the corresponding "R" (range) phase for the same MIGRATION_ID, a pattern visible in the nested scalar subqueries of the view text.

Key Columns

The most important exposed columns are:

• PHASE_ID — the primary correlating key; the user search term "phase_id" maps directly to this column.
• PI_C, PI_NS, PI_S, PI_E — counts of phase items in Completed, Not Started, Started, and Error statuses respectively.
• RNG_C, RNG_NS, RNG_S, RNG_E — counts of migration ranges in Completed, Not Started, Started, and Error statuses, restricted to relevant phases such as 'DP', 'UP', and 'D'.
• Concurrent request counts — derived from HR_DM_MIGRATION_REQUESTS joined to FND_CONCURRENT_REQUESTS where STATUS_CODE = 'C', indicating successfully completed executions.

Common Use Cases and Queries

Typical uses include migration progress dashboards, exception reporting when error counts are non-zero, and reconciliation of phase items against range activity. A simple query isolating a specific phase would be:

• SELECT phase_id, pi_c, pi_ns, pi_s, pi_e, rng_c, rng_s, rng_e FROM apps.hr_dm_migration_summary_v WHERE phase_id = :phase_id;
• SELECT * FROM apps.hr_dm_migration_summary_v WHERE pi_e > 0 OR rng_e > 0; — to surface migrations with errors.
• SELECT phase_id, pi_c, rng_c FROM apps.hr_dm_migration_summary_v ORDER BY phase_id; — for overall completion summaries.

Because the view delegates aggregation to scalar subqueries, performance depends on indexed access to PHASE_ID on the underlying DM tables; queries should therefore always filter or join on PHASE_ID where practicable.