Resolution:
Description:
= = = = = = =
BusinessConnect EDI protocol (BC EDI) 5.4 fails to convert a valid X12 document.

Environment:
= = = = = = =
This applies to all environments.


Symptoms:
= = = = = =
BC server logs will display the following stack trace:

2011 Jan 21 19:39:57:261 GMT -5 BW.BusinessConnect-Primary_Interior_A Error [bw.logger] BW-EXT-LOG-100000  Exception caught in EDI document parserException: com.tibco.ax.edi.parser.ParseException: Invalid interchange segment at position: 0
        at com.tibco.ax.edi.parser.EDIParser.a(EDIParser.java:188)
        at com.tibco.ax.edi.parser.EDIParser.parse(EDIParser.java:106)
        at com.tibco.ax.edi.runtime.pf.inbound.BMHPreProcessor.cm(BMHPreProcessor.java:663)
        at com.tibco.ax.edi.runtime.pf.inbound.BMHPreProcessor.cp(BMHPreProcessor.java:223)
        at com.tibco.ax.edi.runtime.pf.inbound.BMHPreProcessor.Start(BMHPreProcessor.java:64)
        at com.tibco.ax.edi.runtime.inbound.EDIBMHService.validateDocument(EDIBMHService.java:141)
        at com.tibco.ax.fw.runtime.inbound.impl.IBBMHService.preProcessMsg(IBBMHService.java:183)
        at com.tibco.ax.fw.runtime.impl.AbstractService.preProcessor(AbstractService.java:277)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.tibco.plugin.gateway.InvokeOperationActivity.sInvokeServiceOp(InvokeOperationActivity.java:246)
        at com.tibco.plugin.gateway.InvokeOperationActivity$OperationThread.run(InvokeOperationActivity.java:376)
        at com.tibco.pe.util.ThreadPool$ThreadPoolThread.run(ThreadPool.java:99)

Cause:
= = = =

The BC server is not able to fetch a list of valid EDI protocols from the BC database to compare the inbound document against.

Resolution:
= = = = = =

Verify that the EDI protocol has been properly activated and that the EDI_PLUGIN_INFO table has a valid list of EDI protocols (EDI-X12, EDI-EDIFACT etc.).  If not, deactivate and reactivate the EDI protocol to force the creation of this table.

EDI X12 data fails to parse with the exception, " Invalid interchange segment at position: 0".