Search Results ame_approval_group_pkg




Overview
Explore in AI Chat

Overview

AME_APPROVAL_GROUP_PKG is the core PL/SQL package within the Oracle Approvals Management (AME) module responsible for managing approval group definitions and their associated configuration metadata. Approval groups are the organizational containers that determine which approvers participate in a given transaction approval chain, and this package provides the programmatic interface through which AME retrieves, validates, and maintains the structural attributes of those groups. In Oracle EBS 12.1.1 and 12.2.2, the package resides in the APPS schema with a status of VALID, and it is classified under the "OTHER" API category, indicating it is primarily an internal engine utility rather than a public, supported integration API.

The package operates at the intersection of AME's rule engine and its underlying transactional data model, exposing both single-attribute accessors and higher-level comparison routines. Because approval group definitions are versioned and effective-dated, the package handles the resolution of the appropriate version at a given point in time, along with the ordering of items within a group and the voting regime that governs how group member responses are aggregated.

Key Procedures and Functions

The documented interface comprises 47 procedures and functions. The accessor functions center on the identity and descriptive attributes of approval groups: GETID returns the internal identifier, GETNAME and GETDESCRIPTION return the group's name and descriptive text, and GETISSTATIC indicates whether the group is defined statically or through a dynamic query. GETQUERYSTRING returns the query text used for dynamic group membership.

Item-level functions concern the individual entries that make up a group: GETITEMID, GETITEMAPPROVALGROUPID, GETITEMORDERNUMBER, GETITEMPARAMETER, and GETITEMPARAMETERNAME retrieve the identity, parent group, sequence position, and parameter metadata for a given item. The ordering routines — GETAPPROVALGROUPORDERNUMBER, GETAPPROVALGROUPMAXORDERNUMBER, GETAPPROVALGROUPITEMMAXORDNUM, and GETORDERNUMBERCOUNT — support sequencing and capacity checks within a group.

Versioning is handled by GETCHILDVERSIONSTARTDATE and GETPARENTVERSIONSTARTDATE, which resolve the effective start dates of related group versions. Comparison and structural routines include GROUPISINGROUP, which tests containment relationships, and the HASGROUPCHANGED and HASGROUPCHANGED2 functions, which detect whether a group definition has been modified between versions. GETVOTINGREGIME returns the voting rule applied when the group's members respond to an approval request.

Tables Accessed

The package reads from and writes to several AME base tables through APPS synonyms. Group header data is held in AME_APPROVAL_GROUPS and its shadow table AME_APPROVAL_GROUPS_S, while item-level data resides in AME_APPROVAL_GROUP_ITEMS and AME_APPROVAL_GROUP_ITEMS_S. Member information is retrieved from AME_APPROVAL_GROUP_MEMBERS and AME_APPROVAL_GROUP_MEMBERS_S. Configuration metadata is sourced from AME_APPROVAL_GROUP_CONFIG, and action-related lookups draw on AME_ACTIONS, AME_ACTION_TYPES, and AME_ACTION_USAGES.

Supporting data is obtained from AME_CALLING_APPS, FND_USER, and PER_ALL_PEOPLE_F for application context and approver identification. DUAL and PLITBLM are referenced for standard utility purposes.

Usage Notes

AME_APPROVAL_GROUP_PKG is referenced by several other AME components, including AME_ADMIN_PKG, AME_AG_CHAIN_HANDLER, AME_AG_HANDLERS, and AME_ENGINE, and is documented as being referenced by four other packages. It is therefore invoked indirectly during approval chain construction and during the administration of approval group definitions through the AME setup forms. Custom code should treat this package as an internal engine dependency rather than a supported public API; the AME_ENGINE and admin packages are the appropriate integration points for most extensions. Direct calls should be limited to read-only accessor use where the calling context already holds valid group identifiers and effective dates.