When EDI Documents Have No Interchange or Transmission Header

Sorting Transactions when Queued Documents Have No Interchange Headers

You can place EDI documents that do not have interchange or TRADACOMS transmission headers in the queue. As described in How Documents Are Combined to Create the Batch EDI Document, the batchProcess service typically uses information from the interchange or transmission headers when sorting the documents. The following lists describes how the batchProcess service behaves when the interchange or transmission headers are not available.

For each transaction in an EDI document that does not have an interchange or transmission header:

1. The batchProcess service extracts a transaction from the EDI document.

2. The batchProcess service uses its senderIDQualifier, senderID, receiverIDQualifier, and receiverID input parameters to determine the EDITPA to use. For more information about the EDITPA variables that the batchProcess service uses, see Controlling How the batchProcess Service Forms the Batch Document.

3. The batchProcess service sorts the transactions. For more information, see Sorting Transactions when Queued Documents Have No Interchange Headers.

4. Each queued EDI document is associated with a Trading Networks delivery task. After all transactions for an EDI document have been extracted, the batchProcess service updates the task status. For more information, see Updating the Task Status and Publishing Documents for Failed Tasks.