Results for “ame_api7”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AME_API7 is a PL/SQL package owned by the APPS schema within Oracle E-Business Suite. It forms part of the Oracle Approvals Management Engine (AME) API layer, the framework that governs approval routing, approver determination, and approval-group evaluation across EBS application modules such as Purchasing, iProcurement, Payables, and Human Resources. AME_API7 is classified as an "OTHER" API, meaning it is not a public integration API exposed for general customer consumption but rather an internal support package used by the AME engine itself.

The package's documented purpose centers on the retrieval of approval group members and attribute values. Approval groups in AME define collections of approvers whose membership may be determined statically or through dynamic rules. AME_API7 provides the runtime plumbing that resolves the membership of these groups when the approval routing engine requires a list of candidate approvers. Its dependency on AME_UTIL confirms that it participates in the shared utility layer of AME rather than owning top-level business logic. The ETRM metadata records the package as VALID in both the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

The ETRM metadata documents five procedures or functions in this package. It is important to note that the documented procedure names suggest variant implementations of group-member resolution, likely differing by the type of approval-group definition being processed.

• GETGROUPMEMBERS1 — Returns the set of members belonging to an approval group. This is the first of four variant member-resolution routines, each presumably handling a distinct group-definition category (for example, static lists, HR organization-based, and dynamic query-based groups).
• GETGROUPMEMBERS2 — A second variant of approval-group member retrieval, providing an alternate resolution path for a different class of group definition.
• GETGROUPMEMBERS3 — A third variant, again resolving group membership under different structural assumptions than the preceding routines.
• GETGROUPMEMBERS4 — The fourth documented member-resolution variant.
• GETATTRIBUTEVALUE — Retrieves the value of an approval-related attribute at runtime. This routine supports the AME rule-evaluation process, where attribute values (such as transaction amount, item category, or job level) drive routing decisions.

The presence of four distinct group-member routines indicates that the underlying logic branches heavily based on the approval group's type and the manner in which its membership is defined in the AME setup.

Tables Accessed

The package references the following tables via APPS synonyms:

• AME_APPROVAL_GROUP_MEMBERS — The primary data source for the GETGROUPMEMBERS routines. This table stores the resolved membership of approval groups, and the package reads from it to return candidate approvers to the calling AME process.
• DBMS_SQL — The Oracle-supplied dynamic SQL package. Its reference indicates that at least some of the group-member routines construct and execute SQL statements dynamically, consistent with AME's support for user-defined dynamic approval groups whose membership is expressed as a query.
• PLITBLM — A PL/SQL-indexed table of VARCHAR2 used as a collection type within the package, employed to pass arrays of member identifiers or attribute values between routines and their callers.

Usage Notes

AME_API7 is invoked internally by the AME engine during approval routing and is not documented as a public API. Because it is referenced by zero other packages per the ETRM dependency record, it sits at a leaf of the AME call graph and is called directly by the AME runtime or by sibling API packages within the AME suite. Custom code that invokes AME_API7 directly is uncommon and unsupported, since the package is not published for customer integration. The supported integration surface for AME remains the documented AME_API and AME_API2 entry points. Administrators troubleshooting approval routing behavior may encounter AME_API7 in database traces and AWR reports, where the GETGROUPMEMBERS routines are typically visible as the immediate consumers of AME_APPROVAL_GROUP_MEMBERS during approver-list construction.