Trading Networks 10.3 | Administering and Monitoring B2B Transactions | webMethods Module for EDI | Batching EDI Documents | Extracting Transactions and Sorting the Batched Documents | When EDI Documents Have No Interchange or Transmission Header | Sorting Transactions when Queued Documents Have No Interchange Headers | Delimiters Associated with the Default Collection Area
 
Delimiters Associated with the Default Collection Area
The default collection area is associated with a set of delimiters.
The delimiters for the default collection area are determined as follows:
1. The batchProcess service uses the values from its delimiters input parameter.
2. If you do not specify a value for the delimiters input parameter, the batchProcess service uses its senderIDQualifier, senderID, receiverIDQualifier, and receiverID input parameters to locate the EDITPA values and uses the EDITPA delimiters variables.
3. If there are no values for the EDITPA delimiters variables in the partner-specific and default EDITPAs, the batchProcess service uses its own defaults.
For more information, see Delimiters Used for the Batch EDI Document.
The batchProcess service cannot replace delimiters before placing transactions in a collection area. When the interchange or transmission header is available, the batchProcess service can determine the delimiters used by the transaction from the queue, and as a result, can determine whether the transaction uses delimiters that are different from those used by the collection area. When the interchange or transmission header is not available, the batchProcess service is unable to determine the delimiters used by a transaction; therefore, the service cannot replace delimiters if they do not match.
Important:
If you place EDI documents into a scheduled delivery queue for batching and the EDI documents do not have interchange or transmission headers, you must ensure that the delimiters that the EDI documents use match the delimiters of the default collection area. If there is a delimiter mismatch, the batchProcess service will create a batch EDI document that is not valid and that will not be able to be processed.