TN adds unwanted UNE segment to EANCOM document

My flow service generates and submits an EANCOM D96A envelope. TN processes the payload and creates individual ORDRSP documents. The envelope has no UNG/UNE group segments. The ORDRSPs have a UNE segment I don’t want. They do not contain a corresponding UNG segment in the header. I’m using TN 6.1. Has anyone seen this? Thanks,

Tim

Tim,

If no UNG segment then having UNE (Trailer)is not a valid message.Is it not giving validation error in TN?

HTH,
RMG

It is strange, but I get no validation errors or any other errors. There’s nothing in the server log (log level 4) or error log either. My EDI analyzer software flags it as a non-fatal error and ignores it, but I’d like to correct it if possible. Could the template be somehow corrupt? Thanks,

Tim

Apparently, no error is thrown because doing a convert to values for the ORDRSP document type causes the envelope segments to be dropped, including the bad UNE. Not sure why TN is adding that orphan segment, but I’d sure like to fix it.

Tim

As final alternative Please check with WM tech support as well for this problem and keep us posted.

Thanks,

Tim I think there’s a fix for this. I saw this at a client last winter but unfortunately I can remember it. Check Advantage.

RMG and Chris,

Thanks for the advice. There is a fix: WmEDIforTN_6-1_Fix10. Here’s a link to a support request:

http://advantage.webmethods.com/cgi-bin/advantage/main.jsp?w=0&targChanId=knowledgebase&oid=1612092417

This took care of the problem. Thanks again,

Tim

Tim,

Thanks for the update though.