Search Results ame_rules_api2




Overview
Explore in AI Chat

Overview

AME_RULES_API2 is a public PL/SQL package in the Oracle Applications (APPS) schema that provides the programmatic interface for maintaining rule definitions in the Oracle Approvals Management (AME) engine. AME is the rules framework that determines approval routing, approval hierarchies, and authorization limits for transactions such as requisitions, purchase orders, invoices, and expenses across Oracle E-Business Suite. This package is the supported entry point by which rule records are created, deleted, seeded, and translated in the underlying AME rule tables.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking schema rather than the definer. This makes it suitable for invocation from seed data scripts, Oracle Forms-based setup screens, and customer extensions that must respect the caller's security context. The header comment identifies the file as amereapi.pkh, with a revision of 120.0 dated 2005, consistent with the long-standing AME API family carried forward into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes five documented procedures. Each is a public API intended for controlled use; direct DML against the AME tables is not supported.

  • INSERT_ROW — Creates a new AME rule using the rule's natural business key (X_RULE_KEY) rather than a pre-assigned identifier. All standard WHO columns, start date, description, item class, rule type, and action are supplied by the caller.
  • INSERT_ROW_2 — Performs the same rule creation as INSERT_ROW but accepts X_RULE_ID explicitly as the first parameter. This variant is used when the caller must supply or preserve a known rule identifier, such as during data migration, cloning between environments, or seeding where deterministic IDs are required. This is the procedure most commonly associated with the search term "insert_row_2".
  • DELETE_ROW — Removes an existing rule identified by X_RULE_KEY.
  • LOAD_ROW — Seeds or uploads a rule from external source data using human-readable names (action type name, item class name) and an owner, with custom mode and last-update-date parameters controlling whether an existing definition is overwritten.
  • TRANSLATE_ROW — Loads translated description text for a rule, supporting multilingual (MLS) deployments.

Tables Accessed

The package operates against the AME rules schema through APPS synonyms.

  • AME_RULES, AME_RULES_S, AME_RULES_TL — the base, MLS shadow, and translation tables where rule header data and language-specific descriptions are written and deleted.
  • AME_ACTIONS and AME_ACTION_TYPES — referenced to resolve and validate the action associated with a rule.
  • AME_ITEM_CLASSES — used to validate the item class to which the rule applies.
  • FND_LANGUAGES — consulted for translation handling in TRANSLATE_ROW.
  • DBMS_LOCK — used to serialize concurrent API calls and protect rule integrity.
  • DUAL — used for single-row lookups and sequence or value resolution.

Usage Notes

The package is typically invoked from the AME setup forms, from concurrent programs and seed data loaders, and from custom code performing environment migration. Because no other packaged object is documented as referencing AME_RULES_API2, callers invoke it directly rather than through a wrapper API. Developers should call INSERT_ROW_2 only when an explicit rule identifier must be supplied; otherwise INSERT_ROW is the preferred creation path. All calls should honor the supplied WHO and date columns, and customers upgrading from 12.1.1 to 12.2.2 should verify that custom logic relying on these signatures remains aligned with the current AME data model, since the API is sensitive to rule key uniqueness and translation sequencing.