xsys.012.001.02 mapper

The xsys.012 (xsys.012.001.02) inbound mapper is used by T2 for sending delivery notification (DlvryNtfctn) messages from RTGS to FTM for High Value Payments.

Overview

The default mapper name is Xsys012ToISFMapper. The xsys.012 mapper can also be used along with the High Value Payments business application header mapper. For more information, see High Value Payments business application header mapper.

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.

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 xsys.012.* in the value table. The <msgTypeCfg> entry contains the configuration parameters for the inbound mapper.

For example, the default Message From Target2 channel is configured with a CONFIG=HVP_MAP_CFG_MSG_FROM_TARGET2 parameter. When an xsys.012.001.02 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_MSG_FROM_TARGET2.
The <msgTypeCfg> entry has a <type> child element with the value of xsys.012.*.

If the <msgTypeCfg> entry cannot be found, the mapper causes an exception to report a subType not found error.

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

<msgTypeCfg>
   <class>XSYS012</class>
   <subType>HVP_FROM_NETWORK_DELIVERY_NOTIF_NACK</subType>
   <extendedCfg>
      <name>MASTER_FLAG</name>
      <value>N</value>
   </extendedCfg>
   <pt>
      <class>XSYS012</class>
      <subType>HVP_FROM_NETWORK_DELIVERY_NOTIF_NACK</subType>
   </pt>
   <mapName>Xsys012ToISFMapper</mapName>
   <type>xsys.012.*</type>
</msgTypeCfg>

The following table shows the values from the <msgTypeCfg> entry that are used as configuration parameters by the inbound mapper.

Table 1. Values from `<msgTypeCfg>` that are used as configuration parameters by the inbound mapper
Element	Description
`<class>`	The value from this element is used as the value for TRANSACTION_V.OBJ_CLASS.
`<subType>`	The value from this element is used as the value for TRANSACTION_V.SUBTYPE and ISFMessage/Header/BusinessConcept.
`<extendedCfg>` element that has a `<name>` child element with the value MASTER_FLAG.	The value from the associated `<value>` child element is used as the value for MASTER_FLAG for TRANSACTION_V and TRANSMISSION_V.
`<pt>`	The value from the `<class>` child element is used as the value for TRANSMISSION_V.OBJ_CLASS.
`<pt>`	The value from the `<subType>` child element is used as the value for TRANSMISSION_V.SUBTYPE.

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

Table 2. Default configuration parameters for channels that use the xsys.012 inbound mapper
Category	Class	SubType	MASTER_FLAG	Pt.class	Pt.subType
`HVP_MAP_CFG_MSG_FROM_TARGET2`	`XSYS012`	`HVP_FROM_NETWORK_DELIVERY_NOTIF_NACK`	`N`	`XSYS012`	`HVP_FROM_NETWORK_DELIVERY_NOTIF`