Skip to main content
Skip table of contents

Terms & reserved variable names


The following terms are used in this manual. This statement is intended to give an overview .


Mapping Definition

A mapping definition is the mapping itself. It is saved as an XML file.


A mapping is basically the connection between a source data field and a target data field. Under certain conditions, a source data field can be used to trigger certain tasks without assigning a value to a target data field.

Mapping Group

Mappings are organized in groups. The groups will be displayed in the editor window one at a time. Grouping elements usually count to higher ordering units (e.g. data elements of EDIFACT are grouped by their segment).

The first element at the left side is the element that defines the group.

Source Node

The source data field whose value should be transferred into the target data structure.

Beneath the group defining element are the source nodes (orange).

Additional NodeA source node, which is bound to another source node instead of being directly mapped. The purpose of additional nodes lies in the linking of several source date fields to a target value. This linking is initiated by the appearance of the linked source data field.
Target Node

The target data field takes the (possibly tested and/or processed) value.

On the right are the target nodes (blue).

A task represents a processing unit that fulfills a defined task. Depending on their type, tasks can contain a varying number of parameters (or no parameters) that determine their behavior. Tasks are organized in groups (e.g. mathematical and key string oriented tasks). A list of tasks that will be processed one after the other can be added to a mapping.
Tasks are in front of the target node and have a white background.

A condition tests whether a particular situation is correct or not. A mapping will be run or not, depending on the results.
Several condition tests can be merged into one single test with an AND/OR connection.
Conditions can also be grouped. A group of conditions can be merged with other groups or single conditions by using an AND/OR connection. Groups can also contain further groups.

Group Condition

In the dialog for creating conditions, individual conditions can be grouped. This is equivalent to setting brackets.

Example: group1( a = 3 and b = 3) or group2( a = 2 and b = 2)

DefaultsDefaults are fixed points within a mapping that are used to pre-set target values of target data fields. Defaults can be changed during the mapping process.

Predefined reserved variable names

variable name
$CURRENT Includes the value of the source data element which is currently to be mapped and passed to the target page. The value contained at the time of handover, which can be changed on the tasks or by setting a constant value. This value is passed to the target module as a value for the data element to be fillled.
$ORIGINAL Includes the original value of the source data element. This should not be changed within the mapping, because it serves as a kind of protection, so that you can always get to the original value.

This variable refers to the left comparison value of a condition and can be altered by tasks (if necessary).
If this value in $CONDITIONLEFT is the source value (so no referential value or the value of a variable), than the modified value is NOT taken in $CURRENT. If the changed value retained, the value of $CONDITIONLEFT of the variables $CURRENT must be assigned.
The value of $ CONDITION LEFT is reset at the beginning of each condition.

$CONDITIONRIGHT Behaves as $ CONDITION LEFT, with the only difference that it receives the reference value of the right side.


// is a module zip package

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.