UNA Segment Required for TN Doc Recognition?

[joer (joer@ebrsi.com joer@ebrsi.com)]

Is it the case that EDIFACT EDI documents submitted to TN must include the UNA Segment (Service String Advice)?

If I do not include this segment in my tests, the document is not recognized by TN. If I add the UNA segment, everything works as expected.

[gupta_r.17495]

I believe its not mandatory segment for TN recognizion,but this is required segment for VAN providers…Actually it just indicates about the delimeters contained in the edifact document.

I have submitted documents with out UNA before UNB it worked fine…Please try submitting with EDI submiter of the WmEDI adming webpage.

HTH,
RMG

[ychang]

@jbr

Is it the case that EDIFACT EDI documents submitted to TN must include the UNA Segment (Service String Advice)?

If I do not include this segment in my tests, the document is not recognized by TN. If I add the UNA segment, everything works as expected.

It depends on what exactly you’re doing. If you’re submitting the doc to TN for outbound batching, then you probably don’t want TN to do its recognition and (optionally) transaction splits. What you can do then is to construct the bizDoc yourself (createBizDocEnvelope, addContentPart) and persist or route the bizDoc to TN.

HTH