Introduction

• Lines Without Dependencies

• Lines With Dependencies

GUI

(1) If this checkbox is set, the source fields will be checked against the stored format templates during parsing. If a value violates the format template of the source field or exceeds the field length, an error is generated. If errors occur, the profile will not terminate instantly but only after phase 2 or after 50 errors. Attention: This feature puts a strain on performance and should only be used when absolutely necessary.

(2) Specifies whether to check the number of repetitions of fields and nodes in the source tree.

(3) Whitespaces at the beginning and end of quoted field values are removed. Example: "33 ";" 44";" 55 "; "66 77 " becomes "33"; "44"; "55"; "66 77".

(4) Specifies whether the data should be parsed into a single record. If this checkbox is set, the parser is prevented from creating multiple records.

(5) Row-wise or column-by-column arrangement of the data in the file.

(6) The delimiter between columns or rows (see item 5). Usually, for a row-wise arrangement, new line is used. The delimiter may occur in the text, but the affected text must then be surrounded by the CSV quoting character (7).

(7) See (6).

(8) Specifies at which line the data to be used starts. This setting is used to ignore a certain number of lines. The value is used if (5) is set to a row-wise arrangement of the input data. Empty lines are not counted. Note: See also system variable VAR_SYS_LINES.

(9) Specifies at which column the data to be used starts. This setting is used to ignore a certain number of columns. The value is used if (5) is set to a column-by-column arrangement of the input data. Empty columns are not counted.

(10) Specifies up to which line the data should be read. The subsequent lines in the file are then ignored.

(11) Specifies how many lines should be skipped after a dataset.

(12) If set, the CSV input document is expected to be as it is generated by the Microsoft Excel CSV export.

(13) If this checkbox is set, line breaks in columns will be removed.

(14) Indicates whether identical record types occur multiple times (nested), but do not belong to the same node. Example:

The first C dataset should be parsed into a separate node, the subsequent C datasets each in a D/C node. So the CSV parser will work similar to an EDIFACT parser here, i.e. it goes through the structure from top to bottom and remembers where it is. Once the lower D/C node has been entered, nothing will be inserted into the upper C node anymore. Note: The set checkbox also affects when the parser creates a new record.