Results for “ame_admin_pkg”

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

Overview

AME_ADMIN_PKG is an administrative utility package within the Oracle E-Business Suite Approval Management Engine (AME). The AME framework, introduced in EBS 11i and carried forward through releases 12.1.1 and 12.2.2, provides configurable, rules-based approval routing for transactions originating in Oracle Purchasing, iProcurement, Human Resources, Payables, and other modules. Rather than embedding approval hierarchies directly in each transaction application, AME externalizes the decision logic so that administrators can maintain approval groups, conditions, and rule definitions declaratively.

AME_ADMIN_PKG supports this model by exposing a library of administrative and lookup functions that the core AME engine and its public API layer rely upon at runtime. Its documented classification is OTHER, meaning it is not part of the officially supported public API surface, but it is a foundational internal component. The package is present and VALID in the APPS schema, and it references APPS.AME_UTIL together with the SYS.STANDARD package, confirming its role as a low-level helper beneath the higher-level APIs.

Key Procedures and Functions

The ETRM gives 92 documented program units. Representative members, grouped by purpose, are:

• Application and lookup resolution: GETAPPLICATIONID, GETAPPLICATIONIDBYNAME, GETAPPLICATIONNAME, GETFNDAPPLICATIONID, GETFNDAPPLICATIONS, GETFNDAPPDESCRIPTION, and GETFNDAPPDESCRIPTION1 return FND application identifiers, names, and descriptive text. These are used throughout AME to translate between internal numeric IDs and user-facing application references.
• Condition and rule support: GETEQUALITYCONDITIONID assists in locating an equality-based condition record, while GETATTRIBUTEQUERY and GETLINEITEMQUERYSTRING build the SQL fragments AME uses to evaluate attributes against transaction data.
• Striping administration: DOESSTRIPESETIDEXIST, ADDSTRIPINGATTRIBUTE, GETATTRIBUTESTRIPESETNAMES, and GETATTRIBUTESTRIPINGUSECOUNT manage the AME "striping" feature, which partitions approval logic across concurrent sets of attributes and rules.
• Item class and attribute validation: CANHAVEITEMATTRIBUTES, GETEXISTINGSHAREABLEICLASSES, and GETATTRIBUTEDISPLAYVALUE determine whether item classes may carry attributes and how those attributes are presented.
• Versioning and behavior options: GETCHILDVERSIONSTARTDATE supports rule-version effective dating, while GETFORWARDINGBEHAVIORLIST and AREPRIORITIESDISABLED return configuration flags governing approval forwarding and priority-based routing.

Tables Accessed

AME_ADMIN_PKG reads and writes the core AME configuration tables via APPS synonyms. AME_APPLICATIONS_S and AME_CALLING_APPS identify the source applications and the AME-enabled calling contexts. AME_ATTRIBUTES, AME_ATTRIBUTE_USAGES, and AME_MANDATORY_ATTRIBUTES define the data points available for rule evaluation. AME_CONDITIONS, AME_RULES, and AME_RULE_USAGES hold the approval rulesets themselves. AME_ITEM_CLASSES and AME_ITEM_CLASS_USAGES support item-classification-driven attribute permissioning. AME_ACTION_TYPE_CONFIG, AME_APPROVAL_GROUP_CONFIG, and AME_STRING_VALUES store action and group configuration parameters. AME_CONFIG_VARS is the general configuration store, and AME_EXCEPTIONS_LOG captures runtime exception records generated during administration and evaluation.

Usage Notes

AME_ADMIN_PKG is invoked almost exclusively from other PL/SQL, not directly by end users. According to ETRM dependency data, it is referenced by twelve packages, notably the public API family AME_API, AME_API2, AME_API3, AME_API5, AME_API6, and AME_API7, the evaluation engine AME_ENGINE, the configuration packages AME_RULE_PKG and AME_ATTRIBUTE_PKG, and the test utilities AME_TEST_PKG and AME_TEST_UTILITY_PKG. The Oracle Approvals Management administrative responsibility, exposed through the OA Framework pages under the Application Developer and AME Administrator menus, drives these higher-level APIs, which in turn call AME_ADMIN_PKG. Because the package is unsupported for direct external use, customizations should not call it from bespoke forms or concurrent programs; integrations should instead use the supported AME_API entry points. Oracle recommends treating AME_ADMIN_PKG as internal implementation detail whose signatures may change between point releases of 12.1.1 and 12.2.2.