Search Results master_slave_meaning

Overview

The APPS.HR_DM_MIGRATION_REQUESTS_V view is a reporting and integration object within the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exists to support the Data Migration (DM) user interface, exposing the contents of the hr_dm_migration_requests entity in a denormalized, user-readable form. The underlying HR_DM_MIGRATION_REQUESTS table stores the association between a migration request and the concurrent request that performs the actual data movement work; the view enriches that association with meaningful status, phase, and program descriptions sourced from the concurrent manager tables and the FND lookup repository.

Because the conversion of concurrency identifiers into human-readable meanings is handled inside the view, it is particularly valuable for administrators, technical consultants, and integration developers who need to monitor or report on HR data migration activity without performing multiple joins manually. In ETRM terms, the view is documented as VALID and is owned by APPS in both the 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The documented ETRM metadata identifies five referenced base objects:

• HR_DM_MIGRATION_REQUESTS (SYNONYM) — the primary driving table alias H1, holding migration request, migration, phase, phase item, request, enabled flag, and master/slave attributes.
• FND_CONCURRENT_REQUESTS (SYNONYM) — alias F1, supplying the actual start date, actual completion date, status code, and phase code of the concurrent request.
• FND_CONCURRENT_PROGRAMS (SYNONYM) — alias F2, used to link the concurrent program definition behind the request.
• FND_CONCURRENT_PROGRAMS_VL (VIEW) — alias F3, providing the translated program description exposed as PROGRAM_NAME.
• FND_LOOKUP_VALUES_VL (VIEW) — aliases LV1 and LV2, resolving PHASE_CODE against lookup type CP_PHASE_CODE and STATUS_CODE against CP_STATUS_CODE.

The join condition F1.CONCURRENT_PROGRAM_ID = F2.CONCURRENT_PROGRAM_ID (and F2.CONCURRENT_PROGRAM_ID = F3.CONCURRENT_PROGRAM_ID) is the mechanism by which the concurrent program is resolved — this is the point of interest behind the search term "concurrent_program_id". The view filters on H1.PHASE_ID IS NOT NULL, so only migration requests that have progressed to an identified phase are surfaced.

Key Columns

• MIGRATION_REQUEST_ID — unique identifier for the migration request record.
• MIGRATION_ID / PHASE_ID / PHASE_ITEM_ID — the migration definition and phase/phase-item context to which the request belongs.
• REQUEST_ID — the FND_CONCURRENT_REQUESTS identifier of the executing concurrent request.
• ENABLED_FLAG / MASTER_SLAVE / MASTER_SLAVE_MEANING — the enabled indicator and a decoded MASTER/SLAVE designation.
• START_DATE / END_DATE — actual start and completion timestamps from the concurrent request.
• STATUS / STATUS_MEANING — status code plus a concatenated phase/status meaning string.
• PROGRAM_NAME — the translatable description of the concurrent program.
• MIGRATION_CODE — the migration identifier/code exposed for reporting.

Common Use Cases and Queries

Typical scenarios include monitoring active HR migration requests, reconciling completed requests by program, and building dashboards filtered by status. A simple query lists the most recent requests:

• SELECT migration_request_id, migration_id, program_name, status_meaning, start_date, end_date FROM apps.hr_dm_migration_requests_v WHERE status IN ('R','P') ORDER BY start_date DESC;
• SELECT migration_id, migration_code, program_name, COUNT(*) FROM apps.hr_dm_migration_requests_v GROUP BY migration_id, migration_code, program_name;
• SELECT * FROM apps.hr_dm_migration_requests_v WHERE start_date >= TRUNC(SYSDATE)-7;

Because the view already joins to FND_CONCURRENT_PROGRAMS via concurrent_program_id and to the lookup views, custom reports can rely on PROGRAM_NAME and STATUS_MEANING directly rather than re-implementing those joins.