If you want to process the information in the file of an inbound EDI document, for example to use information from file documents to form a document that is to go to a back-end system, you will primarily use the Execute a Service action. You create the service that the Execute a Service processing action invokes.

For the file and/or batch documents that result from the split, you would define processing rules that use the Execute a Service processing action to invoke a service that acts on the file and/or batch documents. For more information about how to create the services, see Coding Services to Process File and Batch Documents When Using TRADACOMS.

There is no need to process the transmission document, so you can define a processing rule that has no processing actions selected, which in effect causes Trading Networks to ignore the document. Alternatively, you can set up your processing rules to allow the Transmission document to fall through to the Default rule, which only sets the User Status system attribute of the document to IGNORED. If you use the Default rule, you do not need to define a processing rule for the transmission document.

If you are sending the inbound EDI document through Trading Networks to simply deliver it to a destination without processing the file, you will primarily use the Deliver Document By action, with the TRADACOMS/splitOption EDITPA variable set to Transmission. In this scenario, the only document sent to Trading Networks is the transmission document. For more information about delivering documents, see Forming EDI Documents to Send Outbound When Using Trading Networks .