Results for “ben_dm_master”

34 results




Overview
Explore in AI Chat

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

Overview

The APPS.BEN_DM_MASTER package body is a core component of the Oracle EBS Advanced Benefits (BEN) data migration framework, introduced and maintained across the 12.1.1 and 12.2.2 releases. Its principal business function is to orchestrate the master control process that drives the migration of legacy benefits data into the Oracle Advanced Benefits tables. The data migration (DM) infrastructure allows implementers to transfer compensation objects, plans, eligibility profiles, and enrollment data from external or legacy sources into BEN using a phased, restartable model. BEN_DM_MASTER acts as the central controller in this framework: it validates the defined migration, initializes runtime context, coordinates parallel worker processes, tracks phase and slave execution status, and reports errors back to the migration request tables. The package is not a business-facing API intended for ad-hoc invocation; rather, it is the internal engine invoked by the Benefits Data Migration concurrent programs. The header comment (RCS revision 120.0) dates the source to 2006, and the shipped flag (noship) indicates it forms part of the proprietary internal codebase rather than a customer-facing seeded object.

Key Procedures and Functions

The documented package exposes eight procedures and functions, all oriented around the master controller lifecycle. Their responsibilities are as follows:

  • CONTROLLER_INIT — Performs initialization for a migration run. It verifies that migration data exists in BEN_DM_MIGRATIONS, marks prior entries in BEN_DM_MIGRATION_REQUESTS as inactive, seeds the migration data record, increments the migration count, validates the migration definition, and sets the migration status to started.
  • MAIN_CONTROLLER — Serves as the principal driver that sequences the migration phases and invokes the appropriate subordinate logic for each phase.
  • MASTER — Acts as the top-level entry point coordinating the overall migration execution.
  • SPAWN_SLAVES — Creates and launches parallel slave processes so that migration work can be distributed and executed concurrently.
  • SLAVE_STATUS — Reports the current execution status of the spawned slave processes, supporting the controller's progress tracking.
  • WORK_REQUIRED — Determines whether additional units of migration work remain to be processed, enabling the controller to decide whether to continue.
  • INSERT_REQUEST — Inserts a migration request record, registering the run within the migration request tracking tables.
  • REPORT_ERROR — Captures and records errors encountered during migration processing for later review and remediation.

Tables Accessed

The package reads and writes several BEN and HR tables through APPS synonyms, each serving a defined role in the migration control model.

  • BEN_DM_MIGRATIONS and BEN_DM_MIGRATIONS_S — Store the master migration definitions and their translated/secure variants; CONTROLLER_INIT validates data against them.
  • BEN_DM_MIGRATION_REQUESTS and BEN_DM_MIGRATION_REQUESTS_S — Hold individual migration request records; prior requests are deactivated and new requests are inserted via INSERT_REQUEST.
  • BEN_DM_PHASE_ITEMS — Defines the phase-level items that the controller must process as it advances the migration.
  • HR_DM_PHASE_RULES — Supplies the rules governing phase sequencing and applicability, which the master controller consults to decide work allocation.
  • DUAL — Used for simple singleton queries and status checks.

Usage Notes

BEN_DM_MASTER is invoked indirectly, not directly by end users. It runs when the Benefits Data Migration concurrent programs are submitted, and it may also be called programmatically by related BEN_DM transport packages that depend on its controller routines. The package is described as referenced by zero other documented packages in the ETRM metadata, reflecting its position as a controller-level object. Its parallel architecture (SPAWN_SLAVES, SLAVE_STATUS, WORK_REQUIRED) means it is designed for high-volume migrations where concurrent workers process data in phases tracked by BEN_DM_PHASE_ITEMS and HR_DM_PHASE_RULES. In 12.1.1 and 12.2.2, administrators trigger migration through standard concurrent request submission; the package handles initialization, phase control, request registration, and error reporting on their behalf. Custom code should treat BEN_DM_MASTER as an internal implementation detail and avoid calling its procedures directly, since its interface and behavior are not guaranteed across releases.