Search Results ame_transaction_types

Overview

AME_MIGRATION_PKG is a PL/SQL package body owned by APPS in Oracle E-Business Suite, shipped as part of the Approvals Management Engine (AME) module. Its documented purpose is to support data migration and conversion activities associated with the AME schema, particularly the movement of users, item class definitions, and item class usages between the AME data model variants used across releases. The package header carries a version identifier consistent with the 12.x code line (120.1), and the body includes an autonomous logging routine that records diagnostic and error information into the AME exceptions log without disturbing the transaction of the calling session. Because the package is classified as OTHER rather than as a public API, it is intended primarily for internal, one-time, or administrative migration operations rather than for routine application integration. In Oracle EBS 12.1.1 and 12.2.2 the package remains available under the APPS schema, and its procedures are typically executed during upgrade, patching, or controlled data-conversion windows.

Key Procedures and Functions

Four procedures are documented for this package:

• MIGRATE_AMEA_USERS — Migrates approval-related user data, aligning AME user records with the current AME configuration so that approval rules continue to resolve to valid approvers after conversion.
• MIGRATE_ITEM_CLASS_USAGES — Populates or realigns the AME item class usage records that associate transactional item classes with the AME transactions in which they participate.
• MIGRATE_ALL — Executes the full set of migration steps in a single invocation, providing an orchestrated entry point for a complete AME data migration.
• MIGRATE_TO_AMEB — Performs the migration toward the AMEB (AME B) data structures, converting item class and usage information into the target model.

The body additionally contains helper routines visible in the source, including LOG_MESSAGE, which inserts into AME_EXCEPTIONS_LOG using an autonomous transaction, and support procedures that assign roles through the UMX registration APIs and grant function security via FND_GRANTS_PKG. These helpers exist to service the migration logic and to record outcomes.

Tables Accessed

The package operates against the following tables, referenced through APPS synonyms:

• AME_ITEM_CLASSES and AME_ITEM_CLASS_USAGES — the primary migration targets, holding item class definitions and their usage mappings.
• AME_CALLING_APPS — identifies the applications that invoke AME transactions, used to scope migration to relevant calling applications.
• AME_EXCEPTIONS_LOG and AME_EXCEPTIONS_LOG_S — the logging table and its sequence, written by the autonomous logging routine.
• FND_USER — source of user identity and user ID values for user migration.
• FND_APPLICATION, FND_CONCURRENT_PROGRAMS, and FND_SECURITY_GROUPS — supporting metadata used to resolve application context, concurrent program registration, and security group assignments.
• AK_WEB_USER_SEC_ATTR_VALUES — web user security attribute values read during user-related migration.
• DUAL — used for sequence retrieval and expression evaluation.

Usage Notes

AME_MIGRATION_PKG is not referenced by any other documented package, which reinforces its role as a standalone administrative utility rather than a reusable API. It is normally invoked from SQL*Plus or a custom concurrent program during upgrade, patch application, or a dedicated data-conversion project, executed by a DBA or technical consultant with APPS privileges. Because MIGRATE_ALL and MIGRATE_TO_AMEB alter approval configuration data, invocations should be preceded by a validated backup and performed within a controlled maintenance window. Error conditions are captured in AME_EXCEPTIONS_LOG for post-run review. The package should not be called from forms or from routine runtime code paths.