Showing posts with label APIs. Show all posts
Showing posts with label APIs. Show all posts

Oracle Purchasing AME Tables and APIs

 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 Type as 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

Applying Workflow Engine APIs to Function Activities

Function activities are stored in PL/SQL procedures. There is a standard API format for all stored procedures called by function activities. When the Workflow Engine executes the function activity, the Workflow Engine passes four input variables and, if a result type is set up for the activity, expects one output variable in return. Output variables are: