Please enable JavaScript to view this site.

Altova MapForce 2021 Enterprise Edition

SWIFT (Society for Worldwide Interbank Financial Telecommunication, https://www.swift.com) is a global provider of financial messaging services. SWIFT MT (Message Text) is a message type used in SWIFT network. MapForce supports mapping SWIFT MT data to or from any other MapForce-supported format (including XML, CSV, JSON, databases, and others). The SWIFT MT releases supported by MapForce are as follows:

 

November 2020 (default)

November 2019

 

Note:Mapping data to or from SWIFT MT requires BUILT-IN as transformation language. You can preview the mapping in MapForce (and save the output files, if any) or choose to execute it with MapForce Server (licensed separately) on a different computer or platform. It is not supported to generate an executable C#, C++, or Java program from mappings that read or write SWIFT MT data.

 

To support mapping data to or from various EDI-related formats, including SWIFT MT, MapForce uses configuration files (also known as "EDI Collections") specific to each release. An EDI collection is a directory that contains machine-readable configuration files, in XML format. By default, the EDI collections are installed in the C:\Program Files\Altova\MapForce2021\MapForceEDI directory. The name of collections (directories) applicable to SWIFT begins with "SWIFT".

 

Be aware that only the latest supported SWIFT collection is installed by default—you can download and install additional versions from the Altova website, see https://www.altova.com/mapforce/download/libraries.

 

Limitations

The following limitations apply when mapping data to or from SWIFT MT components. These limitations are applicable regardless of the execution engine running the mapping, be it MapForce or MapForce Server.

 

The following message types are not supported:

oNon-FIN messages

oCategory 0 messages (SWIFT system messages)

oCategory n messages (MTx9x)

To generate a SWIFT MT message, you need to supply the correct Message Type in the Application Header from the mapping, because it's not created automatically from content data. Also, make sure to map only data for the correct message type into the message text body (block 4).

MapForce provides no validation of SWIFT MT content. Only basic checks required to parse a message are performed.

No checks are performed with respect to the maximum message length.

On invalid input, the parser stops with an error message—no further recovery options are available.

 

Adding SWIFT MT components to the mapping

SWIFT MT messages have a structure that is significantly different from other EDI messages. Nevertheless, you can map SWIFT MT structures in MapForce in a way that is common to all EDI-based formats. Specifically, you can add SWIFT MT components (either source or target) to the mapping using any of the following approaches:

 

On the Insert menu, select the EDI command.

Click the Insert EDI btn_insert_edi toolbar button.

 

On the "Browse EDI Collections" dialog box, select the required SWIFT release, and then select the check boxes corresponding to the message types that you need to add to the mapping.

mff_swift_collections

Note:By default, only a generic collection called "SWIFT" is available on the "Browse EDI Collections" dialog box illustrated above. This default SWIFT collection is not suitable for production, because its version may change in newer versions of MapForce, just like all other EDI-related standards. For production, it is recommended to download and install the release-specific SWIFT configurations from the Altova website, see https://www.altova.com/mapforce/download/libraries. After installation, these release-specific configurations will appear on the "Browse EDI Collections" dialog box in addition to the default "SWIFT" configuration.

 

See also Adding EDI Components to the Mapping. For a mapping example, see Example: Convert SWIFT MT to SWIFT MX.

 

SWIFT MT settings

You can change the input files (or the path of the generated file) and other settings of SWIFT MT components from the "Component Settings" dialog box. To open the "Component Settings" dialog box, double-click the title bar of the component in MapForce (or right-click the title bar and select Properties from the context menu).

 

For reference to all options available on this dialog box, see EDI Component Settings. Note that the validation settings are disabled (grayed out) for SWIFT MT components because they are not supported, as mentioned above.

 

Handling SWIFT MT data types

MapForce handles SWIFT MT-specific simple data types as follows:

 

You can map SWIFT MT date types to an item of type xs:date or to a function that takes xs:date as input, and this will be processed correctly, without requiring any special handling. For example, if you map an item of type swift:date6 to a string, the resulting string is, for example, "20200922". However, if you map the same type to an xs:date, then the result is 2020-09-22 (of type xs:date).

If the target item is a string and you would like to have the date representation as "2020-09-22", add a variable of type xs:date to the mapping, and then map its result to the target string item.

If you map the swift:decimal value 42,66 to an item of type xs:decimal, then the result is 42.66. However, if you map the same type to an xs:string, the result is "42,66".

The same behavior is true for writing data to a target component. For example, if you map the xs:decimal value 15 to an item of type swift:decimal, then the result is 15, (of type swift.decimal).

 

Quick conversion to XML

Like with all other EDI-related formats, you can easily convert SWIFT MT files to XML without drawing any mapping connections. See Generating XML from EDI for details.

© 2020 Altova GmbH