Configuring Inbound Processing

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

Inbound processing uses the three (3) digit message type found in block 2 of the incoming MT message to determine the business concept to use in the resulting ISF record. It prefixes the number with the constant 'FIN' to create a key for looking up the business concept. If a value is not found for this key name, then one is located for the Key 'MTXXX' for generic mapper processing. If a business concept is still not loaded, an error is posted and the mapping fails.

The user can control the SWIFT release that is to be used by the inbound processing by one of four ways. The inbound 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
  • Configure the FxhStandardsProcessing node globally and add the name of the SWIFT release to be used to category DNI_MSG_DEF_SET with key DNIFIN
  • Let the FxhStandardsProcessing node by default choose the SWIFT release that is active when the message is processed

Inbound mapping utilizes several other configuration settings to process messages. The following table contains a complete list of inbound message configuration settings.

Table 1. Inbound Configuration Settings
Key Name Description
FIN??? The business concept to apply to a specific inbound message type.
MTXXX The default business concept to apply if a specific FIN??? is not found for the inbound message type.
OBJ_CLASS The value to apply as the object class setting (column OBJ_CLASS) for the transaction resulting from the inbound message
FIN???_PRE_BODY_MAPPER The pre-body mapper label name for a specific inbound 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 inbound message type. If unspecified the standard post-body mapper label name is used.
PRE_BODY_MAPPER The standard pre-body mapper label name for all inbound message types.
POST_BODY_MAPPER The standard post-body mapper label name for all inbound message types.