Results for “ame_test_utility_pkg”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.AME_TEST_UTILITY_PKG is a utility package in the Oracle Approvals Management Engine (AME) schema, owned by APPS and classified as an OTHER-type API in ETRM. Its business purpose is to support testing, diagnostics, and simulation of the AME approval engine: it allows developers and functional administrators to preview which approval rules apply to a hypothetical transaction, to determine which approvers would be generated, and to inspect the various production (approval type) lists that AME would derive. Because AME evaluates approvals dynamically from rule definitions, attribute values, and transaction attributes rather than from static routing, a package such as this is essential for validating configuration before it goes live, and for reproducing and debugging approval behavior in a controlled manner. The package operates against the AME rule, attribute, and usage tables rather than against production transaction data, and it is documented in ETRM for 12.1.1 and 12.2.2 with 5 documented procedures/functions. It is not referenced by any other package, indicating it sits at the top of the AME dependency chain as a leaf-level helper.

Key Procedures and Functions

  • POPULATEREALTRANSATTRIBUTES — Populates the temporary transaction attribute values table with the real attribute values for a transaction, giving AME the input data it needs to evaluate rules and attributes in a test context.
  • GETAPPLICABLERULES — Returns the set of AME rules that apply to a given transaction/attribute combination, based on the configured condition and rule usages. This is the core "what rules would fire?" diagnostic.
  • GETAPPROVERS — Returns the approvers that AME would produce for the transaction, corresponding to the AME_APPROVERS_LIST entity (the object associated with the user's search term "ame_approvers_list"). This function mirrors the approver list generation performed by the live engine.
  • GETTRANSACTIONPRODUCTIONS — Returns the productions (approval types / production lists such as AME_PRODUCTIONS_LIST) that apply to the transaction.
  • ISATTRIBUTESEXIST — Determines whether the required AME attributes exist for the test scenario, acting as a precondition check before rule evaluation.

Tables Accessed

The package reads AME configuration and usage metadata through APPS synonyms: AME_ACTION_USAGES, AME_ATTRIBUTES, AME_ATTRIBUTE_USAGES, AME_CONDITION_USAGES, AME_ITEM_CLASSES, AME_MANDATORY_ATTRIBUTES, AME_RULES, and AME_RULE_USAGES supply the rule, condition, action, and attribute definitions used to resolve applicable rules and approvers. AME_TEMP_TRANS_ATT_VALUES holds the temporary transaction attribute values written by POPULATEREALTRANSATTRIBUTES. WF_ITEM_ACTIVITY_STATUSES provides workflow activity status context for the transaction. PLITBLM is the standard PL/SQL table type used internally for array-based parameter passing. ETRM dependency listings additionally associate the package with AME_APPROVERS_LIST, AME_PRODUCTIONS_LIST, and AME_RULES_LIST, reflecting the list structures returned by its getter procedures.

Usage Notes

AME_TEST_UTILITY_PKG is a diagnostic/test utility rather than a seeded integration point. It is typically invoked from custom test scripts, SQL*Plus sessions, or AME setup validation routines used by implementers during configuration, rather than from standard Oracle Forms or concurrent programs. Because the package writes to AME_TEMP_TRANS_ATT_VALUES, it should be executed in a controlled environment or within a transaction that is rolled back, and not called from production approval processing paths. Correct results depend on attributes being fully defined in AME_ATTRIBUTES/AME_MANDATORY_ATTRIBUTES; the ISATTRIBUTESEXIST check should be used first to confirm completeness. Since it references the same underlying lists (AME_APPROVERS_LIST, AME_PRODUCTIONS_LIST, AME_RULES_LIST) that the live engine produces, its output can be compared against real-time AME results to validate a configuration before deployment.