Configuring Outbound Processing

If the channel does not contain a CONFIG specification in its PARAM setting, a default value of 'SWIFT_MT_MAPPERS_OUT' is used.

Outbound mapping determines the MT message type using the same configuration data used by inbound mapping. The lookup is a reverse of the inbound process. The business concept for the lookup is derived as follows:
  • the ISF business concept in the header for a single transaction mapping
  • the SUBTYPE of the Batch object for a batch mapping
If there are multiple outbound configurations that map to the target business concept, the first one located is used. There is no guarantee on the value configuration order.
The user must specify the name of the SWIFT release that is to be used by the outbound processing by one of two ways. The outbound mapper determines the name of the SWIFT release in the following order:
  • Add a MSG_DEF_SET=??? specification to the PARAM setting of the Channel record, where ??? is the name of the SWIFT release, fin2011 for example
  • Assign a value to the Message Set field of the Format record that is used by the Channel, fin2011 for example

Outbound mapping utilizes several other configuration setting to process outbound messages. The following table lists all outbound configuration settings.

Table 1. Outbound configuration settings
Key Name Description
SENDER The default Logical Terminal address to be used during outbound processing if one is not found in the message addenda, block 1.
RECEIVER The default Destination address to be used during outbound processing if one is not found in the message addenda, block 2.
PRIORITY The default message priority to use during outbound processing if one is not found in the message addenda, block 2.
DEL_MON The default message delivery monitoring setting to use during outbound processing if one is not found in the message addenda, block 2.
OBS_MON The default message obsolescence period to use during outbound processing if one is not found in the message addenda, block 2.
FIN???_PRE_BODY_MAPPER The pre-body mapper label name for a specific outbound message type. If unspecified the standard pre-body mapper label name is used.
FIN???_POST_BODY_MAPPER The post-body mapper label name for a specific outbound message type (FIN???). If unspecified the standard post-body mapper label name is used.
PRE_BODY_MAPPER The standard pre-body mapper label name for all outbound mapping types.
POST_BODY_MAPPER The standard post-body mapper label name for all outbound mapping types.
FIELD_LENGTH_ACTION The action to take when a field that is too long is encountered. Valid values are 'truncate' and 'abort'. The default is 'truncate'
FIELD_CHARSET_ACTION The action to take when a field has invalid character set data. Valid values are 'remove', 'replace' and 'abort'. The default is 'remove'.
REPLACEMENT_CHAR The character to use as a replacement when the invalid character set data option is specified as 'replace'. The default is '?'
FIN???_TXN_ROOT The ISF XML root element name to use for a specific message type. This name designates the 'body' node for the resulting message ISF XML.
TXN_ROOT The default ISF XML root element name to use for nonspecific message types. This name designates the default 'body' node for the resulting message ISF XML for all messages not specifically configured. If none is configured, the default is 'CreditTransfer'.