Search Results get_func_asg

Overview

APPS.HR_DM_LIBRARY is a technical utility package within the Oracle E-Business Suite Human Resources data migration framework (the HR_DM schema family). Its role is to support the migration of configuration and transactional data from a source database instance to a destination database instance by generating, resolving, and validating the metadata required to move rows correctly. It is not a user-facing business package; it is an internal engine that other migration packages call to inspect table structures, resolve primary and foreign key relationships, generate PL/SQL code fragments, build column lists, and manage the delete-tracking ("DT delete") bookkeeping that guards a migration run.

The package is declared AUTHID CURRENT_USER and carries a long-standing header date (2003), indicating that its design has been stable across many EBS releases. It operates against the APPS schema and relies on APPS synonyms for its table access.

Key Procedures and Functions

The 30 documented entry points fall into several functional clusters:

• Formatting and version helpers: INDENT returns the requested number of blank spaces on a newline for indenting generated code; GET_GENERATOR_VERSION and GET_PACKAGE_VERSION expose version identifiers used to validate that generated artifacts match the running library.
• Table and column introspection: GET_TABLE_INFO, GET_TABLE_INFO, POPULATE_COLUMNS_LIST, POPULATE_PK_COLUMNS_LIST, POPULATE_HIERARCHY_COLS_LIST, and GET_COLS_LIST_WO_PK_COLS build working lists of columns for a table, distinguishing primary key columns from the remainder.
• Foreign key analysis: CHECK_COL_FOR_FK_ON_AOL and POPULATE_FK_TO_AOL_COLS_INFO determine whether a column participates in a foreign key that maps to AOL (Application Object Library) columns, which drives how lookup and reference data are migrated.
• Key resolution: GET_RESOLVED_PK, INS_RESOLVE_PKS, and the table HR_DM_RESOLVE_PKS support mapping surrogate keys from the source to the destination, ensuring migrated child rows point to the correct parent after re-keying.
• Delete tracking (the subject of the "ins_dt_delete" search): INS_DT_DELETE inserts a row into the HR_DM_DT_DELETES tracking structure; CHK_ROW_IN_DT_DELETE, CHK_ROW_IN_DT_DELETE_1_PKCOL, and CHK_ROW_IN_DT_DELETE_2_PKCOL test whether a given row (identified by one or two primary key columns) is already recorded as deleted or scheduled for deletion. These routines prevent duplicate deletes and reconcile destination rows that no longer exist in the source.
• Code generation and expression building: CONV_LIST_TO_TEXT, GET_NVL_ARGUEMENT, GET_FUNC_ASG, and GET_FUNC_ASG_WITH_DEV_KEY assemble assignment expressions and comma-separated lists emitted into generated PL/SQL.

Tables Accessed

The package reads and writes migration control tables through APPS synonyms: HR_DM_MIGRATIONS (the migration run header), HR_DM_PHASES and HR_DM_PHASE_ITEMS (phase sequencing), HR_DM_TABLES (the table inventory), HR_DM_HIERARCHIES and HR_DM_HIERARCHIES_S (parent/child relationships), and HR_DM_RESOLVE_PKS and HR_DM_RESOLVE_PKS_S (key resolution state). Delete tracking is persisted in HR_DM_DT_DELETES and HR_DM_DT_DELETES_S. Dictionary access uses ALL_CONSTRAINTS and ALL_CONS_COLUMNS for key discovery, DBMS_SQL for dynamic statement execution, AD_DDL for DDL generation, and FND_ORACLE_USERID for schema/user context.

Usage Notes

HR_DM_LIBRARY is invoked indirectly rather than from a user form. It is called by the HR Data Migration runtime and by the 14 other packages that reference it, typically during the generation and execution phases of a migration run. Custom extensions that move HR data between instances should reuse the resolve-PK and DT-delete routines rather than reimplementing them, since INS_DT_DELETE and the CHK_ROW_IN_DT_DELETE_* checks maintain the integrity of the delete reconciliation process. Because the package executes dynamic SQL and DDL under AUTHID CURRENT_USER, callers must connect as APPS with the standard EBS initialization in effect.