Main Tables:
· ame_calling_apps – This table stores application_name and transaction_type_id for a particular document_type.
For example: For Purchase Requisition, this table has transaction_type_id of PURCHASE_REQ, which is a seeded value. Only if we setup the Approval Transaction Typeas PURCHASE_REQ for Purchasing Requisition document type(as seen in setup screen shot in the previous slide), AME will be called for building approver list
· ame_actions
· ame_action_types
· ame_action_type_usages
· ame_approvals_history
· ame_approval_groups
· ame_approval_group_items
· ame_approval_group_members
· ame_attributes
· ame_attribute_usages
· ame_conditions
· ame_condition_usages
Main APIs:
· ame_api2.getallapprovers7
· ame_api2.getnextapprovers4
· ame_api2.updateapprovalstatus
· ame_api3.suppressapprover
· ame_engine