What the example contains

Files included in this example are as follows:

  • Maps:

    The maps directory contains the following map source:

    • cbpr_t9n_mt_frmwrk_maps.mms
      • cbpr1500_mt9n0_framework

        Main map to transform MT900/MT910 into camt.054.001.08

      • cbpr2800_mt103_framework

        Main map to transform MT103 COR/STP into pacs.008.001.08 COR

      • cbpr2808_mt103sgo_framework

        Main map to transform MT103 SGO into pacs.008.001.08 SGO

      • cbpr2810_mt202_framework

        Main map to transform MT202 COR/COV into pacs.009.001.08 ADV/COR/COV

      • cbpr2811_mt205_framework

        Main map to transform MT205 COR/COV into pacs.009.001.08 COR/COV

      • cbpr2820_mtn96_framework

        Main map to transform MT196/296 into camt.029.001.09

      • cbpr2840_mtn92_framework

        Main map to transform MT192/292 into camt.056.001.08

    • cbpr_t9n_mt_setvarlog.mms

      Utility used to report translation logs.

    • cbpr_t9n_mt103_pacs008.mms

      Utility used to populate pacs.008.001.08

    • cbpr_t9n_mt103_pacs008_stp.mms

      Utility used to populate pacs.008.001.08 STP

    • cbpr_t9n_mt103_pacs008_sgo.mms

      Utility used to populate pacs.008.001.08 SGO

    • cbpr_t9n_mt202_pacs009_adv.mms

      Utility used to populate pacs.009.001.08 ADV

    • cbpr_t9n_mt20n_pacs009_cov.mms

      Utility used to populate pacs.009.001.08 COV

    • cbpr_t9n_mt20n_pacs009.mms

      Utility used to populate pacs.009.001.08 COR

    • cbpr_t9n_mt9n0_camt054.mms

      Utility used to populate camt.054.001.08

    • cbpr_t9n_mtn96_camt029.mms

      Utility used to populate camt.029.001.09

    • cbpr_t9n_mtn92_camt056.mms

      Utility used to populate camt.056.001.08

  • Schemas:

    The schemas directory contains the following files downloaded from SWIFT MyStandards MT/ISO 20022 Translation portal.

    • camt.029.001.09.xsd
    • head.001.001.02_camt_029.xsd
    • camt.052.001.08.xsd
    • head.001.001.02_camt.052.xsd
    • camt.053.001.08.xsd
    • head.001.001.02_camt.053.xsd
    • camt.054.001.08.xsd
    • head.001.001.02_camt.054.xsd
    • camt.056.001.08.xsd
    • head.001.001.02_camt_056.xsd
    • pacs.008.001.08.xsd
    • head.001.001.02_pacs_008.xsd
    • pacs.008.001.08_stp.xsd
    • head.001.001.02_pacs_008_stp.xsd
    • pacs.009.001.08.xsd
    • head.001.001.02_pacs_009.xsd
    • pacs.009.001.08_adv.xsd
    • head.001.001.02_pacs_009_adv.xsd
    • pacs.009.001.08_cov.xsd
    • head.001.001.02_pacs_009_cov.xsd
    • trx_config.xsd

      Schema for the translation configuration file.

    Each will have corresponding .mtx files used internally to manage RESTART attributes.

  • Trees:

    The trees directory contains the following files:

    • infoset.mtt

      Metadata used to represent input message into JSON.

    • swift_iso7775_ccyy.mtt

      Metadata supporting SWIFT MT ISO7775 FIN structures.

    • swiftroute_funds.mtt

      Multi-purpose metadata structures.

  • Data:

    The data directory contains the following file:

    • Sample SWIFT MT messages:
      • MT196_bad.inp
      • MT202_ADV_bad.inp
      • MT296_bad.inp
      • MT202_COR_bad.inp
      • MT202_COV_bad.inp
      • MT205_COR_bad.inp
      • MT205_COV_bad.inp
      • MT296_bad.inp
      • MT103.inp
      • MT103_STP.inp
      • MT103_SGO.inp
      • MT196.inp
      • MT296.inp
      • MT192.inp
      • MT292.inp
      • MT202_COR.inp
      • MT202_ADV.inp
      • MT202_COV.inp
      • MT205_COR.inp
      • MT205_COV.inp
      • MT900.inp
      • MT910.inp
      • trx_config.xml

        Translation configuration file.