Search Results ame_rule_pkg




Overview
Explore in AI Chat

Overview

AME_RULE_PKG is the core PL/SQL package body within the Oracle Approvals Management Engine (AME) schema (APPS) responsible for creating, validating, and maintaining approval rules and their associated conditions, actions, and usages. AME is the rules framework that determines approver lists, approval chains, and routing behavior for Oracle E-Business Suite transactions such as requisitions, purchase orders, and expense reports. The package encapsulates the business logic that governs rule keys, rule definitions, item classes, condition usages, and action usages, providing a programmatic and forms-driven interface to the underlying AME configuration tables. As a VALID package body owned by APPS in EBS 12.1.1 and 12.2.2, AME_RULE_PKG is documented as an OTHER-classification API and exposes an extensive set of procedures and functions (84 total) that together form the rule administration layer of the AME engine.

Key Procedures and Functions

The package exposes numerous documented procedures and functions. Representative members include rule-key and identifier utilities such as GETID, RULEKEYEXISTS, GETNEXTRULEKEY, GETITEMCLASSID, GETDESCRIPTION, and DESCRIPTIONINUSE, which support lookups and uniqueness validation during rule administration. Date-effective logic is handled by GETENDDATE, GETSTARTDATE-related utilities, GETEFFECTIVEENDDATEUSAGE, and GETEFFECTIVESTARTDATEUSAGE, which resolve the validity windows applied to rules and their usages.

Validation and status helpers include APPHASRULES, BOTHSEEDEDLMACTIONTYPESCHOSEN, BOTHSEEDEDLMACTIONTYPESCHOSEN2, FINALAUTHORITYACTIONTYPE, FINALAUTHORITYACTIONTYPE2, GETAPPROVERCATEGORY, and GETCONDITIONCOUNT. Deletion and cleanup logic is provided by ALLORDINARYCONDITIONSDELETED, DELETEDALLEXCEPTIONCONDITIONS, and GETLMCONDITIONID. Collectively these routines manage the insertion, update, deletion, and query of rule definitions, condition usages, and action usages that make up an AME configuration. The package also maintains internal consistency of rule keys and their sequencing when rules are added or removed.

Tables Accessed

AME_RULE_PKG reads and writes the principal AME configuration tables. Rule headers and their denormalized shadow table are addressed through AME_RULES and AME_RULES_S, while rule key integrity and sequencing are managed via AME_RULE_KEYS_S and AME_RULE_USAGES. Condition definitions and their applications are handled through AME_CONDITIONS, AME_CONDITION_USAGES, AME_ATTRIBUTES, and AME_MANDATORY_ATTRIBUTES. Action-related tables include AME_ACTIONS, AME_ACTION_TYPES, AME_ACTION_TYPE_USAGES, and AME_ACTION_USAGES. Item class scoping is managed via AME_ITEM_CLASSES and AME_ITEM_CLASS_USAGES, and calling application registration is referenced through AME_CALLING_APPS. Supporting dependencies include AME_UTIL and AME_ADMIN_PKG for shared utilities and administration, plus standard SYS objects (DUAL, DBMS_STANDARD, PLITBLM, V$DATABASE, V$INSTANCE) and HR_ORGANIZATION_UNITS for organization context.

Usage Notes

AME_RULE_PKG is typically invoked through the AME administration forms and rule-building UI, where it enforces validation and persistence for rules, conditions, and actions. It is also called from the AME setup and seeding processes, particularly the logic that checks whether both seeded line-manager action types have been chosen and whether a final authority action type is in use. Custom code and concurrent programs that programmatically configure AME frequently call the package's getters and validators rather than writing directly to AME tables, preserving referential and rule-key integrity. Because the package owns the lifecycle of rules and their usages, direct DML against AME_RULES and related tables should be avoided. The package is referenced by eight other packages, reinforcing its central role in the AME runtime and administration stack, and it depends on AME_ACTION_PKG, AME_ATTRIBUTE_PKG, and AME_CONDITION_PKG for lower-level validation.