Message Mappings (Overview)
In a message mapping, you assign a source and a target message type (according to the source and target operation of the operation mapping the message mapping is assigned to). Using a graphical editor, you can define the mapping between the source and target message type.
Java source code is generated from the message mapping and compiled in a .jar file. At runtime, the .jar file is executed.
The graphical mapping editor is composed of three main areas (see Message Mappings (Detailed Information) ). The left area shows the structure of the source message assigned to the message mapping, the right area the structure of the target message. Below this is the data flow editor.
If you have created the message mapping based on an operation mapping, the source and target structures are already loaded according to the operations you have chosen in the operation mapping.
You use the graphical editor to do the following:
Design a structure mapping between the elements of the source and the target structure
Apply a function to transform the source and target fields into each other, if necessary
A simple assignment between source and target fields is generally not sufficient.
In the data flow editor, you define target field mappings. A target field mapping describes how one or more source fields are mapped to a target field.
A message mapping is constructed from individual target field mappings.
The following kinds of function can be used to specify target field mappings:
These functions are already available in the mapping editor. There are several kinds of standard function available in the mapping editor. For text mappings, for example, these include simple calculations or Boolean operations, and date format conversions.
You can define your own functions if standard functions do not fulfill your requirements.
More information: User-Defined Functions and Function Libraries
The following content is not part of SAP product documentation. For more information, see the following disclaimer .