This transaction is used to maintain field mappings for incoming messages.

This transaction allows fields in an incoming electronic message to be assigned to fields in the application. The field definition enables incoming messages to be mapped automatically to the fields in the related business transaction.

Alternative Mapping
To support especially the testing of incoming messages due to regulatory changes such as SWIFT 2018/2020 with different character sets (‘X’, ‘Z’) or mapping requirements for the same message type, it is possible to handle one alternative mapping per message type and target transaction.

The checkbox “Alternative mapping” will display the alternative mappings and allows the user to apply any changes if required. Depending on the SWIFT activation date (defined in Maintaining System Configuration), the application will use the correct mapping in the “Manager for Incoming Messages”.

With the introduction of New Sequences in Guarantees, many field tags have been used in both the sequences with the same name. To identify the same field tag in different sequence, Sequence (B, C) is added as a suffix to the Sub ID in the mapping.

Importing and exporting Field Mappings
Field mappings (also: field maps) can be imported or exported via  and Icons. The transaction “Export Field Mapping for Incoming Messages” is used for exporting, and the transaction “Import Field Mapping for Incoming Messages” is used for importing.

Follow the below GIF to get the process in detail :