The EDI for TN module performs deenveloping (also known as splitting). The normal behavior is to create TN transactions for each interchange, group and transaction set found within the data submitted to receive. If you submit an EDIFACT/EANCOM document containing one order, you will see the interchange envelope and the ORDERS document in TN. If you submit EANCOM data, say with 1 interchange, 2 groups (not typically used in EDIFACT) with 3 orders each, you’ll see 6 items in TN. You set up rules to process the particular document that you want (e.g. ignore the interchange and groups, process the transaction sets).
A common way to process these is to ignore the envelopes and to process the individual transaction sets. I prefer this approach as TN handles all the deenveloping, acking, etc.
Another way used by some is to configure the TPA(s) to split at the interchange (which is actually no split at all) or group level. Then in the service invoked by the rule you set up, you process the transaction sets as a group. This approach is less common since it is rare that a group of docs must be processeed together–splitting and processing individual documents is usually okay.
What do you mean by a “much cleaner way” to process EDI? Splitting to the transaction set level and tracking progress of each envelope and transaction set seems to me to be the “right way” to process EDI.
#webMethods#Integration-Server-and-ESB#B2B-Integration