Search Results ame_action_pkg




Overview
Explore in AI Chat

Overview

APPS.AME_ACTION_PKG is a core PL/SQL package within the Oracle Approvals Management Engine (AME), the rules-based framework that determines approval routing, approval groups, and posting behavior for transactions across Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, AME is invoked by calling applications such as Purchasing, Payables, iExpenses, and Human Resources to derive the approval path for a given business document. AME_ACTION_PKG provides the metadata access layer for action types and their associated actions — the configurable events that AME executes when approval rules fire, including actions such as approval-group chain-of-authority processing, notification generation, and post-approval execution hooks.

The package is documented in ETRM as status VALID, owned by APPS, and classified as an OTHER API. It exposes 61 procedures and functions and is referenced by five other packages — AME_ACTION_PKG itself (internal recursion or body-level references), AME_ADMIN_PKG, AME_APPROVAL_GROUP_PKG, AME_ENGINE, and AME_RULE_PKG — confirming its role as a shared dependency of the AME administration, rule, and runtime engine layers.

Key Procedures and Functions

The documented entry points fall into several functional groups:

  • Action type lookup and identity: GETACTIONTYPEIDBYID, GETACTIONTYPEIDBYNAME, GETACTIONTYPENAME, GETACTIONTYPENAMEBYACTIONID, GETACTIONTYPEDESCRIPTION, GETACTIONTYPEDESCRIPTQUERY, GETACTIONTYPEDYNAMICDESC. These resolve an action type identifier or name to its descriptive metadata, supporting both static descriptions and dynamically generated text.
  • Action type attributes: GETACTIONTYPEPROCEDURENAME, GETACTIONTYPECREATEDBY, GETACTIONTYPEMAXORDERNUMBER, GETACTIONTYPEORDERNUMBER, GETCHAINORDERINGMODE, GETALLOWEDRULETYPE, GETALLOWEDRULETYPELABEL. These expose configuration attributes governing how an action type is invoked, how it is ordered within a chain, and which rule types may reference it.
  • Generic description helpers: GETDESCRIPTION, GETDESCRIPTION2, GETDYNAMICACTIONDESC, and related getters such as GETCHILDVERSIONSTARTDATE and GETCHILDVERSIONSTARTDATE2.
  • Validation and usage checks: ACTIONTYPEISINUSE and the usage-related getters. ACTIONTYPEISINUSE determines whether an action type is currently referenced by configured actions, rules, or approval groups, and is therefore essential to safe deletion or deactivation through the AME administration forms.

Tables Accessed

The package reads and writes the following AME tables via APPS synonyms: AME_ACTION_TYPES, AME_ACTION_TYPES_S (the MLS/translation shadow table), AME_ACTION_TYPE_CONFIG, and AME_ACTION_TYPE_USAGES, which together define the catalog of action types, their configuration, and where they are consumed. AME_ACTIONS, AME_ACTIONS_S, and AME_ACTION_USAGES store the instantiated actions belonging to approval rules. AME_APPROVAL_GROUPS, AME_APPROVAL_GROUP_CONFIG, AME_APPROVER_TYPES, and AME_APPROVER_TYPE_USAGES link action processing to approver resolution. AME_ATTRIBUTES, AME_ITEM_CLASSES, AME_ITEM_CLASS_USAGES, and AME_CALLING_APPS provide the item-class and calling-application context in which action types are permitted. The package further depends on APPS.AME_UTIL for shared AME utility routines and on SYS.STANDARD.

Usage Notes

AME_ACTION_PKG is an internal engine and administration package rather than a public integration API. It is typically invoked indirectly: the AME Engine (AME_ENGINE) calls it during rule evaluation to resolve action types and their configured behavior, while AME_ADMIN_PKG and the AME setup forms use it to render and validate the Action Types and Actions regions. AME_RULE_PKG and AME_APPROVAL_GROUP_PKG consult the usage-check functions before allowing modifications that would orphan configured actions.

Because the classification is OTHER, customers should treat these entry points as unsupported for direct customization. The correct extension pattern is to define custom action types through the AME setup interface and implement the corresponding PL/SQL handler, rather than calling AME_ACTION_PKG procedures directly. In both 12.1.1 and 12.2.2 the package resides in the APPS schema and is patched with AME mini-packs and consolidated updates.