Search Results ame_item_classes_api




Overview
Explore in AI Chat

Overview

AME_ITEM_CLASSES_API is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Approvals Management (AME) product family and is classified in the ETRM metadata as an API rather than as a private implementation unit. AME provides the rules engine that determines approval routing for transactions across multiple applications, including iExpenses, Purchasing, and Human Resources. Approval routing is driven largely by the attributes attached to an approval item, and AME organizes those attributes into item classes.

An item class is the logical grouping that tells AME which transaction type is being evaluated and which attributes are available for constructing approval rules. AME_ITEM_CLASSES_API exposes the data-maintenance layer for these item class definitions. In practical terms, the package provides programmatic insert, update, delete, load, and translation operations against the AME item class tables, allowing item class metadata to be created or migrated without direct DML against the underlying tables. Its status is recorded as VALID in the ETRM repository.

Key Procedures and Functions

The documented interface consists of five procedures:

  • INSERT_ROW — Creates a new item class record, populating the base definition and its associated translated and secure rows as required by the AME data model.
  • UPDATE_ROW — Modifies an existing item class definition, allowing attributes and descriptive information to be changed after initial creation.
  • DELETE_ROW — Removes an item class definition from the AME repository.
  • LOAD_ROW — Performs a load-style insert or update, typically used for data migration, seeding, or bulk import of item class definitions from external or staged sources.
  • TRANSLATE_ROW — Maintains the translated (multi-language) text associated with an item class, writing to the translation table for the requested language.

The ETRM metadata does not document parameter lists for these routines; consumers should inspect the package specification in the target instance before invoking them.

Tables Accessed

The package operates against the AME item class schema through APPS synonyms. The primary tables are AME_ITEM_CLASSES, AME_ITEM_CLASSES_S, and AME_ITEM_CLASSES_TL. AME_ITEM_CLASSES holds the base definition, AME_ITEM_CLASSES_S holds the secure (effective-dated or secured) row components, and AME_ITEM_CLASSES_TL holds translated descriptions and display text. FND_LANGUAGES is referenced to validate or resolve the language code used by TRANSLATE_ROW. DBMS_LOCK is used for concurrency control so that overlapping maintenance operations do not corrupt item class data. DUAL is referenced for standard PL/SQL and SQL constructs. Because the package is an API layer, all access to these tables occurs through the package routines rather than through ad hoc DML.

Usage Notes

AME_ITEM_CLASSES_API is typically invoked during AME configuration and setup, during patching or data migration that seeds item class metadata, and from custom code that must register or maintain an approval item class programmatically. It is not a high-frequency runtime API; the AME engine reads item class definitions directly during transaction approval processing, so the API is a maintenance and provisioning interface. The ETRM metadata records that the package is referenced by zero other packages, indicating it is not a shared internal dependency of other AME modules and is intended for external or administrative callers. Oracle EBS 12.1.1 and 12.2.2 share the same AME item class data model, so the package behaves consistently across both releases. Where item classes are created through standard AME setup screens, the underlying forms call this API; custom integrations should follow the same path rather than inserting directly into AME_ITEM_CLASSES, AME_ITEM_CLASSES_S, or AME_ITEM_CLASSES_TL, in order to preserve the multi-language and concurrency handling the package provides.