X12Reader reads data in X12 format. All X12 versions from 003030 to 007040 are supported.

X12Reader does not propagate metadata.

X12Reader has a metadata template on its output port available.

Metadata on optional input port must contain string, byte or cbyte field.

Metadata on each output port does not need to be the same.

Each metadata can use Autofilling Functions.

X12Reader reads data from X12 files using SAX technology.

X12Reader can read individual values or entire subtrees of the X12 structure. Individual values can be converted to any field type. Subtrees can be converted to variant fields. When reading into variant fields, all data types in the field will be string type.

Using X12Reader is very similar to XMLExtract. Attributes X12 version and X12 transaction set define the expected structure (schema) of the input data. The schema is generated automatically.

Specifying X12 version and X12 transaction set is optional. You can leave both attributes empty, in which case X12Reader will read entire input data into a single variant field on first output port. Defining a mapping is not possible in this case.

X12Reader Mapping Editor serves to define mapping from X12 transaction set structure to one or more output ports by drag and drop.

To be able to use the editor you have to specify X12 version and X12 transaction set. The schema is created internally and cannot be modified.

Any other operations to set up mapping are described in above mentioned XMLExtract.

In X12Reader, you can map input fields to the output in the same way as you map transaction set fields. The input field mapping works in all three processing modes.

Mapping parts of X12 transaction set onto output metadata. It is possible to map a whole transaction set or its part onto variant field or to map individual values to fields of other data types.