Results for “slave_status”

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

Overview

APPS.BEN_DM_MASTER is the top-level orchestration package for Oracle Advanced Benefits (BEN) data migration within Oracle E-Business Suite releases 12.1.1 and 12.2.2. The package implements the master controller that drives the migration of benefit configuration and enrollment data from external sources into the BEN schema through a phased, restartable process. It coordinates the work of subordinate, or "slave," migration processes by evaluating phase rules, determining whether work is required for a given phase, dispatching slave workers, and recording status and errors throughout the migration lifecycle.

The package is classified as an OTHER API rather than a public business API, which indicates that it is an internal infrastructure component invoked by the BEN data migration framework rather than by external integrations or end users directly. Its responsibilities center on phase sequencing, concurrency management, restart handling, and error capture during large migration runs.

Key Procedures and Functions

• MASTER — The primary entry point for executing a migration phase. It accepts the current and previous phase identifiers together with the migration data record, and drives the logic required to complete that phase.
• SPAWN_SLAVES — Initiates the slave processes that perform the parallel work associated with the current migration phase, using the migration data record to determine which workers to start.
• REPORT_ERROR — Records an error against a specific migration, capturing the current phase, the error message, and the stage at which the failure occurred.
• SLAVE_STATUS — Returns the status of slave processing for the given phase and migration record, allowing the master to determine whether subordinate work has completed.
• WORK_REQUIRED — Evaluates whether any work remains to be performed for the current phase, enabling the controller to skip phases that are already complete or not applicable.
• MAIN_CONTROLLER — The principal concurrent-program entry point. It receives the migration identifier and name, input and output file locations, migration type, optional restart migration identifier, and a flag controlling generation behavior, and returns the standard concurrent request error buffer and return code.
• INSERT_REQUEST — Creates a migration request record, associating a request identifier with a migration, phase, and optionally a phase item, and distinguishing between master and slave requests.
• CONTROLLER_INIT — Initializes the migration data record and request data for a given migration identifier, preparing the controller's in-memory state before phase execution begins.

Tables Accessed

• BEN_DM_MIGRATIONS / BEN_DM_MIGRATIONS_S — Store the migration definitions and their translation rows; the controller reads configuration and writes progress and status for each migration run.
• BEN_DM_MIGRATION_REQUESTS / BEN_DM_MIGRATION_REQUESTS_S — Hold the request-level records created by INSERT_REQUEST, linking concurrent requests to migrations, phases, and phase items.
• BEN_DM_PHASE_ITEMS — Define the individual items belonging to each migration phase, used to determine work scope and associate requests with specific phase items.
• HR_DM_PHASE_RULES — Supply the rules that govern phase sequencing and progression, which the controller consults via WORK_REQUIRED and SLAVE_STATUS.
• DUAL — Used for singleton queries and PL/SQL expression evaluation.

Usage Notes

BEN_DM_MASTER is not intended for direct invocation by end users. It is typically launched through the BEN data migration concurrent programs, where MAIN_CONTROLLER serves as the executable entry point and the standard concurrent manager passes the migration parameters and receives errbuf and retcode. The package supports restartable migrations through the restart migration identifier, allowing failed or interrupted runs to resume without reprocessing completed phases. Because it is referenced by no other documented packages, it sits at the top of the migration call stack and depends on related components such as BEN_DM_UTILITY for shared record types and helper logic. Custom code should not call these procedures directly; integrations should instead use the supported concurrent program interface, which manages phase rules, slave spawning, and error reporting consistently.