Search Results set_active




Overview

HR_DM_DELETE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle HR Data Migration (HR_DM) subsystem, a set of utilities used to migrate, transform, and load human resources and related setup data between environments or from legacy sources. The package is classified in the ETRM metadata as "OTHER," indicating it is not a published public API but rather an internal utility used by the HR Data Migration framework. Its documented status is VALID, and it exposes four documented program units: MAIN, SET_ACTIVE, PRE_DELETE_PROCESS, and DEL_FND_INFO.

Functionally, HR_DM_DELETE is responsible for cleaning up data generated or staged by HR data migration activity. This includes removal of migration definitions, migration ranges, table groupings, phase items, and associated security and lookup artifacts. By centralizing these deletion operations, the package ensures that a migration configuration can be reset or retired without leaving orphan rows spanning the HR_DM and FND tables.

Key Procedures and Functions

The ETRM metadata documents four program units. Parameter lists are not published and should be confirmed against the actual source.

  • MAIN — The primary driver procedure. It likely orchestrates the overall deletion flow, invoking the supporting routines in the correct sequence so that dependent rows are removed before their parents.
  • SET_ACTIVE — Manages the active/inactive state associated with the deletion context. It is presumably used to flag a migration or related record so that it is eligible for, or protected from, deletion.
  • PRE_DELETE_PROCESS — Performs prerequisite processing before the actual deletion. This typically includes validation, dependency checks, and any staging or archiving required so that deletion does not violate referential integrity.
  • DEL_FND_INFO — Handles removal of FND-related information, such as lookup types, lookup values, responsibility, security group, and user references tied to the migration. This isolates the deletion of foundation-layer records into a dedicated routine.

Tables Accessed

The package reads and writes a broad set of application and foundation tables via APPS synonyms. The HR_DM tables — HR_DM_MIGRATIONS, HR_DM_MIGRATION_RANGES, HR_DM_APPLICATION_GROUPS, HR_DM_PHASE_ITEMS, HR_DM_TABLES, and HR_DM_TABLE_GROUPINGS — form the core migration configuration and staging data being removed. The FND tables — FND_APPLICATION, FND_LOOKUP_TYPES, FND_LOOKUP_VALUES, FND_RESPONSIBILITY, FND_SECURITY_GROUPS, and FND_USER — are accessed by DEL_FND_INFO to clean up related foundation records. DUAL is used for trivial SQL operations, DBMS_PIPE supports inter-process communication, and UTL_FILE allows the package to write or read log files. As the metadata notes, HR_DM_DELETE itself references HR_DM_UTILITY and STANDARD, and is referenced by HR_DM_DELETE and HR_DM_MASTER, the latter being the master orchestration package that invokes this deletion logic.

Usage Notes

HR_DM_DELETE is not intended for direct invocation by end users. It is normally called from the HR Data Migration master flow, specifically HR_DM_MASTER, and from within the HR_DM_DELETE package body itself as part of internal recursion or helper calls. In EBS 12.1.1 and 12.2.2 it may be exercised through Data Migration forms, concurrent programs, or the HR_DM administration console rather than a standalone screen. Customizations should avoid calling the procedures directly; instead, use the supported HR_DM_MASTER entry point so that precondition checks and cleanup sequencing are honored. Because the package deletes migration, table grouping, and FND lookup/responsibility data, it should be run with appropriate backups and during planned maintenance windows. Reviewing HR_DM_UTILITY and HR_DM_MASTER dependencies is recommended before extending or wrapping this package in custom code.