Resolution:
DESCRIPTION
==============
A BusinessWorks project with a BusinessConnect palette throws a parser error when processing a RESPONDER.REQUEST message when using an XDATA 2.0 .xsd.  The parser error looks like the following:

2010 Mar 10 09:24:27:077 GMT -8 BW.wdSLSRPT Error [BW_Plugin] BW-XML-100013 Job-1000 Error in [Process Definition.process/Parse XML]
A validation occurred while parsing:  validation error: no declaration for element "{http://www.edifecs.com/xdata/100}Transaction-SLSRPT"   ({com.tibco.xml.validation}COMPLEX_E_MISSING_ELEMENT_DECLARATION) at /Transaction-SLSRPT[1]
com.tibco.xml.validation.exception.i: no declaration for element "{http://www.edifecs.com/xdata/100}Transaction-SLSRPT"

The error message indicates that BC is sending the transaction payload in XDATA 1.0 format rather than XDATA 2.0 format.

Environment
==============
EDI 5.4 using XDATA 2.0 .xsds.


Cause
=====
The error message indicates that BC is sending the transaction payload in XDATA 1.0 format rather than XDATA 2.0 format.

Resolution
=========
In order for BC to generate data using the XDATA 2.0 .xsd format, you must do the following:

1).  Open the .ecs file in SpecBuilder.
2).  Export the .xsd using the XDATA 2.0 format.
3).  Save the .ecs file.  The XDATA 2.0 setting will now be included in the .ecs file for use by the XEngine in BC.
4).  Upload the newly saved .ecs and .xsd files in BC
5).  Refresh the transaction schema in BW.

After importing the new .ecs file, the BC Xengine will generate the XML in the correct format.

A BusinessWorks project with the BusinessConnect palette throws a parser error when processing a RESPONDER.REQUEST message when using an XDATA 2.0 .xsd