Creating SWIFT Maps

The Sterling B2B Integrator Map Editor enables you to map SWIFT documents. The Sterling B2B Integrator Map Editor generates a file layout for you using the components and message types that you select. The Sterling B2B Integrator Map Editor-generated SWIFT map consists of groups, records, composites, and fields that are comparable to parameters that are defined by SWIFT. See How SWIFT Terminology Correlates with the Sterling B2B Integrator Map Editor.

Note: You need to download the Sterling B2B Integrator Map Editor component from Sterling B2B Integrator to use it.

Sterling B2B Integrator Map Editor allows you to modify the map components by using the Deactivate, Promote, Split, Copy, Cut, and Paste functions.

You can create a map for all SWIFT Standards Release messages loaded into the standards database. All messages are validated by the Sterling B2B Integrator for syntax (for example, field types, field lengths, and so forth). See Using SWIFTNet (8.0.1) for information on which messages are validated by the Sterling B2B Integrator for syntax and semantics. If you create a map for a message that is not currently validated by the Sterling B2B Integrator, when the Sterling B2B Integrator Map Editor is capable of updating your existing map with message validation rules in a future release, any extended rules you have created will exist outside the validation block (and thus will always run regardless of whether validation is enabled).

When you create a map, for both the input and output sides, you choose whether you want to use a preloaded standard, an existing file format, or wants to create a new file format for that side of the map (including selecting from standards that you have previously downloaded to the standards database. The preloaded standards are automatically loaded when you download the Sterling B2B Integrator Map Editor to your machine. You must install the SWIFT Financial Services XML Standards to be able to select SWIFTNet Bulk Payments, SWIFTNet Transaction Reporting, SWIFTNet Funds, SWIFTNet Trade Services Utility, SWIFTNet Exceptions and Investigations, SWIFTNet Proxy Voting, SWIFTNet SCORE, SWIFTNet FpML, SWIFTNet Cash Management, or SWIFTNet Cash Reporting.

For version 8.0 and forward, all SWIFT and SWIFTNet maps have group parsing shortcuts enabled for the Input side of the map during translation to skip group parsing if the first non-repeating mandatory record of a group is not present in the input.

However, if you want to use a specialized version of a message that is not available in the Sterling B2B Integrator SWIFT data dictionary, it may be appropriate for you to define the SWIFT map yourself. Alternatively, you could use an MT or MX that is similar to what is required and customize it yourself.

The Sterling B2B Integrator also performs SWIFT MX validations. Validations are defined in the translator_swift_mx.properties property file and generated maps define the parameters used to look up validates in this property file. Changes to validations are also applied to SWIFT MX messages for currencies, BICPlusIBAN, BIC/BEI addresses, and International Bank Account Number checksum validation (IBAN). You can define code lists for currencies, countries, ,BIC or BEI addresses (that are validated against the SWIFT_Addresses code list) BICPlusIBAN, and SEPARouting. IBAN data contains a country code that is validated against the SWIFT_Countries code list in the Sterling B2B Integrator, and additional IBAN validation is handled internally by the translator.

The Sterling B2B Integrator supplies you with the following statements to be used with SWIFT maps and any other data format:

  • cerror
  • exist
  • occurrencetotal
  • resetoccurrencetotal
  • sum
  • sumtotal

See Alphabetic Language Reference for all the available extended rules.

To ensure that extended rules for SWIFT maps are only run when validation is enabled, place your custom extended rule code in a validation block. See Creating Extended Rules for SWIFT Maps.