MT196 mapper

The MT196 mappers are used by the channel for sending and receiving answer messages for High Value Payments.

Overview

The MT196 mappers are a pair of inbound and outbound mappers.

MT196 inbound mapper: This mapper maps the MT messages to ISF messages. The default mapper name is MTToISFMapper.
MT196 outbound mapper: This mapper maps the ISF messages to MT messages. The default mapper name is ISFToMTMapper.

The details of the mapping specification for these mappers are in separate documentation that is included in the documentation fix pack for High Value Payments. For more information about getting the documentation fix pack, see FTM support links for High Value Payments.

The inbound and outbound MT196 mappers can also be used along with the High Value Payments business application header mapper or the ISO message router mapper. For more information, see High Value Payments business application header mapper and ISO message router mapper.

Inbound mapper

The CONFIG=entry channel parameter is required for the inbound mapper. The mapper uses this parameter to locate the <msgTypeCfg> entry with a <type> child element that contains FIN196 in the value table. The <msgTypeCfg> entry contains the configuration parameters for the inbound mapper.

For example, the default Message From channel is configured with a CONFIG=HVP_MAP_CFG_SWIFT_MT parameter. When an MT196 message is received, the mapper searches the value table to find the <msgTypeCfg> entry to use for the message. It searches for a value table entry that meets the following conditions.

The category is HVP_MAP_CFG_SWIFT_MT.
The <msgTypeCfg> entry has a <type> child element with the value of FIN196.

The default <msgTypeCfg> entry for HVP_MAP_CFG_SWIFT_MT is shown in the following example.

<msgTypeCfg>
   <class>MT196</class>
   <subType>HVP_FROM_CDTR_ROI</subType>
   <extendedCfg>
      <name>MASTER_FLAG</name>
      <value>Y</value>
   </extendedCfg>
   <extendedCfg>
      <name>SUBTYPE_RJCR</name>
      <value>_REJECT</value>
   </extendedCfg>
   <extendedCfg>
      <name>SUBTYPE_PDCR</name>
      <value>_ACCEPT</value>
   </extendedCfg>
   <extendedCfg>
      <name>SUBTYPE_FTNA</name>
      <value>_ACCEPT</value>
   </extendedCfg>
   <extendedCfg>
      <name>SUBTYPE_CNCL</name>
      <value>_ACCEPT_RETURN</value>
   </extendedCfg>
   <mapName>FXH_FIN196ToISFBodyMapper_fin2021</mapName>
   <type>FIN196</type>
</msgTypeCfg>

The following table shows the default configuration parameters for channels that use the MT196 inbound mapper.

Table 1. Default configuration parameters for channels that use the MT196 inbound mapper
Category	Class	SubType	MASTER_FLAG
`HVP_MAP_CFG_SWIFT_MT`	`MT196`	`HVP_FROM_CDTR_ROI`	`Y`

The inbound mapper handles the datetime elements by using the following rules.

If a time zone offset is included in the datetime value, the datetime value is mapped to ISF with the UTC time zone.
If a time zone offset is not included in a datetime value, the following rules are used.
- If the time zone is configured in the Channel table, the input datetime value is recognized in the format of the channel time zone. It is mapped to ISF with the UTC time zone.
- If the time zone is not configured in the Channel table, the input datetime value is recognized in the format of the local time zone where the mapper is running. The input datetime is mapped to ISF with the UTC time zone.

Outbound mapper

The CONFIG=entry channel parameter is required for outbound mapper. The mapper uses this parameter to locate the <msgTypeCfg> entry with a <subType> child element that contains the same value as the ISF business concept. The <msgTypeCfg> entry contains the configuration parameters for the outbound mapper.

For example, the default Message To channel is configured with a CONFIG=HVP_MAP_CFG_MT_NOTIFY_TO_CHANNEL parameter. When a message is received, the mapper searches the value table to find the <msgTypeCfg> entry to use for the message. It searches for a value table entry that meets the following conditions.

The value of the category is HVP_MAP_CFG_MT_NOTIFY_TO_CHANNEL.
The <msgTypeCfg> entry has a <subType> child element with a value that is the same as the ISF business concept.

The default <msgTypeCfg> entry for HVP_MAP_CFG_MT_NOTIFY_TO_CHANNEL is shown in the following example.

<msgTypeCfg>
   <subType>HVP_TO_DBTR_ROI_NOTIF</subType>
   <extendedCfg>
      <name>DESTINATION_ADDRESS</name>
      <value>HVPBEF20XXXX</value>
   </extendedCfg>
   <extendedCfg>
      <name>LT_ADDRESS</name>
      <value>TRGTXETGXXXX</value>
   </extendedCfg>
   <mapName>FXH_FIN196ISFToMTBodyMapper_fin2021</mapName>
   <type>FIN196</type>
</msgTypeCfg>

The following table shows the default configuration parameters for the channels that use the MT196 outbound mapper.

Table 2. Default configuration parameters for channels that use the MT196 outbound mapper
Category	SubType	Type
`HVP_MAP_CFG_MT_NOTIFY_TO_CHANNEL`	`HVP_TO_DBTR_ROI_NOTIF`	`FIN196`

The outbound mapper handles the datetime elements by using the following rules.

If the time zone is configured in the Channel table, the input datetime value is mapped from the UTC time zone to the format of the channel time zone.
If the time zone is not configured in the Channel table, the local time zone where the mapper is running is used. The input datetime value is mapped from the UTC time zone to the format of the local time zone.

The outbound mapper uses the TS_INCLUDE_OFFSET channel parameter to control whether the time zone offset is included in the output datetime values.

If TS_INCLUDE_OFFSET is set to Y, the time zone offset is included in the output datetime values.
If TS_INCLUDE_OFFSET is set to N or not configured, the time zone offset is not included in the output datetime values.