Generating RM reports

During the trial stage of a SWIFT service, you might want to determine whether the available RMA authorisations meet your needs. For example, you might want to:
  • Identify RMA authorisations for which there is no complementary authorisation (that is, no authorisation that authorizes a transfer in the opposite direction)
  • Identify missing RMA authorisations
To help you do this, FTM SWIFT generates, during customization, for each business OU, files containing SQL statements with a name of the form: 
deployment_dir/instance/admin/ou_dnfczlr1.ddl
deployment_dir/instance/admin/ou_dnfczlr2.ddl
where:
deployment_dir
Directory specified in the CDP initialization file
instance
Name of the instance.
ou
Name of the OU.

To use these files:

  1. Adapt the SQL statement as described in the header of the file.
  2. Process the file or the included SQL query with any SQL interpreter such as SPUFI or DB2® command line processor.
The SQL statements contained in these files require the following read authorizations:
dnfczlr1.ddl
Read authorization on the RM view DNF_RMAUT2_ou
dnfczlr2.ddl
Read authorization on:
  • The following message warehouse views:
    • DNI_MWH_ou
    • DNF_MWHEFM_ou
    • DNF_MWHEFA_ou
  • The following RM views:
    • DNF_RMAUT2_ou
    • DNF_RMPRM_ou
The SQL statements contained in these files use information in the message warehouse and the RMDS to create reports:
dnfczlr1.ddl
This file queries the RMDS and displays the following information about each RMA authorisation for which there is no complementary authorisation:
OWNBIC
The own BIC of the authorisation.
CORBIC
The correspondent BIC of the authorisation.
SERVICE
The SWIFTNet service of the authorisation.
RMAUT_TYPE
The type of the missing complementary authorisation.
RMAUT_STATUS
The status of the complementary authorisation. If this is null, the complementary authorisation is missing, otherwise it is invalid.
dnfczlr2.ddl
This file queries the message warehouse entries written by the MSIF transfer service and identifies records that lacked authorisation. Based on the information in these records, it queries the RMDS and displays the following information about the RMA authorisations that are missing or invalid:
OWNBIC
The own BIC of the authorisation.
CORBIC
The correspondent BIC of the authorisation.
SERVICE
The SWIFTNet service of the authorisation.
RMAUT_TYPE
The type of the authorisation.
MWH_REQUEST_TYPE
The type of the request that lacks authorisation. This can be used to check the permissions of the authorisation.
MWH_AUTH_STATUS
The authorisation status reported in the message warehouse. These values are described in Figure 1 and Figure 1. The following values correspond to RMA authorisations that are missing:
  • RM_NFND
  • RM_INV
  • RM_TNFND
  • RM_TINV