Outbound maps

The outbound maps are used with the ITX Outbound Integration flow. It calls the map that is specific to the SWIFT message type that is to be created.

The SWIFT message type maps are named:

  • MT200OB for MT 200 messages
  • MT202OB for MT 202 messages
  • MT203OB for MT 203 messages
  • MT204OB for MT 204 messages
  • MT210OB for MT 210 messages
  • MT900OB for MT 900 messages
  • MT910OB for MT 910 messages
  • MT920OB for MT 920 messages
  • MT940OB for MT 940 messages
  • MT942OB for MT 942 messages
  • MT950OB for MT 950 messages
  • MTn98OB for MT n98 messages
  • MTn99OB for MT n99 messages

The map creates block 4 of the SWIFT message, and then calls MapAddenda to create blocks 1, 2, 3, and 5. After the SWIFT message is created, and if the user requested that the message be validated in the Channel table entry, the map 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 the map. If the message failed validation, the map exits and the message follows the error path through the rest of the integration flow.