Search Results migrate_amea_users

Overview

AME_MIGRATION_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It is classified under the Application Management Exchange (AME) family of utilities and serves as a data migration engine for the Oracle Approvals Management (AME) framework. Its business function is to relocate or transform approval-management configuration and transactional metadata — including user-approver associations, item class definitions, and item class usage records — between the legacy AMEA data model and the current AMEB repository used by AME in Release 12.1.1 and 12.2.2.

The package is therefore an upgrade and conversion tool. During the transition from earlier AME rules structures to the redesigned AME approval model, organizations require a controlled mechanism to move existing approver definitions, item class hierarchies, and usage mappings without manual re-entry. AME_MIGRATION_PKG centralizes that logic so the conversion executes consistently across environments, and it records exceptions for rows that cannot be migrated cleanly.

Key Procedures and Functions

The ETRM metadata documents four callable programs:

• MIGRATE_ALL — The master driver routine. It sequences the full migration by invoking the individual migration steps in the required order, providing a single entry point for a complete conversion run.
• MIGRATE_AMEA_USERS — Migrates user-level approver configuration and user security attribute data from the legacy AMEA tables into the AME structures, reconciling FND_USER records against AME calling applications.
• MIGRATE_ITEM_CLASS_USAGES — Migrates item class usage associations, mapping which item classes are used by which calling application and transaction type so that approval rule evaluation continues to function after conversion.
• MIGRATE_TO_AMEB — Performs the core transfer of item class and related AME configuration data into the AMEB model, forming the central step of the AMEA-to-AMEB transition.

No parameter signatures are published in the ETRM extract; callers should not assume argument lists and must consult the package specification in the database.

Tables Accessed

The package reads and writes the following documented objects, resolved through APPS synonyms:

• AME_ITEM_CLASSES and AME_ITEM_CLASS_USAGES — Source and target of item class and usage migration.
• AME_CALLING_APPS — Identifies registered AME calling applications for which configuration is migrated.
• AME_EXCEPTIONS_LOG and AME_EXCEPTIONS_LOG_S — Capture rows that fail migration, supporting error diagnosis and re-processing.
• AK_WEB_USER_SEC_ATTR_VALUES — Supplies web user security attribute values used when converting user-level approver data.
• FND_USER, FND_APPLICATION, FND_SECURITY_GROUPS, FND_CONCURRENT_PROGRAMS — Standard EBS foundation tables used for user identity, application registration, security group scoping, and concurrent program registration.
• DUAL — Used for single-row selection and validation logic.

Usage Notes

MIGRATE_ALL is typically invoked during AME upgrade or configuration-conversion activity rather than in routine transaction processing. Because the package logs failures to AME_EXCEPTIONS_LOG, DBAs and AME administrators should review that log after each run and correct source data before re-executing individual migration routines. The zero inbound package references reported by ETRM indicate the package is not called by other PL/SQL APIs; it is driven externally, generally from a concurrent program registered in FND_CONCURRENT_PROGRAMS, from SQL*Plus during controlled cutover windows, or from custom conversion scripts. Environments should be backed up and the migration run in a non-production instance first, since the routines perform direct DML against live AME configuration tables.