Search Results ame_approver_type_pkg




Overview
Explore in AI Chat

Overview

The APPS.AME_APPROVER_TYPE_PKG package body is a foundational component of the Oracle Approvals Management (AME) engine in Oracle E-Business Suite 12.1.1 and 12.2.2. AME provides a rules-based framework for determining the approver list for any transaction that requires authorization, including purchasing documents, human resources actions, and expense reports. The approver type is the atomic unit of that framework: it defines a category of participant, such as a supervisor, a job holder, a position holder, or an application-specific role, that AME may place on an approval chain. This package supplies the data-access and validation layer for those approver type definitions. It retrieves identifying and descriptive attributes for approver types, maps approver types to their originating system and workflow roles, resolves approver definitions into concrete users or roles at runtime, and validates that a proposed approver satisfies the constraints defined against its approver type. Because the package body is marked VALID and classified as OTHER, it functions as an internal engine utility rather than a published open interface; nevertheless, it is referenced by twenty-seven other database objects, which reflects its centrality to the AME runtime.

Key Procedures and Functions

The forty documented routines fall into four functional groups.

  • Descriptive and identity accessors: GETAPPROVERDESCRIPTION, GETAPPROVERDESCRIPTION2, GETAPPROVERDISPLAYNAME, GETAPPROVERDISPLAYNAME2, GETAPPROVERDISPLAYNAME3, and GETAPPROVERDISPLAYNAME4 return human-readable descriptions and display names for an approver or approver type. The numbered variants accommodate differing calling contexts or return formats.
  • Originating system resolution: GETAPPROVERORIGSYSTEM, GETAPPROVERORIGSYSTEM2, GETAPPROVERORIGSYSTEM3, GETAPPROVERORIGSYSTEMID, GETAPPROVERTYPEORIGSYSTEM, and GETORIGSYSTEMDISPLAYNAME identify the source system from which an approver or approver type originates and translate that system identifier into a display value.
  • Type and role resolution: GETAPPROVERTYPEID, GETAPPROVERTYPEDISPLAYNAME, GETQUERYPROCEDURE, GETWFROLESNAME, ALLOWSALLAPPROVERTYPES, and ISASUBORDINATE resolve the type identifier and its display name, retrieve the query procedure registered for an approver type, return the workflow role name associated with an approver, determine whether a type permits all approver categories, and test the hierarchical subordinate relationship used in supervisory chains.
  • Validation and user resolution: VALIDATEAPPROVER and FNDUSRAPPROVERQUERY verify that a candidate approver is permissible for the given type and resolve approvers against the FND_USER repository.

Tables Accessed

The package reads AME_APPROVER_TYPES, AME_APPROVER_TYPE_USAGES, and AME_ACTION_TYPES for configuration and action mapping data. It resolves approver identities through FND_USER, and organizational context through HR_ALL_ORGANIZATION_UNITS. Person, assignment, and position data are drawn from PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_ASSIGNMENT_STATUS_TYPES, PER_POSITIONS, PER_POSITION_STRUCTURES, PER_POS_STRUCTURE_ELEMENTS, and PER_POS_STRUCTURE_VERSIONS, supporting supervisory and positional approver types. Workflow role data is sourced from WF_LOCAL_ROLES and WF_ROLES.

Usage Notes

This package is invoked internally by the AME engine and by dependent AME packages during approver list generation and rule evaluation. It is not intended as an end-user entry point and is not called directly from standard EBS forms or concurrent programs. Customizations should invoke AME public APIs such as AME_API1 or AME_ENGINE rather than this package, since its signatures and behavior are not contractual and may change between patch levels.