How to run the example

This Example for Italy demonstrates how to map a RNI message into a corresponding SEPA message.

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.

  1. Use Map Designer to open the RNI to SEPA conversion map source file: it_sepa.mms. There are six maps:
    • itsep02c_rete_pacs_008 - Converts a RNI 550 message into a SEPA pacs.008.
    • itsep04d_rete_pacs_003 - Converts a RNI 401 message into a SEPA pacs.003
    • itsep06c_rete_pacs_004 - Converts a returned RNI 550 message into SEPA pacs.004
    • itsep08d_rete_pacs_004 - Converts a returned RNI 401 message (equivalent to a RNI 405) into SEPA pacs.004
    • itsep10c_rete_pacs_002 - Converts a rejected RNI 550 message into SEPA pacs.002.
    • itsep12d_rete_pacs_002 - converts a rejected RNI 401 message (equivalent to a RNI 405) into SEPA pacs.002.
  2. The 2nd input card makes use of either sepa_ct_config.xml or a sepa_dd_config.xml. It contains data which are required in the target SEPA format but is not available in the source RNI format.

    For example:

    constant name : settlement_method with value "CLRG".

    You must make a business decision as to how to determine what type of settlement will be applied per RNI message that is being converted to SEPA.

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

  3. The opposite direction is also available, SEPA to RNI conversion map source file: sepa_it.mms. There are six maps:
    • sepit02c_pacs_008_rete - converts a SEPA pacs.008 to a RNI 550 message
    • sepit04d_pacs_003_rete - converts a SEPA pacs.003 to a RNI 401(riba) message
    • sepit06c_pacs_004_rete - converts a SEPA pacs.004 to a "returned" RNI 550 message
    • sepit08d_pacs_004_rete - converts a SEPA pacs.004 to a "returned" RNI 401(riba) equivalent to RNI 405 message.
    • sepit10c_pacs_002_rete - converts a SEPA pacs.002 to a "rejected" RNI 550 message.
    • sepit12d_pacs_002_rete - converts a SEPA pacs.002 to a "rejected" RNI 401(riba) equivalent to RNI 405 message.

  4. The 2nd input card makes use of either rete_550_config.xml, rete_401_riba_config.xml or rete_405_riba_config.xml It contains data which is required in the RNI format but is not available in the SEPA format.

    For example:

    constant name : mittente with value "12345".

    You must determine what is the "mittente" (sender) five digit numeric id to be applied per SEPA transaction that is being converted to a RNI message.

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

  5. Prior to running the example maps under sepa_it.mms, copy the following schemas from :

    <install dir>\packs\sepa_vn.n.n\mapsandschemas

    to :

    <install dir>\packs\sepa_vn.n.n\examples\italy\maps
    • pacs.002.001.03.xsd
    • pacs.002.001.03.xsd
    • pacs.004.001.02.xsd
    • pacs.008.001.02.xsd
    • sepa_config.xsd

  6. Prior to executing the sepa validation map against the SEPA messages from this example, perform the following:
    1. Backup the bic.xml file that is located in :

      <install dir>\packs\sepa_vn.n.n\mapsandschemas

    2. Copy the bic.xml file from:

      <install dir>\packs\sepa_vn.n.n\examples\italy\data

      to

      <install dir>\packs\sepa_vn.n.n\mapsandschemas