Search Results phase_name_meaning

Overview

HR_DM_PHASES_V is an APPS-owned database view in the Oracle E-Business Suite PER (Human Resources) product module. It exists to support the Data Migration (DM) user interface, specifically the "hr_dm_phases" page, and is documented in ETRM as a VALID object for EBS 12.1.1 and 12.2.2. The view presents phase-level information for HR data migration activities, exposing the run phases associated with a given migration, their processing status, and their timing. Rather than adding business logic of its own, HR_DM_PHASES_V is a presentation-support view: it projects columns from the underlying transactional table and supplements the raw lookup codes with decoded, human-readable meaning through calls to a shared HR utility package. This makes it suitable for concurrent-program monitoring, ad hoc reporting, and any integration that needs to display migration phase states in a legible form rather than raw internal codes.

Underlying Base Objects

The documented referenced base objects are HR_DM_PHASES (referenced through a SYNONYM) and the HR_GENERAL package. HR_DM_PHASES is the transactional table that stores one row per migration phase, keyed by PHASE_ID and linked to its parent run through MIGRATION_ID. HR_DM_PHASES_V is defined as a simple projection over that table: the FROM clause selects only from HR_DM_PHASES (aliased H1). The corresponding table also supplies the who-columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE), which the view passes through unchanged. The second referenced object, HR_GENERAL, is not joined into the result set; it is invoked as a PL/SQL package function, HR_GENERAL.DECODE_LOOKUP, to translate two coded columns into descriptive text. The view therefore depends on the table for its data and on the package for its lookup decoding, with no other base tables involved.

Key Columns

• PHASE_ID — primary key of the migration phase row.
• MIGRATION_ID — foreign key to the parent migration, grouping phases into a single migration run.
• PHASE_NAME — internal code of the phase, drawn from the HR_DM_MIGRATION_PHASE lookup type.
• PHASE_NAME_MEANING — decoded meaning of PHASE_NAME obtained via HR_GENERAL.DECODE_LOOKUP('HR_DM_MIGRATION_PHASE', ...).
• STATUS — status code of the phase, drawn from the HR_DM_STATUS lookup type.
• STATUS_MEANING — decoded meaning of STATUS obtained via HR_GENERAL.DECODE_LOOKUP('HR_DM_STATUS', ...).
• START_TIME and END_TIME — timestamps marking when the phase began and completed.
• LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE — standard EBS audit and accountability columns carried through from HR_DM_PHASES.

Common Use Cases and Queries

The view is most often used to monitor the progress of an HR data migration by phase, and to report on completed, failed, or in-progress phases across migrations. Typical queries select by MIGRATION_ID to inspect a single run, or filter on STATUS_MEANING for exception reporting. Because the view exposes decoded meanings, it is convenient for user-facing reports and for integrations that should not carry their own lookup-decoding logic.

• Phase detail for one migration:

  SELECT phase_id, migration_id, phase_name_meaning, status_meaning,
         start_time, end_time
  FROM   apps.hr_dm_phases_v
  WHERE  migration_id = :p_migration_id
  ORDER  BY phase_id;

• Exception report across migrations:

  SELECT migration_id, phase_name_meaning, status_meaning,
         start_time, end_time
  FROM   apps.hr_dm_phases_v
  WHERE  status_meaning NOT IN ('Complete')
  ORDER  BY migration_id, phase_id;

• Phase duration analysis:

  SELECT migration_id, phase_name_meaning,
         (end_time - start_time) AS duration
  FROM   apps.hr_dm_phases_v
  WHERE  end_time IS NOT NULL;

These patterns rely solely on the columns documented above and remain valid across EBS 12.1.1 and 12.2.2.