Results for “ame_test_pkg”

28 results




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

Overview

AME_TEST_PKG is a PL/SQL package owned by APPS within the Oracle Application Management Engine (AME) module of Oracle E-Business Suite. AME provides the rules-based engine that determines approvers and approval routing for transactions submitted from various EBS applications, such as iProcurement requisitions, Purchasing documents, and Human Resources transactions. The AME_TEST_PKG package serves a specialized purpose within AME: it supports the "test transaction" facility that allows administrators and implementers to simulate approval processing without committing real business transactions. It enables users to create test transactions, populate them with attribute values, evaluate the applicable approval rules, and inspect the resulting approver lists. This functionality is essential during AME rule configuration and validation, allowing rule logic to be exercised and verified before being deployed against live production documents. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the defining user.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions, organized around the lifecycle of a test transaction:

  • GETTESTTRANSACTIONID — Returns a generated transaction identifier used to tag test transactions.
  • INITIALIZETESTTRANS — Initializes the internal state for a new test transaction.
  • ISTESTITEMIDDUPLICATE — Returns a boolean indicating whether a given item identifier already exists within a test transaction for a specified application, transaction, and item class.
  • DELETETESTITEMS — Removes test items associated with an application, transaction, and item class, accepting a list of items to delete.
  • SETALLATTRIBUTEVALUES and SETATTRIBUTEVALUES — Populate attribute values for items within a test transaction.
  • GETALLATTRIBUTEVALUES and GETALLATTRIBUTEVALUES2 — Retrieve the full set of attribute identifiers, names, types, mandatory flags, and up to three value columns for a transaction or item.
  • GETITEMATTRIBUTEVALUES — Retrieves attribute values for a specific item.
  • GETITEMIDS — Returns the item identifiers present in a test transaction.
  • GETAPPLICABLERULES — Returns the rules that apply to a test transaction for a given rule list version, including rule item classes, item classes, item IDs, rule types, and descriptions.
  • GETAPPROVERATTRIBUTES — Retrieves attributes associated with identified approvers.
  • GETAPPROVERLIST — Returns the list of approvers produced by evaluating the applicable rules against the test transaction.
  • GETTRANSACTIONPRODUCTIONS — Returns the production (non-test) transactions related to the current context.

Tables Accessed

The package references several tables through APPS synonyms. AME_TEST_TRANS_S stores the header records for test transactions created through this facility, while AME_TEST_TRANS_ATT_VALUES stores the attribute values associated with those test transactions. AME_ATTRIBUTES is the AME configuration table defining available attributes, their types, and mandatory status, and is queried to populate the attribute metadata returned by the GET procedures. DUAL is referenced for single-row value generation. PLITBLM is an Oracle-supplied package used for PL/SQL table (index-by table) manipulation, supporting the list-based out parameters used throughout the API.

Usage Notes

AME_TEST_PKG is primarily invoked by the AME Test Workbench, a set of Oracle Forms screens within the AME setup responsibility that allow administrators to define and run test transactions interactively. When a user creates a test transaction through the Workbench, the forms call INITIALIZETESTTRANS and the SET procedures to persist attribute values, then invoke GETAPPLICABLERULES and GETAPPROVERLIST to display the evaluated rules and resulting approvers. The package is not referenced by any other documented packages, confirming its role as a leaf-level utility rather than a shared library. It is documented with a "noship" header version, indicating it is not shipped as part of the standard seeded code stream but rather generated or maintained for the test facility. Custom code and diagnostics should treat this package as configuration-support tooling; it is not intended for integration into production approval processing, and its AUTHID CURRENT_USER declaration means callers must themselves hold the necessary privileges on the underlying AME tables.