I’m attempting to create outgoing EDI transactions. Part of our process involves generating the EDI string, and submitting it to TN, so that transactions can be traced from a single spot (TN)
Anyway, I translate the flatfile to a record structure, map it to the EDI record (4010 X12 856 in this case) then call convertToString, the add the envelopes. I submit the document to TN (having a problem getting that part working, so as a stop-gap I’m copying/pasting into the “test document submission” but that’s a problem for another day)
So, at this point, I’ve got ISA/GS/ST…/SE/GE/IEA in a string, and TN de-envelopes properly, so I see X12 Envelope, and X12 Group in TN. However, I don’t see the transaction sets, instead, I get a single Unknown document. I’ll post a small example here:
You need to make sure the document type for 856 is loaded in TN.
To load the document type go to [url]http://localhost:5555/WmEDIforTN[/url] and load the respective document types.
I wish it were that simple… The document type has been loaded into TN already. The only other thing I should mention is that this particular customer wants to see \u0061 (“a”) as their segment delimiter, so where you see carriage returns, my actual document has just “a”
Try loading the document first with default segment delimeter such as * and test it. if its successfully recognizing then you need to figure out how to resolve segment delimeter.
If you are using Ver 6.0 or later, then the TPA is used for determining to what level the EDI txns are persistend in TN.
TN creates a TPA called the Default TPA when you do the EDIfoTN installation. If you open the TPA, you will be see the “splitOption” field (persisting level) as “Group” in it. Hence, any EDI txn, you persist in TN, it will only get broken into Envelope and Group.
So, if you want to see your txn at the ST level, either you can change your default TPA and reload the package(seems like a bug as it needs to be reloaded) or create a partner specific TPA and change accordingly.
I am able to post the document you sent into my TN and see the transaction type 856 in TN. Are you able to see the transaction types for other EDI standards like 850 ie do you have problem with only 856.
Shouldn’t ISA12 be 00401 and GS08 be 004010? Just a shot in the dark but maybe de-enveloping is getting confused as to what version the transaction sets are, and thus the doc type names, if it is expecting 004010 instead of 4010.
I’ve had 850s and 855s get recognized without a hitch, just these 856’s are giving me trouble.
The transaction that you posted didn’t go through either - though I think it’s because of the formatting that the forum does to it. I’m going to try and re-install that document into TN, and try again.
Oh - and before I forget to mention it - I’m on 4.6
When I manually fixed the ISA that SS sent me (padding stuff to the correct length) then it recognized fine. I noticed the ISA difference, and made that quick change, but didn’t spot the GS difference.
Rob’s suggestion fixed the problem right up. Thanks again for all your help everyone!
