Framework EDI is an EDI software tool that facilitates development of EDI
solutions. It enables you to create EDI applications quicker and more
accurately. This page explains how in some detail.
component Framework EDI includes a FREDI-COM and FREDI-NET component that can be
referenced by your programming language furnishing it with hundreds of well
tested, built-in functions for creating EDI applications.
The Framework EDI
component shields the programmer from the intricate and overwhelming details of
the EDI standard, and only exposes the basics structure to allow for business
mapping logic. For example:
Creating an EDI file To create a data segment, you would only need to call a command line to
create a segment, and then assign values to its data elements by writing the
Note that you do not even have to know
the details of the data elements such as its minimum length, nor do you have to spend development time
trying to correctly align data values
into the standard file format since that will all be done automatically for you.
Reading an EDI file To translate an EDI file, you simply look for the data segment, and then
interrogate its data elements to obtain their values by writing the following
If sSegmentID = "SEG" Then
var_dataelement1 = oSegment.DataElementValue(1)
var_dataelement3 = oSegment.DataElementValue(3)
So you need not have to bother about the exact positioning of the data values in the file layout - where they start and
where they end - because the component automatically extracts the values for you.
Validating an EDI file To validate an EDI file with the Framework EDI component, you simply load the SEF and
EDI files, and then interrogate the component objects for errors by doing the following:
'load sef file.
oEdiDoc.LoadSchema sSefFile, 0
'Load EDI file
Set oWarnings = oEdiDoc.GetWarnings
nWarningCount = oWarnings.Count
For i = 1 To nWarningCount
Set oWarning = oWarnings.Warning(i)
Therefore, the component
enables you to create a powerful EDI validation program without the incredible
task of having to know all the EDI standard specifications. Basically, the
only thing you need to know is
what version of the implementation guideline in the SEF is required to use
against the EDI file.
Acknowledging an EDI
file To acknowledge an EDI file, you simply enable a property of the
component, and then save the acknowledgment file as shown below:
Set oAck = oEdiDoc.GetAcknowledgment
oAck.EnableFunctionalAcknowledgment = True
The component will
automatically create the EDI acknowledgment file (997 or CONTRL) so that you do
not need to bother having to create it yourself.
The Framework EDI
Utilities The utilities packaged with the Framework EDI can help you troubleshoot and
maintain your EDI solution. The Framework EDI Utilities are:
The SEF Manager The SEF Manager allows you to view and edit SEF files. A SEF file is
the best method of deploying an implementation guideline because its data can be
parsed and used by a program (unlike pdf format); and it is small, manageable and
readable (unlike a database).
The eFileManager The eFileManager allows you to view EDI files in a more readable
format. Descriptions of segments, codes and data values that are not
normally included in an EDI file are displayed next to those units making the
EDI file more understandable.
The eAnalyzer The eAnalyzer validates EDI files of any size, and generates a report
that pin-points to errors in the EDI file. This utility can help you
troubleshoot problems in an EDI file, and can help you create a more accurate
EDI program that adheres to the standard.
A brief description of the Framework EDI component, and its utilities.