Resolution:
BC EDI Protocol uses a tool, known as SpecBuilder, to design transaction specifications for X12 and EDIFACT transactions that will be used with it.  SpecBuilder creates two files that are needed for every transaction;  an .ecs file that governs the transformation and validation rules for EDI to XML and XML to EDI conversion within BC, and an .xsd file, which is used by the BW-BC palette to define the schema that is to be populated within the BW private process.

To help with the creation of these files, it is helpful to have a sample transaction file that can be used as a template.

1.  To create a .ecs file, open SpecBuilder and click on the New Document icon.  A wizard will appear that will walk you through the steps of creating the .ecs file.  

Do not specify envelope segments as part of your new file (the envelope segments are handled at by the group and interchange level guidelines which are built into BC).  Envelope segments are the ISA, GS, GE, and IEA segments in X12, and the UNB, UNG, UNE, and UNZ segments in EDIFACT.

Alternately, you can use the Analyzer wizard to analyze your sample document and create a guideline.  Again, do not use envelope segments in your guideline.

2.  Modify the guideline to suit your specific application using the SpecBuilder editor.

3.  When complete, save the .ecs file for uploading into an EDI transaction.

4.  Before closing, export the guideline as an XDATA 1.0 .xsd file using the the  File | Export command in SpecBuilder.  BC and BW only support the XDATA 1.0 specification.  

5.  In the Administrator&gtBusinessConnect&gtOperations Editor, create a transaction under the appropriate Interchange and Group levels.  Upload the .ecs file into the transaction, and upload the .xsd file into the transaction for use by the BW-BC palette.  The BW-BC palette will fetch the .xsd when you import it via the BC Connection resource in Designer.

Process for creation of .ecs files for EDI transactions