Configuring EDI-TEXT files with BusinessConnect EDI Protocol powered by Instream 6.3.

Configuring EDI-TEXT files with BusinessConnect EDI Protocol powered by Instream 6.3.

book

Article ID: KB0085081

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect EDI Protocol Powered by Instream -
Not Applicable -

Description

Resolution:
Description:
============
When configuring EDIFACT or X12 (which is my case) in the Operations Editor, there is the option to select either "EDI to XML" or "EDI to TEXT" conversion.  The EDI-TEXT option requires different file options.  What are these file options?

Environment:
===========
BusinessConnect EDI 6.3.x Protocol powered by Instream

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

For “EDI to TEXT” conversions, the “Foresight Translator tool”, a stand-alone UI tool for creating maps is needed to configure the necessary maps for EDI<-&gtTEXT conversion.

EDI – TEXT involves 3 components for creation of a TEXT file based on an EDI source guideline.

EDI source guideline which is a X12 or EDIFACT document (either using standard guidelines from EDISIM or customized using EDISIM)

TEXT target guideline which is created using EDISIM using either the DELIM or FIXED length guideline format

Map files to create source to target mappings.  The Foresight Translator Tool should be used to map EDI source to TEXT target guideline.

The Foresight Translator tools is available via a separate license from TIBCO, and is required for use with the EDI-TEXT protocol with EDI 6.3.

Issue/Introduction

Configuring EDI-TEXT files with BusinessConnect EDI Protocol powered by Instream 6.3.