Step | Description |
1 | For each collection area, the batchProcess service combines the transactions in the collection area. Each collection becomes an interchange in the final EDI batch document, with each subcollection a group within the interchange. |
2 | The batchProcess service obtains the EDITPA information for the sender/receiver associated with the collection area. It uses information associated with the collection area, the subcollections, and the EDITPA to create the interchange and group headers as follows:  Uses the sender/receiver, EDI standard, production mode, and delimiters associated with the collection area for the interchange headers.Obtains fields for the interchange header from the EDITPA ICHeaderInfo variables. If an ICHeaderInfo EDITPA variable does not have a value, the batchProcess service uses the corresponding value from the interchange header of the original document. For more information about the ICheaderInfo variables, see ICheaderInfo Variables.Uses the sender/receiver, group type, version of the EDI standard associated with a subcollection for a group header.Obtains the value of the GS07 field (for ANSI X12) from the EDITPA ICHeaderInfo/GS/GS07 variable. If this variable does not have a value, it uses the GS07 from the original EDI document. For more information, see ICheaderInfo Variables. |
3 | After recombining the information for all collection areas, the batchProcess service creates a BizDocEnvelope for the final batch EDI document. The batchProcess service sets the sender and receiver for the BizDocEnvelope to the sender/receiver identified in its senderIDQualifier, senderID, receiverIDQualifier, and receiverID input parameters. It then sends the BizDocEnvelope to Trading Networks processing rules for routing. Note: If you use Sender or Receiver criteria in the processing rule to route the final batch EDI document, identify the final batch EDI document using the sender/receiver of the BizDocEnvelope. |