Alex,
Which version of IS/TN/EDIModule you are working on?
you can use either of these services to route the EDI document to TN
(wm.tn.doc.xml:routeXML,wm.tn:receive)services.I prefer always routeXML service,since tn:receive is a gateway service but you can use this in the flow either.
For both the services Input will be the Node object.
If you have made the EDIFACT document string wrapped with (UNB,UNH,UNT,UNZ)segments
So convert the final edi string to Node using (XMLStringToNode or StringToDocument)this gives output Node and this will map to input of routeXML or tn:receive service and routes it to TN.
(So now you will get rid of the above thrown /node absent error.)
Before pushing the EDIFACT document to TN,make sure in the TN whether the particular EDIFACT documentType is installed and enabled.
Note:Please use the keyword search functionality provided in this site,since lot of threads been discussed on the procedure of routing the EDI file to TN.you will suprise after seeing the results
HTH,
RMG
#edi#Integration-Server-and-ESB#webMethods