If you want to process transactions from an inbound EDI document, for example, to transform that information into a format that is readable by an internal (back-end) system, you will primarily use the Execute a Service action. You must create the service that the Execute a Service processing action invokes.

To process the Transaction and/or Group documents from the split, you would assign the appropriate processing rules in the Execute a Service processing action. For more information about how to create the services, see Coding Services to Process Transaction and Group Documents.

For the Interchange document, you could define a processing rule with no processing actions selected. This causes Trading Networks to ignore the document because there is no need to process it. Alternatively, you could define processing rules that allow the Interchange 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 Interchange document.

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