Inbound maps
The inbound maps are used with the ITX Inbound Integration flow. The inbound maps all flow
through a common driver map called CommonMap. This common map is the map name that needs to
be specified in the channel table entry.
CommonMap first checks to see whether the SWIFT message needs to be validated. If it does,
CommonMap calls
../FTM_Pack_SWIFT_MTyyyy/maps/validate_messages, where
yyyy is the SWIFT release year. It in turn calls the Java™ Verification Component to do the validation. The results are returned to
CommonMap. If the message failed validation CommonMap exits and the message
follows the error path through the rest of the integration flow.
For valid messages CommonMap converts blocks 1, 2, 3, and 5 of the SWIFT message to parts
of the ISF record. It then calls a map that is specific to the type of SWIFT message to convert block 4. If
the message type is not one of the types that are provided, CommonMap exits and the message
follows the error path through the rest of the integration flow.
MT200InboundBodyfor MT 200 messagesMT202InboundBodyfor MT 202 messagesMT203InboundBodyfor MT 203 messagesMT204InboundBodyfor MT 204 messagesMT210InboundBodyfor MT 210 messagesMT900InboundBodyfor MT 900 messagesMT910InboundBodyfor MT 910 messagesMT920InboundBodyfor MT 920 messagesMT940InboundBodyfor MT 940 messagesMT942InboundBodyfor MT 942 messagesMT950InboundBodyfor MT 950 messagesMTn98InboundBodyfor MT n98 messagesMTn99InboundBodyfor MT n99 messages