Search Results ame_api6




Overview
Explore in AI Chat

Overview

AME_API6 is an Oracle Application Object Library package owned by the APPS schema and is a component of the Oracle Approvals Management (AME) framework. Its role is to provide a programmatic interface through which calling applications can create, retrieve, and maintain approver lists and approval transaction records. In the Oracle E-Business Suite technology stack, AME supplies the rule-based approval engine that determines who must approve a given business transaction — purchase requisitions, expense reports, HR actions, contracts, and work orders, among others. AME_API6 is a lower-level API that supports this engine by exposing approver retrieval and approval status update operations to both standard EBS products and customer extensions. The object is documented as VALID in the ETRM repository and is classified under the OTHER API category. Its metadata is consistent across the 12.1.1 and 12.2.2 releases, where it continues to be referenced by several approval-driven workflows and self-service pages.

Key Procedures and Functions

The ETRM documentation records four entry points in this package:

  • GETAPPROVERS — retrieves the approver list for a given approval transaction. It is the primary read access point for callers needing to know which approvers have been identified by the AME rules engine.
  • GETAPPROVERS2 — a supplementary or later-generation variant of the approver retrieval routine, typically offering extended behaviour or additional selection criteria while preserving the original contract for existing callers.
  • UPDATEAPPROVALSTATUS — writes the outcome of an approval action (for example, approved, rejected, or reassigned) back to the AME transaction records.
  • UPDATEAPPROVALSTATUS2 — a companion routine that performs the same logical status update with revised or extended semantics.

No parameter lists are documented in the ETRM metadata, and callers should obtain exact signatures from the package specification in the database.

Tables Accessed

AME_API6 operates against the following tables through APPS synonyms:

  • AME_CALLING_APPS — identifies the applications registered with AME and governs which calling application is entitled to use the API.
  • AME_TEMP_OLD_APPROVER_LISTS — stores interim or historical approver list data consumed when reconstructing prior approval state.
  • AME_TRANS_APPROVAL_HISTORY — the audit trail of approval actions against a transaction; read for status retrieval and written by the status update routines.
  • WF_LOCAL_ROLES — the Oracle Workflow role repository, used to resolve approvers and their role memberships.
  • PLITBLM — the standard PL/SQL table-of-varchar2 index-by table type declaration, used internally for passing collections.

Usage Notes

AME_API6 is not intended for direct end-user invocation. It is consumed by other packaged code, and the ETRM dependency listing shows it referenced by AP_WEB_EXPENSE_WF, EAM_WORKORDER_UTIL_PKG, HR_APPROVAL_SS, OKC_REP_WF_PVT, and POR_AME_APPROVAL_LIST, covering expense, maintenance, HR self-service, contracts, and purchasing requisition approval flows respectively. The package itself depends on AME_UTIL and AME_UTIL2, the shared AME utility packages. Custom integrations that require approver determination or status write-back should call the same documented procedures, but must respect the AME calling-application registration recorded in AME_CALLING_APPS. Because the package is a supported, valid database object, it may be invoked from concurrent programs, workflow function activities, OAF pages, and custom PL/SQL; nevertheless, direct calls should be treated as an interface risk, and any use should be validated against the target release, as internal behaviour may differ between 12.1.1 and 12.2.2.