B2B Integration 10.4 | 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 | Subcollections when there Are No Headers (Groups in the Final Batch EDI Document)
 
Subcollections when there Are No Headers (Groups in the Final Batch EDI Document)
The batchProcess further sorts the transaction into a subcollection. Each subcollection becomes a group (or a TRADACOMS batch) in the final batch EDI document. If the EDI document has group headers, the batchProcess service sorts the transaction into the subcollection as described in Subcollections Representing a Group in the Final Batch EDI Document. If the EDI document does not have group headers, it uses the following:
Item
From Where It Is Obtained
Group type
Determined based on the type of transaction; for example, if the transaction is an ANSI X12 850 (which is a purchase order), the batchProcess service uses the group type PO
Version of the EDI standard
(for example, 4010)
Obtained from the version input parameter of the batchProcess service
Group sender/receiver
Obtained from the following inputs of the batchProcess service: senderID and receiverID
Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release