Unsupported Message Mapper

For example, the default Request From CSM channel is configured with a CONFIG=IP_MAP_CFG_REQ_FROM_CSM parameter. When an unsupported remt.001.001.XX message is received , the mapper looks for the <msgTypeCfg> entry in the Value table with the following conditions:

• In Value table, the value of Category is IP_MAP_CFG_REQ_FROM_CSM.
• In msgTypeCfg entry, the value of Type is remt.001.001.XX.

The example of <msgTypeCfg> of IP_MAP_CFG_REQ_FROM_CSM for remt.001.001.XX is as follows.

<msgTypeCfg>
	<class>REMT001</class>
	<subType>IP_FROM_CSM_UNSP_MSG</subType>
	<extendedCfg>
		<name>MASTER_FLAG</name>
		<value>Y</value>
	</extendedCfg>
	<extendedCfg>
		<name>Sender</name>
		<value>{RmtAdvc/GrpHdr/InitgPty/Id/OrgId/Othr/Id}</value>
	</extendedCfg>
	<extendedCfg>
		<name>Receiver</name>
		<value>{RmtAdvc/GrpHdr/MsgRcpt/Id/OrgId/Othr/Id}</value>
	</extendedCfg>
	<extendedCfg>
		<name>CreationDateTime</name>
		<value>{RmtAdvc/GrpHdr/CreDtTm}</value>
	</extendedCfg>
	<extendedCfg>
		<name>MessageIdentification</name>
		<value>{RmtAdvc/GrpHdr/MsgId}</value>
	</extendedCfg>
	<extendedCfg>
		<name>InstructionIdentification</name>
		<value>{RmtAdvc/RmtInf/OrgnlPmtInf/Refs/InstrId}</value>
	</extendedCfg>
	<extendedCfg>
		<name>TransactionIdentification</name>
		<value>{RmtAdvc/RmtInf/OrgnlPmtInf/Refs/TxId}</value>
	</extendedCfg>
	<extendedCfg>
		<name>InterbankSettlementAmount</name>
		<value>{RmtAdvc/RmtInf/OrgnlPmtInf/Amt/InstdAmt}</value>
	</extendedCfg>
	<extendedCfg>
		<name>Currency</name>
		<value>{RmtAdvc/RmtInf/OrgnlPmtInf/Amt/InstdAmt/Ccy}</value>
	</extendedCfg>
	<extendedCfg>
		<name>Status</name>
		<value>RJCT</value>
	</extendedCfg>
	<extendedCfg>
		<name>ReasonCode</name>
		<value>NARR</value>
	</extendedCfg>
	<pt>
		<class>REMT001</class>
		<subType>IP_FROM_CSM_UNSP_MSG</subType>
	</pt>
	<mapName>UnspMsgToISFMapper</mapName>
	<type>remt.001.001.XX</type>
</msgTypeCfg>

The inbound mapper uses the configuration parameters of the <msgTypeCfg> entry as follows:

• <class> - value for TXN_PAYMENT_V.OBJ_CLASS
• <subType> - value for TXN_PAYMENT_V.SUBTYPE and ISFMessage/Header/BusinessConcept
• <pt>.<class> - value for TRANSMISSION_V.OBJ_CLASS
• <pt>.<subType> - value for TRANSMISSION_V.SUBTYPE
• <type> - value for ISFMessage/Header/MessageName
• <extendedCfg> - the <extendedCfg> entries contain <name>/<value> pairs that are used as follows:
  • <name> - Each name represents a predefined ISF path that the <value> in the <name>/<value> pair is populated to. Table 1 shows the predefined names in the inbound mapper, and the corresponding ISF paths and Database columns that the values are mapped to. The Mandatory column in the table indicates if the <name>/<value> pair is mandatory in the <msgTypeCfg> entry.

    Table 1. Predefined elements and ISF paths in UnspMsgMap mapper

    Name	ISF path	Database	Mandatory	Description
    Sender	ISFMessage/Header/Sender	TXN_PAYMENT_V.SENDER TRANSMISSION_V.SENDER	Y	Creditor/Debtor FI identification
    Receiver	ISFMessage/Header/Receiver	TXN_PAYMENT_V.RECEIVER TRANSMISSION_V.RECEIVER	Y	Debtor/Creditor FI identification
    MessageIdentification	ISFMessage/Wrapper/MessageIdentification	TXN_PAYMENT_V.CID TRANSMISSION_V.CID	Y	Message Identification
    CreationDateTime	ISFMessage/Wrapper/CreationDateTime		Y	Creation Date Time Note: the value is mapped to ISF with UTC timezone.
    InstructionIdentification	ISFMessage/Wrapper/InstructionIdentification		N	Instruction Identification
    TransactionIdentification	ISFMessage/Wrapper/TransactionIdentification		N	Transaction Identification
    InterbankSettlementAmount	ISFMessage/Wrapper/InterbankSettlementAmount		N	Interbank Settlement Amount
    Currency	ISFMessage/Wrapper/Currency		N	Currency of the InterbankSettlemnt Amount
    InterbankSettlementDate	ISFMessage/Wrapper/InterbankSettlementDate		N	Interbank Settlement Date
    Status	ISFMessage/Wrapper/Status		N	Transaction Status
    ReasonCode	ISFMessage/Wrapper/ReasonCode		N	Status Reason
    MASTER_FLAG		TXN_PAYMENT_V.MASTER_FLAG TRANSMISSION_V.MASTER_FLAG	Y	Master Transaction/Transmission

  • <value> - the value mapped to the <name> element in ISF. The value in the <value> can be
    • a path - the inbound mapper retrieves the value of the path from the incoming message, and maps the value to the ISF path for the <name> element.
      Note: The <value> must be enclosed in braces when the value is a path.
      For example, with the following entry, the mapper retrieves the value of CdtrPmtActvtnReq/GrpHdr/MsgId from the incoming message, and maps the value to the ISF path ISFMessage/Wrapper/MessageIdentification.

      <name>MessageIdentification</name>
      <value>{CdtrPmtActvtnReq/GrpHdr/MsgId}</value>

    • a constant - the inbound mapper maps the value to the ISF path for the <name> element.
      Note: The <value> cannot be enclosed in braces when the value is a constant.
      For example, with the following entry, the mapper maps the value 'RJCT' to the ISF path ISFMessage/Wrapper/Status.

      <name>Status</name>
      <value>RJCT</value>