BC EDI server or EdiConvert utility reports "No evelop" error in XML to EDI conversion. What could be the reason for this?
Article ID: KB0091856
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Resolution:
One reason for the "No envelop" error reported by BC or EdiConvert is an incorrect attribute in the XML sent to BC, that needs to be converted to EDI.
For example, this error is observed when XML corresponding to an 810 transaction is passed to XEngine with the "Standard" attribute for the <Transaction-810> element set to "EDI-X12".
The correct value for the "Standard" attribute in this case should have been "X12" and not "EDI-X12".
ie. the <Transaction-810> element should appear something like this:
<Transaction-810 XDataVersion="1.0" Standard="X12" Version="V4010" GUID="D1BA3617-CAB9-4121-A91D-29D36C861081" CreatedBy="XEngine" CreatedDate="2002-11-01T06:00:00">
One reason for the "No envelop" error reported by BC or EdiConvert is an incorrect attribute in the XML sent to BC, that needs to be converted to EDI.
For example, this error is observed when XML corresponding to an 810 transaction is passed to XEngine with the "Standard" attribute for the <Transaction-810> element set to "EDI-X12".
The correct value for the "Standard" attribute in this case should have been "X12" and not "EDI-X12".
ie. the <Transaction-810> element should appear something like this:
<Transaction-810 XDataVersion="1.0" Standard="X12" Version="V4010" GUID="D1BA3617-CAB9-4121-A91D-29D36C861081" CreatedBy="XEngine" CreatedDate="2002-11-01T06:00:00">
Issue/Introduction
BC EDI server or EdiConvert utility reports "No evelop" error in XML to EDI conversion. What could be the reason for this?
Environment
Product: TIBCO BusinessConnect EDI Protocol
Version: 2.x
OS: All
--------------------
Feedback
Yes
No
Powered by
