Search Results migrate_parallel_config

Overview

The APPS.AME_MIGRATE_PARALLEL_CONFIG package is an Oracle Applications migration utility within the Approvals Management Engine (AME) module. It exists to relocate or consolidate AME configuration metadata between the various parallel data models that were introduced and refined across releases of the E-Business Suite. AME stores approval rules, action types, and action parameters through a hierarchy of configuration tables; when those structures are reorganized (for example, when action type configuration is split from usage rows, or when approval group configuration migrates to a revised schema), a mechanism is required to copy the existing definitions forward without manual table manipulation. This package provides that mechanism through a small, focused set of migration entry points.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling session rather than the definer, so it must be invoked with sufficient APPS-level access to the underlying AME tables. The header indicates AME development ownership and a provenance traceable to the 12.0 code line, with the object continuing to be documented in the 12.2.2 ETRM repository as an OTHER-classified API under the AME product family.

Key Procedures and Functions

The package exposes three documented procedures. Each follows the standard concurrent-program interface, returning an error buffer and a completion code so it can be registered and monitored as a concurrent request.

• MIGRATE_APPROVAL_GROUP_CONFIG — Migrates approval group configuration data into the current schema representation. Approval groups define the sets of approvers available to AME rules; this procedure propagates their stored configuration.
• MIGRATE_ACTION_TYPE_CONFIG — Migrates action type configuration records. Action types describe the behaviors AME can perform during an approval process (for example, sending notifications or invoking function-based actions), and their configuration must be present in the target structures for rules to execute correctly.
• MIGRATE_PARALLEL_CONFIG — The procedure most directly associated with the search term. It performs the parallel configuration migration, orchestrating the movement of the configuration set referenced across the action and approval structures. This is the entry point that corresponds to the object name and is the procedure normally targeted when a DBA or implementation consultant searches for "migrate_parallel_config."

Tables Accessed

The package interacts with the following AME tables, reached through APPS synonyms:

• AME_ACTIONS and AME_ACTION_USAGES — store instantiated actions and where they are consumed.
• AME_ACTION_TYPES, AME_ACTION_TYPE_CONFIG, and AME_ACTION_TYPE_USAGES — hold action type definitions, their configuration, and usage relationships, which are the focus of the action type migration procedure.
• AME_APPROVAL_GROUP_CONFIG — the approval group configuration source/target for the approval group migration.
• AME_RULE_USAGES — indicates where rules are applied, ensuring migrated configuration aligns with active rule usage.
• AME_EXCEPTIONS_LOG and AME_EXCEPTIONS_LOG_S — the AME exception logging pair, used to record migration anomalies and errors that arise during processing.
• DUAL — used for simple select or validation statements within PL/SQL.

ETRM records no other packages as referencing this object, indicating it is a leaf-level utility rather than a shared dependency.

Usage Notes

This package is not intended for routine runtime execution. It is a one-time or release-triggered migration tool, typically invoked during upgrades, patching, or controlled data remediation when AME parallel configuration must be reconciled. Because the procedures accept errbuf and retcode, the intended invocation model is a registered concurrent program executed from the Submit Request form or scheduled on a maintenance window. Such requests are normally run with the AME application context, as the calls depend on the current-user privilege model and on APPS synonyms resolving to the correct AME tables. Custom code should not call these procedures as part of normal approval processing; they are administrative utilities whose use should follow Oracle's migration guidance for the specific release, and their execution should be preceded by a backup of the AME configuration tables.