How to run the example in Design Studio

These examples demonstrate how to map a SWIFTNet FIN message to a SEPA message, as well as how to map a SEPA message to a SWIFTNet FIN message.

About this task

The example maps allow the use of a configuration file that represents field values specific to the target format that is not readily available from the source format.

Follow these steps to run the example:

Procedure

  1. Use the Design Studio to open the following map source files:
    • fn_sepa.mms
    • sepa_fn.mms
  2. Build the maps in the source files, and then run the following transformation maps.
    • mt101_pain_001
    • mt102_pacs_002
    • mt102_pacs_004
    • mt102_pacs_008
    • mt102plus_pacs_008
    • mt103_pacs_002
    • mt103_pacs_004
    • mt103_pacs_008
    • mt103plus_pacs_008
    • pacs_002_mt102
    • pacs_002_mt103
    • pacs_004_mt102
    • pacs_004_mt103
    • pacs_008_mt102
    • pacs_008_mt102plus
    • pacs_008_mt103
    • pacs_008_mt103plus
    • pain_001_mt101
  3. Review the contents of sepa_config.xml. This file contains data which are required in the SEPA format but is not available in the SWIFT format.

    For example:

    constant name : inout_indicator with value O.

    A business decision must be made as to how to determine what type of direction will be applied per SEPA transaction that is being converted to a SWIFT message.

    During actual implementation, this file must be replaced with an actual source (that is, the database repository), or it must be based upon your unique situation.

    A value of O populates an outbound specific application header block and an I will populate all inbound specific application header block.