Search Results ame_item_classes_s

Overview

The APPS.AME_ITEM_CLASSES_API package body provides the programmatic interface for maintaining Approvals Management Engine (AME) item class definitions in Oracle E-Business Suite 12.1.1 and 12.2.2. Item classes are the top-level categorization construct in AME: every transaction type that participates in the approval routing framework—such as header, line item, cost center, and project code—is registered as an AME item class before rules, attributes, and approver groups can be associated with it. The package encapsulates the DML and translation logic required to create, change, and remove these definitions without requiring callers to manipulate the underlying tables directly.

In the ETRM 12.2.2 classification the object is registered as an API owned by APPS, confirming that it is an Oracle-supported interface rather than a private utility. The header comments in the source (ameicapi.pkb 120.11) show that the body is itself seeded and version-managed, and helper routines such as OWNER_TO_WHO and KEY_TO_IDS resolve seed-data owner names into the WHO columns and derive surrogate keys from natural item class names.

Key Procedures and Functions

• INSERT_ROW — Creates a new item class definition, writing the base row to AME_ITEM_CLASSES and the corresponding translated name to AME_ITEM_CLASSES_TL. When the supplied item class name is one of the predefined AME classes, the procedure resolves the fixed identifier (1 through 4) through the same decode logic embedded in KEY_TO_IDS; otherwise it consumes the ame_item_classes_s sequence.
• UPDATE_ROW — Modifies an existing item class, including its effective start and end dates and its display name, applying the standard WHO audit columns through OWNER_TO_WHO. Optimistic locking is enforced through the object version number returned by KEY_TO_IDS, which defaults to 1 when the column is null.
• DELETE_ROW — Removes an item class definition and its translated rows, subject to the referential constraints that prevent deletion of a class still referenced by AME rules or attributes.
• LOAD_ROW — Performs a "create or update" seed-style load. It is the entry point used by seed data loaders to insert the row when it does not exist, or to apply the supplied values when the item class is already present, making it idempotent across repeated patch runs.
• TRANSLATE_ROW — Maintains the language-specific name in AME_ITEM_CLASSES_TL for each installed language, allowing an item class to carry distinct display text per locale while sharing a single base definition.

Tables Accessed

The package operates across the AME item class table family. AME_ITEM_CLASSES holds the base definition, including the name, effective dating columns, and object version number. AME_ITEM_CLASSES_S is the sequence used to generate identifiers above the reserved range of 4. AME_ITEM_CLASSES_TL stores the translated names consumed by INSERT_ROW, LOAD_ROW, and TRANSLATE_ROW. FND_LANGUAGES identifies the installed and active languages for which translation rows are created or validated. DBMS_LOCK is used to serialize concurrent modifications to the same item class, and DUAL supports the decode-based key resolution and date arithmetic in KEY_TO_IDS.

Usage Notes

Because the package is registered as an API and is referenced by no other packaged object, it is normally invoked from three contexts: AME setup forms that present item classes to the application administrator, concurrent programs or patch drivers that seed the predefined classes during installation and upgrade, and custom code or data-migration scripts that register new item classes for customer-specific transaction types. Callers should supply the owner identifier expected by the seed utility so that WHO columns are populated correctly, and should always pass the current object version number on update to avoid overwriting concurrent changes. Custom code should call the documented procedures rather than inserting into AME_ITEM_CLASSES and AME_ITEM_CLASSES_TL directly, since the API also handles sequence allocation, translation maintenance, and locking. Note that the user query term insert_tl_row corresponds to internal translation-handling logic; the publicly documented entry point for translation is TRANSLATE_ROW, and the documented insert path is INSERT_ROW.