Search Results ame_rules_s

Overview

APPS.AME_RULES_API2 is a public PL/SQL package body that belongs to the Approvals Management Engine (AME) schema in Oracle E-Business Suite. Its principal business function is to provide the seed-data and translation data maintenance interface for AME approval rules. Within the AME architecture, a "rule" is the entity that links business conditions to approval actions and action types, ultimately determining the approval routing applied to a transaction such as a purchase order, requisition, or expense report. The package supports Oracle's standard mechanism for seeding configuration data into a database during installation, upgrade, or localization, and it therefore works in close conjunction with the AME seed utility and AME utility APIs. The object is documented as VALID in the ETRM repository for both 12.1.1 and 12.2.2; its API classification is OTHER, indicating it is a seed-support API rather than an end-user facing approval processing API. It is referenced by no other database object, confirming its role as a top-level maintenance entry point.

Key Procedures and Functions

Five documented procedures constitute the public interface of the package body:

• INSERT_ROW — Inserts a new row into the AME rules repository. It is the primary interface for creating rule definitions during seeded data loading operations.
• INSERT_ROW_2 — A secondary insert routine, providing the additional insert variant required by later or alternative seed data load paths; it complements INSERT_ROW where a different set of defaults or a distinct insert path is needed.
• DELETE_ROW — Removes an existing rule row, providing the standard deletion path used when seed data is retired or refreshed.
• LOAD_ROW — Performs the standard seed loader operation: it determines whether the target rule already exists and either inserts new data or applies the required update, thereby making repeated seed executions idempotent.
• TRANSLATE_ROW — Loads or refreshes translated (non-base-language) rule text, operating against the translation table so that rule names and descriptions are available in the languages defined in FND_LANGUAGES.

No parameter lists are reproduced here, as the ETRM metadata documents procedure names and purposes only.

Tables Accessed

The package reads and writes the tables that make up the AME rule configuration model. AME_RULES is the rule header table and is the primary target of INSERT_ROW, INSERT_ROW_2, DELETE_ROW, and LOAD_ROW. AME_RULES_S is the corresponding seed table that holds the seed definitions applied by the loader. AME_RULES_TL holds the translated rule text and is the target of TRANSLATE_ROW. Supporting configuration tables include AME_ACTIONS and AME_ACTION_TYPES, which define the approval actions a rule can invoke, and AME_ITEM_CLASSES, which defines the item classes (transaction types) a rule applies to. FND_LANGUAGES supplies the installed language list used during translation loading, and FND_PROFILE supplies environment and language context. DBMS_LOCK and DUAL are used for locking and single-row query constructs respectively. The package also depends on AME_SEED_UTILITY and AME_UTIL for shared seed and utility logic.

Usage Notes

AME_RULES_API2 is not normally invoked directly by end users. It is called by Oracle's seeded data loading processes — typically from SQL*Plus scripts or concurrent-program driven loader routines delivered with AME and executed during installation, patching, upgrade, and NLS localization. Because the loader routines are idempotent, they may be re-run safely. Custom implementations may call these procedures when delivering their own AME rule seed data, but such use must respect the AME_RULES_S seed staging conventions and the schema's validation rules. Direct DML against the AME rules tables is discouraged; the API and the AME seed utility should be used instead.