Delimited report files

To get an asterisk-delimited report instead of an XML report, use –fd on the Docsplitter command line (see page Command Line - Parameters).

The report includes key information about the EDI document that was split. You can parse it with one of your application programs or bring it into a desktop application like a spreadsheet.

If an error is detected during validation, the delimited report will contain a record that starts with the word ERROR.

The next line is often an EMSG record that describes the error. If specific erroneous data is available, there will also be an EDAT record that shows the invalid data. These two records are simply echoed from validation’s detail file.

For example, this segment in the EDI input file has an error:

CN1~01~HDG50.00~.10~12345678900987654321768958473~.25~VERSION IDENTIFIER!

It might prompt these lines in a Docsplitter delimited report:

ERROR*10626*190*3*1*2300*CN1*782**187*2*
EMSG*Syntax Error for CN102 (D.E. 782) at col. 8 (R 1/10) "HDG50.00": Real value required
EDAT*HDG50.00

The error record contains some or all of the attributes listed below, with delimiters maintaining the positions:

Where:

1	record tag
2	number
3	line number
4	severity
5	type
6	loop_id
7	seg_id
8	elem_id
9	comp_id
10	seg_pos
11	elem_pos
12	comp_pos

Delimited Fatal Records

A fatal error will look like this:

FATAL*Error occurred while creating Node Tree. Error occurred while processing Record
DTL          28        GS 480             2 8           0                    10614 4    01 8 1007     122                         
DocSplitter encountered an Envelope Level Error with a Severity of Fatal.

The DTL record format is documented in TIB_fsp-instream_<n.n.n>_UsersGuide.pdf.