Config / Mappings / General EDI Mapping Properties

General EDI Mapping Properties

We’ve described the general concept of EDI Properties before and how to access the header and line properties from the mapping. In this section we will look at some properties that are available in all mappings. We will later on have a look at the properties that are more specific to mapping formats, like XML etc.

EDI Mapping Header Properties

Documentation

Whenever a property shows the value in the “{“, “}” brackets, it is read-only. The documentation gives you two sub-properties:

Description

A multi-language enabled single line description that is shown to the user in the EDI Processing Queue and in the mapping list. Use this property to describe what the mapping is doing.

Long Description

A multi-line multi-language enabled property that allows you to document what the mapping is doing in detail. You can also use this for changelogs etc.

Error Handler

This property gives you a lot of control over what should happen, if there is an error during the mapping execution. You do not have to configure it. The property allows you to define a mapping that should be executed in case there are errors during the execution of the current mapping. From the error handler mapping you can access all named table views that are available in the current mapping. In addition you can access the queue by using the named table view PROCESSINGQUEUE. Linked to the EDI Processing Queue, you can access the table EDI Processing Log table with all the error information.

Careful, the Error Handler is also called if processing cannot be started due to table locks or other general system errors or license errors. You should ensure that the Error Handler does not call itself or other mappings in circular dependency.

EDI Mapping Line Properties

Type

The main property that is available on all mapping lines is the type. The selectable values may depend on the mapping format, but in general you can choose between:

Loop

The mapping line represents a structure that can be repeated. If you change the mapping line type to Loop other properties will become available. You want to choose the type Loop, if you want to repeat a section in a mapping or when you want to add a table for data access. We will discuss this line type for each converter and in the section read and write table data. A line of this type can have children, which are the structure that might be repeated.

Conditional

The mapping line represents a block in the mapping that is only executed based on a condition. The condition can be any function and for example, compare two values and only execute the child-lines, if the comparison returns true.

We will discuss this mapping line type in detail in the section handling conditional branches.

Data

This represents a data mapping line. A data mapping line represents data that is read or written or transferred between tables. The properties of a data mapping line depend on the selected mapping format. You can learn more about data mapping lines in the description of the converter you’re using.

Command

The module offers some general commands and some format specific commands. A command can, for example, check data, raise an error or break the processing. You can learn more about commands in the section working with commands.

Documentation

Whenever a property shows the value in the “{“, “}” brackets, it is read-only. The documentation gives you two sub-properties:

Description

A multi-language enabled single line description that is directly shown in the mapping. This can be used to document any important information that should be visible to users working in the mapping.

Long Description

A multi-line multi-language enabled property that allows you to document what the mapping line is doing in detail. You can also use this for changelogs etc.

WordPress Cookie Notice by Real Cookie Banner