Module for EDI 9.12 | Understanding EDI Concepts | Forming EDI Documents and Sending Them Outbound | Submitting the Outbound EDI Document to Trading Networks to Deliver It
 
Submitting the Outbound EDI Document to Trading Networks to Deliver It
The following diagram illustrates the process of receiving an internal-format document and using a processing rule to invoke a service that you create to:
*Form the outbound EDI document based on the internal-format document.
*Submit the outbound EDI document back to Trading Networks document recognition to process the outbound EDI document through Trading Networks to deliver it.
Step
Description
1
A back-end system or client sends an internal-format document to the webMethods Integration Server invoking the wm.tn:receive service to send the document to Trading Networks.
2
Trading Networks matches the internal-format document to its TN document types. You need to create a TN document type that will match your internal-format. For more information about creating TN document types, see the webMethods Trading Networks Administrator’s Guide for your release.
After selecting the appropriate TN document type, Trading Networks forms the BizDocEnvelope that contains the internal-format document as the content and places the BizDocEnvelope in the pipeline in the bizdoc variable.
3
Trading Networks searches its processing rules to find the appropriate rule to use to process the internal-format document. You should create a processing rule that uses the Execute a Service processing action to invoke a service that you create to form the EDI document. For more information about creating this service, see Creating a Service for Forming an Outbound EDI Document.
4
The service you create to form the EDI document executes. After forming the EDI document, your service invokes the wm.tn.doc.xml:routeXml service to submit the outbound EDI document back into Trading Networks document recognition.
5
Trading Networks document recognition passes the document to the EDI recognizer. The EDI recognizer executes as described in Initial Processing of the EDI Recognizer. That means it obtains EDITPA information and splits the document based on the split option in the EDITPA.
For outbound documents, set the split option to:
* Group if you want the Module for EDI to perform FA reconciliation in addition to delivering the outbound EDI document.
* Interchange if you just want to deliver the outbound EDI document.
Module for EDI selects the TN document type for the outbound EDI document, forms the BizDocEnvelope that contains the outbound EDI document as the content, and places the BizDocEnvelope in the pipeline in the bizdoc variable.
6
Trading Networks searches its processing rules again to find the appropriate rule to use to deliver the outbound EDI document. You need to create a processing rule for the EDI document that does one of the following:
*Uses the Execute a Service processing action that invokes a service that you created to deliver the EDI document.
-OR-
*Uses the Deliver Document By processing action to:
* Send the EDI document to a VAN. For more information, see Outbound Processing: Delivering Documents to VANs.
* Batch the EDI document for delivery. For more information, see Batching Outbound EDI Documents.