Search Results ame_actions_s

Overview

AME_ACTION_PKG is the core PL/SQL package in the Oracle Approvals Management (AME) module of Oracle E-Business Suite. It encapsulates the business logic that governs approval actions—the discrete operations AME performs during an approval transaction, such as notifying an approver, requesting additional information, or executing a stored procedure. The package body resides in the APPS schema with a status of VALID and is classified under the OTHER API category in the ETRM 12.2.2 documentation. It is central to the runtime execution of approval rules, translating approver and action configurations into actionable outcomes. The package body exposes 61 documented procedures and functions, making it one of the more substantial API surfaces within the AME schema. It is referenced by five other packages and itself depends on several AME packages including AME_APPROVER_TYPE_PKG, AME_ATTRIBUTE_PKG, and AME_UTIL.

Key Procedures and Functions

The documented procedures and functions fall into several functional groups. Action-type retrieval functions include GETACTIONTYPEIDBYID and GETACTIONTYPEIDBYNAME, which resolve action type identifiers from internal IDs or human-readable names. Descriptive functions such as GETACTIONTYPEDESCQUERY, GETACTIONTYPEDYNAMICDESC, GETACTIONTYPEDESCRIPTION, GETTYPENAME, and GETDYNAMICACTIONDESC build display text for action types, supporting dynamic descriptions that incorporate runtime data. Metadata accessors include GETACTIONTYPEMAXORDERNUMBER, GETACTIONTYPEORDERNUMBER, GETACTIONTYPEPROCEDURENAME, and GETACTIONTYPECREATEDBY, which expose ordering, procedure name, and audit information for configured action types. Configuration-related functions include GETALLOWEDRULETYPE, GETALLOWEDRULETYPELABEL, and GETCHAINORDERINGMODE, which govern how approval chains are assembled and which rule types are permissible. Version-related functions such as GETCHILDVERSIONSTARTDATE and GETCHILDVERSIONSTARTDATE2 determine effective dating for child approval versions. Generic description accessors GETDESCRIPTION and GETDESCRIPTION2 round out the documented surface. In addition, ACTIONTYPEISINUSE verifies whether an action type is referenced by active configuration, protecting referential integrity during maintenance.

Tables Accessed

The package reads and writes a broad set of AME configuration and transaction tables. AME_ACTIONS and its language-independent sibling AME_ACTIONS_S store the configured approval actions and their translated descriptions. AME_ACTION_TYPES, AME_ACTION_TYPES_S, and the view AME_ACTION_TYPES_VL hold action type definitions, while AME_ACTION_TYPE_CONFIG and AME_ACTION_TYPE_USAGES record how action types are configured and where they are used. AME_ACTION_USAGES tracks actual action usage. AME_APPROVAL_GROUPS, AME_APPROVAL_GROUP_CONFIG, AME_APPROVER_TYPES, AME_APPROVER_TYPE_USAGES, and AME_ATTRIBUTES supply the approver and attribute context necessary to evaluate and execute actions. AME_CALLING_APPS identifies the calling application context, and AME_ITEM_CLASSES with AME_ITEM_CLASS_USAGES link actions to the transaction types they apply to. Supporting dependencies include AME_MANDATORY_ATTRIBUTES and AME_RULES, which are referenced indirectly through the package's declared dependencies.

Usage Notes

AME_ACTION_PKG is not typically invoked directly by end users. It is called primarily from within the AME runtime engine during approval list generation and action execution, and from AME configuration forms and concurrent programs that maintain action types and their associated routing. Custom code extending AME should call the public functions to resolve action type identifiers and descriptions rather than querying the underlying tables directly, ensuring consistency with AME's own metadata handling. Because the package depends on AME_UTIL and AME_APPROVER_TYPE_PKG, any modification to those dependencies can invalidate this body. Administrators troubleshooting approval behavior should confirm the package remains VALID after patching, as an invalid AME_ACTION_PKG will halt approval processing for transactions that rely on configured actions. The object is not referenced by any database object outside of the AME package family, so its impact is contained to the approvals domain.