Trading Networks 10.3 | Administering and Monitoring B2B Transactions | webMethods Module for EDI | Including Documents in a Business Process | Overview
 
Overview
Using Software AG Designer (Designer), you design a process model that describes your business process (also called a conversation) that involves EDI documents. For an EDI document to be involved in a business process, it must have a conversation ID. A conversation ID is a identifier that is unique to an instance of a business process. All documents involved in the same instance of a business process contain the same conversation ID.
When webMethods Module for EDI (Module for EDI) receives an EDI document, it splits the original inbound EDI document based on the EDITPA splitOption variable. Module for EDI can split the original EDI document into Interchange, Group, and/or Transaction documents. The Interchange, Group, and/or Transaction documents are passed to a business process when they contain a conversation ID.
Module for EDI always assigns the Interchange and Group documents conversation IDs. Consequently, the Interchange and Group documents are always passed to Process Engine, which is the facility of Integration Server that executes and manages business processes in Integration Server.
Module for EDI only assigns a conversation ID to a Transaction document if you have created an instance ID query that identifies the value to set for the conversation ID. You define instance ID query for specific transaction sets (for example, X12 4010 850) using the WmEDIforTN home page.
Note:
You cannot process TRADACOMS documents in a business process.
For more information about processing EDI documents in business processes, including an illustration of how EDI documents are passed to a business process, see webMethods Module for EDI Concepts Guide .
For more information about using process models in Designer, see the webMethods BPM Process Development Help for your release.