Liquid XML Studio 2019
EDI Target
Data Mapping > Data Mapper Functions > By Category > EDI > EDI Target

Function Name
EDI Data Target
Category
EDI
Icon
Description
Allows data to be written to an EDI document.
Inputs
Filename Source file to read data from, if this input is not connected then the filename provided in the 'Default Source File' property
EDI data Items Segments and element corresponding to the structure of the selected EDI standard.
Outputs
Data The raw EDI data (does not need to be connected)
Properties
Default Target Uri The filename the EDI document will be written to (Ignored if the Filename input is connected or the Data output is connected).
Execution Order If the transform contains multiple Output Components then this determines the order in which they are executed

Usage

The EDI Data target makes it possible to create EDI documents within the Data Mapper.

Creating an EDI data source

To begin, drag the EDI Source component from the EDI section of the Component Palette onto a new Data Mapper file.

This will cause the wizard to launch

This wizard page makes it possible to select the required EDI standard.

 

Once a standard has been selected the next button is enabled and we can move onto the next wizard page.

The default terminators and separators will be selected based on the standard selected on the previous page.

These are common default values, however the files you need to write may use different values and so you should change these values as appropriate.

These values are set when you first run the Wizard, however you can change them inside the Data Mapper by selecting the Component and selecting Properties from the right click menu.

Write End of Line

When checked, each segment is written to a new line.

If it is not checked, the entire EDI document is written onto a single line.

Write Missing Trailing Components

When checked, separators are added for all empty components within an element. 

If it is not checked, then trailing empty components are omitted.

Write Missing Trailing Elements

When checked, empty fields and separators are added for all empty Elements within a segment.

If it is not checked, then trailing empty elements are omitted.

Pad Fields to Minimum Length (0s and spaces)

When checked, all fields (Elements and Components) are padded to the Minimum Length specified in the standard. Text fields are right padded with spaces, and numeric fields are left padded with zeros.

If it is not checked, then the fields are written using the specified values and any padding should be done using components within the Data Mapper transform before connecting to the EDI Target Component.

Pad Empty Fields to Minimum Length

When checked, all empty fields (Elements and Components) are padded to the Minimum Length specified in the standard using spaces.

If it is not checked, then the fields are written with empty values and any padding should be done using components within the Data Mapper transform before connecting to the EDI Target Component.

Truncate Fields to Minimum Length (0s and spaces)

When checked, all fields (Elements and Components) are truncated by removing zeros and spaces to the Minimum Length specified in the standard. Text fields have trailing spaces truncated from the right, and numeric fields have leading zeros truncated from the left.

If it is not checked, then the fields are written using the specified values and any truncating should be done using components within the Data Mapper transform before connecting to the EDI Target Component.

Truncate Fields to Maximum Length

When checked, all fields (Elements and Components) are truncated to the Maximum Length specified in the standard. Text fields are truncated from the right, and numeric fields are truncated from the left.

If it is not checked, then the fields are written using the specified values and any truncating should be done using components within the Data Mapper transform before connecting to the EDI Target Component.

Caution, truncating values may lead to loss of data.

 

 

When the wizard is complete pressing the Finish button will created the EDI Source on the transform.

Inputs

The component has a root input called 'Filename', each value provided to this is treated as a filename and a new EDI document is created.

If the 'Filename' input (and the 'Data' Output) is not connected then the "Default Target Uri" is used (see properties window).

The child inputs are all specific to the EDI standard you selected when the component was created.

Outputs

The Data output returns the resulting EDI document as a string. This allows it to be consumed by other components rather than just being written to a file.

If the Data output is connected the Default Target Uri property is ignored.

It is an error to have connections to BOTH the Data output and the Filename input.

 

See Also