RM distribution files
FTM SWIFT can exchange authorisations with other RMAs by means of an RM distribution file. You can import authorisation from an RM distribution file into the RMDS, or create an RM distribution file by exporting the authorisation data from the RMDS.
When you import authorisations from an RM distribution file, you must also specify the name of a CO associated with a LAU key. Each LAU key is composed of two half keys, both of which were entered earlier and are stored in FTM SWIFT in encrypted form.
Before importing the contents of a distribution file, FTM SWIFT uses the LAU key to calculate a LAU value and compares the result to the value contained in the distribution file. It imports the file contents only if the two LAU values are identical.
Similarly, when you export authorisations to an RM distribution file the LAU key is used to calculate a LAU value, which is stored as part of the file.
- Complete
- The data in
the distribution file represents all authorisations for all the BIC8s
of your financial institution. Authorisations for all the BIC8s listed
in the distribution file are deleted from the target before the contents
of the distribution file are imported. Note: Import a distribution file with the filemode complete only in exceptional situations such as when you are unsure whether all partial RM distribution files were properly imported to FTM SWIFT. When you import a distribution file with the filemode complete, there is a time period during which the old records were deleted, but the new records are not yet created. If there is FIN or MSIF traffic during this period, some messages or files might not be able to be processed due to missing RMA authorisations. Therefore, before importing a complete RM distribution file, stop all FIN and MSIF traffic, for example:
- For FIN traffic, by issuing the quit command for each FIN LT, or by stopping the DNF_ILC_FIN message flow
- For MSIF traffic, by issuing the stop command for each OU, or by stopping the DNF_O_FTx message flows
- Partial
- The data in the distribution file represents a subset of the authorisations for the BIC8s of your financial institution. No authorisations are deleted from the target before the contents of the distribution file are imported. If the target already contains a record that corresponds to a record in the distribution file, it is replaced only if the record in the distribution file is younger.
Partial and incremental distribution files are typically much smaller than complete or full distribution files, so you will probably prefer to work with them, and use complete or full distribution files only when you suspect that the relationship management data in the RMA or the RMDS is corrupted. By exporting authorisations from and importing authorisations to FTM SWIFT after each change, you can ensure that the authorisations in the RMA and the RMDS remain synchronized.