Why do we need to have a seperate processing rule for the x12 Envelope document type …
The edi file is stored in TN by using the processing rules of X12 Group and X12 4010 850 document type …
Should we have 3 seperate processing rules??? If so why
Please help me sort out this basic Question…
Thanks in Advance
It depends on your application design. We use TN to extract EDIINT payloads and pass the whole envelope to our legacy translator, and also to wrap envelopes from our translator into AS2 before sending them to partners. Therefore we have two X12 envelope rules, one inbound and one outbound.
If and when we use decide to use wM as a translator, we’ll probably implement document level rules for translation and group level rules for functional acknowledgements.
Oh the joys of flexibility! You can process at various levels ISA, Group and Transaction depending on your implementation. We have our inbound split on the TPA set to Group for the data we translate in webMethods and Envelope for the data we pass back and forth to our legacy translator. Outbound we persist at transaction and ISA level only. It just depends on how you want to handle the data. Be aware that TN forces functional acknowledgements to split all the way out and ignores the TPA setting so you have to set up rules to ignore the levels you don’t want to handle.