Search Results loader_name




Overview
Explore in AI Chat

Overview

HR_DM_PHASE_ITEMS_V is an APPS-owned database view in Oracle E-Business Suite, classified under the PER (Human Resources) product family. It is documented as a "View to support DM UI - hr_dm_phase_items," meaning it serves as a reporting and display layer for the Data Migration (DM) user interface. The Data Migration framework within Oracle HRMS is used to load legacy or external data into EBS through a structured, phased process: batches are defined, groups of tables are identified, and individual phase items represent discrete loading steps executed against specific target tables.

The view consolidates phase-item records with descriptive attributes drawn from several supporting tables, so that the DM UI can present human-readable status, group, table, loader, and batch information without requiring the calling form or report to perform its own joins. Because it exposes resolution of lookup codes into meanings, it is equally useful for ad hoc reporting and for integration routines that monitor migration progress.

Underlying Base Objects

Per the documented metadata, HR_DM_PHASE_ITEMS_V is defined over the following base objects:

Three of the four joins are outer joins (indicated by the (+) operator), which means phase items are returned even when no matching group, batch, or loader row exists. This is deliberate: during migration setup or after cleanup, a phase item may reference identifiers that are not yet fully populated, and the UI must still display the row.

Key Columns

  • PHASE_ITEM_ID, PHASE_ID — primary and foreign identifiers linking a phase item to its parent phase.
  • LOADER_NAME — the loader identifier associated with the phase item; this is the column most commonly used when tracing which loader processed a given item, and it is the join key to HR_DM_TABLES.
  • BATCH_ID, BATCH_NAME — the batch identifier and its resolved name from HR_PUMP_BATCH_HEADERS.
  • GROUP_ID, GROUP_DESCRIPTION — the group identifier and its description from HR_DM_GROUPS.
  • TABLE_NAME, TABLE_DESCRIPTION — the target table being loaded and its descriptive text.
  • STATUS, STATUS_MEANING — the raw status code and its lookup-decoded meaning (HR_DM_STATUS).
  • START_TIME, END_TIME — execution timestamps for the phase item.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.
  • LOADER_DESCRIPTION — descriptive text for the loader, derived from HR_DM_TABLES.

Common Use Cases and Queries

The view is typically queried to monitor migration activity, identify failed or long-running phase items, and confirm which loader handled a given table. A frequent entry point is a search on loader_name:

SELECT phase_item_id, phase_id, loader_name, batch_name,
       group_description, table_name, status, status_meaning,
       start_time, end_time
FROM   apps.hr_dm_phase_items_v
WHERE  loader_name = :loader_name;

To review status distribution across a batch:

SELECT batch_name, status_meaning, COUNT(*)
FROM   apps.hr_dm_phase_items_v
GROUP  BY batch_name, status_meaning;

To find unfinished items:

SELECT phase_item_id, loader_name, table_name, status_meaning, start_time
FROM   apps.hr_dm_phase_items_v
WHERE  end_time IS NULL
ORDER  BY start_time;

Because HR_GENERAL.DECODE_LOOKUP is called for every row, queries returning large result sets should filter on indexed columns such as PHASE_ID, BATCH_ID, or LOADER_NAME to limit the lookup-decoding overhead.