Submit Test EDI Data from EDI Home Page

, ,
1

EDI 6.1. I’m trying to submit an EDI document via Submit Test EDI Data on the EDI home page and it isn’t working. It recogizes the X12 envelope, but not the GS or transaction. Invalid data error (unexpected large segment) is issued. I copied and pasted the EDI data from TN in another environment. wm.tn/receive is in the URL.

It doesn’t seem to recognize the data. Any help is appreciated.

Thanks!

2

Could be the edi data delimters not formatted correctly from GS level,also when you copy/paste the EDI data it wont work as expected.So please use any hex editor like ultraedit and format the edi document with correct delimiters (record delimiters especially).

If you can pls post your edi data we will have a look whats wrong in it.

HTH,
RMG

3

Here’s the data. I copied it from the TN Document Details Content screen.

ISA00 00 ZZ11111111 082222222222 0601120553U004038500024410P>

~GSFA111111112222222222200601120553850002441X004030~ST9970001~AK1PO850002441~AK28500001~AK5A~AK9A111~SE60001~GE1850002441~IEA1*850002441~

4

Format it with ultraedit tool 997 should work…

I mean replace hex (~) record delimiter with newline all the places …and paste the new edi data in EDI submitter it should work.

I did it,try this out with exact sender/receiver/qualifiers

ISA00 00 ZZ11111111 082222222222 0601120553U004038500024410P>~
GSFA111111112222222222200601120553850002441X004030~
ST9970001~
AK1PO850002441~
AK28500001~
AK5A~
AK9A111~
SE60001~
GE1850002441~
IEA1*850002441~

HTH,
RMG

5

That worked, RMG. Thanks very much for your help.

6

From what I see, I believe the reason this didn’t work for you because there were 2 characters used as the terminator for the ISA, and one for every thing else. Unless its a display issue, you are using a CR and ~ after the ISA, and then just ~ afterwards. The data you submitted should also work if you remove all of the CR(LF) and used ONLY ~. your translator should be able to expect any delimiter you throw at it so long as it is consistent.
Once this flow sees the real world, and assuming you get data from multiple sources, you wont be able to count on any delimiter being the same from one interchange to the next.

7

Glad to know it worked.