Resolution:
Description:
============
After importing an EDI-TEXT schema into BusinessWorks using the BusinessConnect palette, the transaction schema does not appear under the body field of the Send Request/Notification task.

Environment:
============
- BusinessConnect EDI Protocol 5.2 and above
- BusinessWorks 5.4 and above


Symptoms:
========
- User creates a .ecs file for a Delimited Flat File in SpecBuilder, with an example transaction name of "ITEMOB".
- The XDATA 1.0 .xsd file is generated from the .ecs file, and both are uploaded into an EDI-TEXT transaction in the BusinessConnect GUI.
- The transaction is imported into BW, and the operation schema can be seen in the BC Schemas folder of BW
- In the Send Request/Notification task, the transaction is not listed.  Instead, a "textRawRequest" is displayed.

Cause:
======
The transaction is not named correctly in the .ecs file.  The name and ID in the .ecs file must match the transaction name defined in the Operation Editor for the EDI-TEXT document in order for the BW palette to place the transaction schema in the body section of the BW Send Request map.

Resolution:
===========

- Edit the .ecs file and correct the name and ID in the .ecs file.
- Generate the correct .xsd
- Re-import the .ecs file and .xsd file into BC.
- Re-import the operation into BW.