Coding Services to Process Transaction and Group Documents
The logic that you design in your processing service (set in the Execute a Service action) depends on the type of document that Module for EDI generates when splitting the document from the original EDI document. This document type is specified in the EDITPA splitOption variable.
The following table explains the types of documents that the module creates depending on the value of the splitOption variable.
If the splitOption is... | Module for EDI creates... |
Transaction | Transaction, and Group and Interchange documents from the original EDI document. When the split document is of type: Transaction. Create a service that processes a single transaction set from the document. For example, create a document in a format used by an internal application based on the transaction set information. For information about how to create this service, see
Logic to Process a File Document. Group and interchange. Do not create a service because all processing for EDI documents is handled when processing Transaction documents. You could also set up processing rules specifically for group and Interchange documents that have no processing actions selected. Or, set up your processing rules so that Interchange documents fall through to the Default rule. |
Group | Group and Interchange documents from the original EDI document. When the split document is of type: Interchange. Do not create a service. Processing for the EDI document is handled when processing the Group document. You could also set up a processing rule specifically for the Interchange document that has no processing actions defined or set up your processing rules so that Interchange document falls through to the Default rule. |
Interchange | Interchange documents from the original EDI document. You would set the splitOption to Interchange if you want to simply deliver the EDI document to its receiver. |
The services you create can use information that is in the pipeline. For information about using data in the pipeline when your service is invoked, see
Information in the Pipeline that Your
Service Can Access.