Why does the service fail? What are the error messages?
Remember the character is displayed differently depending on the system you’re on and the viewer you are using. All TN and EDI care about is the hex value of the Element Separator.
Provide some more details.
We are able to submit data to TN web console-WmTNforEDI.
Submission of one single transaction set passes thru but when we try to submit multiple data the processing fails.
When we do the same operation of submitting the data to the TN through a flow servce it fails again.
Kindly let us know if there are any details relating to setting that needs to be taken care of.
I believe that submitting content with content-type of application/edistream is not supported by TN (see discussion [url=“wmusers.com”]wmusers.com).
A project I’m working on has a partner that is using that same value for the sub-element delimiter. Try setting the content-encoding to ISO-8859-1, either on the submission side or if you have the bytes in your flow, set it in the bytesToString call.
Now we are able to submit multiple transactions through flow service by setting Content-type Application/EDIStream.But it fails whenever we tried to process document using wm.b2b.edi:envelopeProcess flow Service.
You document seems to error on the ISA01 which is usually 00.
However I see that your output is in XML format. The output from envelopeProcess Values, is a record (4.6) or document (6.0).
What exactly are you mapping into edidata?
You should be doing a bytesToString and map that output to edidata.
Maybe you can share the sequence of steps you are following after you document gets to TN.
Yes i am doing a bytesToString and map that output to edidata.Values, is a record(4.6), I am using recordTodocument to convert Values record into XML.This step i used for debugging purpose.
Here is the sequence of steps that execute after document gets to TN:
I see “³” in the data of the error message. So your ISA looks to IS to be something like:
ISA³00³ ³00³…
Thus it thinks that  is your element delimiter and ³ is the value of ISA01, which is not a valid value. You need to set the encoding correctly in your bytesToString call. Set it to ISO-8859-1 and ³ won’t be turned into 2 characters during the conversion from bytes to string.