Maintain the External Code Lists

Edit online

About this task

All necessary code lists are automatically installed but except for the Message Type code lists, they are not automatically populated with codes. Therefore, you need to populate the following five external code lists for use in conjunction with the SWIFT_MessageTypes code list (all code lists are automatically installed with the Sterling B2B Integrator—the SWIFT_MessageTypes code list already contains a list of valid message types) to perform SWIFTNet validations.

The external code lists for which you need to populate SenderID, ReceiverID, Description, and occasionally Text1 are:

  • SWIFT_Addresses
  • SWIFT_BaseAddresses
  • SWIFT_Currencies
  • SWIFT_Countries (this SWIFT code list contains countries and regions)
  • SWIFT_BICPlusIBAN
  • SWIFT_IBANFormats
  • SWIFT_SEPARouting

You populate these code lists automatically by using the HIPAA codelist conversion map for countries or regions to populate it. However, prior to using the HIPAA codelist conversion map, you need to modify the import file created using the conversion map (the import file is used to populate the codelist). To modify the import file you need to change the codelist name from xxx to SWIFT_xxx (for example, change BICPlusIBAN to SWIFT_BICPlusIBAN).

To populate the each code list automatically:

Procedure

  1. From a command line, go to the tp_import directory.
  2. Type the following command to start the conversion and import process, where <map name> is the name of the map to use during translation (without the file extension) and <code list path and filename> is the fully qualified name of the code list to translate, including filename extension, if any:
    • If you are using Windows, hipaaconvert.cmd [-import] <map name> <code list path and filename>
    • If you are using UNIX, hipaaconvert.sh [-import] <map name> <code list path and filename>

      Do not specify the file extension for the map name when importing a code list—just indicate the base name of the map.

      The [-import] parameter is optional. You can convert the code list file without importing it. If you do not use the [-import] parameter during conversion, you can import the resulting XML file into the Sterling B2B Integrator using the import utility.

      The input files and maps for each code list are as follows:

      Code List Map Input File and Directory
      SWIFT_Addresses SWIFTFIFIleToSWIFT_Addresses FI file from BIC directory
      SWIFT_BaseAddresses SWIFTFIFIleToSWIFT_BaseAddresses FI file from BIC directory
      SWIFT_BICPlusIBAN SWIFTBIFileToSWIFT_BICPlusIBAN BI file from BICPlusIBAN directory
      SWIFT_IBANFormats SWIFTISFileToSWIFT_IBANFormats IS file from BICPlusIBAN directory
      SWIFT_Countries (this SWIFT code list contains countries and regions) SWIFTCTFileToSWIFT_Countries (which contains countries and regions) CT file from BIC directory
      SWIFT_Currencies SWIFTCUFileToSWIFT_Currencies CU file from BIC directory
  3. Once the utility completes, a translation report (hipaaconvert.rpt) and an input file (hipaaconvert.xml) are created. If no translation errors are reported, the code list was successfully generated (and imported if you used the [-import] parameter). A code list will not be imported if there are translation errors.
  4. To modify the import file, change the codelist name from xxx to SWIFT_xxx so it can be used for SWIFT messages.