5.11.1 Configuring Jurisdictions and Business Domains

The default Sanctions groups are tfanalytgroup and tfsupervisorgrp. According to the ready- to-use product, these groups get all alerts and notifications for all jurisdictions and business domains. To configure the alerts, follow these steps:

1. Load all the jurisdictions. To do this, run the query SELECT * FROM FCC_SWIFT_JSRDSN_MAP

   and load the jurisdictions in the V_JRSDCN_CD column in the FCC_SWIFT_JSRDSN_MAP table. The following columns are provided to populate any additional information:

   Table 5-4 Columns used to provide additional information for Jurisdictions

   Column	Data Type and Length
   V_EXTRACTED_SWIFT_- FIELD	VARCHAR2(100 CHAR)
   V_JRSDCN_CD	VARCHAR2(40 CHAR)
   V_CUST_COLUMN_1	VARCHAR2(4000 CHAR)
   V_CUST_COLUMN_2	VARCHAR2(4000 CHAR)
   V_CUST_COLUMN_3	VARCHAR2(4000 CHAR)
   V_CUST_COLUMN_4	VARCHAR2(4000 CHAR)

   Table 8:

   Table 5-5 Columns used to provide additional information for Jurisdictions

   Column	Data Type and Length
   N_CUST_COLUMN_1	NUMBER(20)
   N_CUST_COLUMN_2	NUMBER(20)
   N_CUST_COLUMN_3	NUMBER(20)
   N_CUST_COLUMN_4	NUMBER(20)

2. Load all the business domains in the V_BUS_DMN_CD column in the FCC_SWIFT_BUS_DMN_MAP table.

   The following columns are provided to populate any additional information:

   Table 9:

   Table 5-6 Columns used to provide additional information for Business Domains

   Column	Data Type and Length
   V_EXTRACTED_SWIFT_- FIELD	VARCHAR2(100 CHAR)
   V_JRSDCN_CD	VARCHAR2(40 CHAR)
   V_CUST_COLUMN_1	VARCHAR2(4000 CHAR)
   V_CUST_COLUMN_2	VARCHAR2(4000 CHAR)
   V_CUST_COLUMN_3	VARCHAR2(4000 CHAR)
   V_CUST_COLUMN_4	VARCHAR2(4000 CHAR)
   N_CUST_COLUMN_1	NUMBER(20)
   N_CUST_COLUMN_2	NUMBER(20)
   N_CUST_COLUMN_3	NUMBER(20)
   N_CUST_COLUMN_4	NUMBER(20)

3. Map user groups to the appropriate jurisdiction and business domain. To do this, run the query SELECT * FROM DOMAIN_JUR_GRP_MAP and do the mapping in the DOMAIN_JUR_GRP_MAP table and map with the additional columns STATUS_CD, ALERT_TYPE_CD.

   Note:

   • Refer N_SANCTION_STATUS_CODE column from DIM_SANC- TIONS_STATUS table for list of Status codes.
   • Refer N_ALERT_TYPE_CODE column from DIM_SANC_TF_ALERT_- TYPE table for list of alert types.

   If multiple jurisdictions are mapped to a single user group, create as many rows as the number of jurisdictions and add the new jurisdiction in each row for the same user group.

   If multiple business domains exist for the same user group and same jurisdiction, create as many rows as the number of business domains and add the new business domain in each row for the same user group and jurisdiction.

4. Put the appropriate SQL query in the Message_jurisdiction and Message_Business_Do- main rows to derive the jurisdiction and business domain respectively in the Setup_Rt_Params table.

This step is required to define the source of jurisdiction and business domain from the message or an external source.

The definition and source of jurisdiction and business domain are different for each customer. In this way, the Transaction Filtering application gives the flexibility to the user to pick any attribute of the message to define the jurisdiction and business domain. For example, jurisdiction can be the BIC present in block 1/block 2 of the SWIFT message or the branch ID present in the SWIFT GPI header.

The ready-to-use application can extract some of the key fields of the message, which are avail- able in the fsi_rt_al_msg_tag table. If the customer wants to use any field as a jurisdiction or business domain from this table, then an SQL query must be written in the Setup_Rt_Param table to extract the respective column.

When a message is posted, the system updates the jurisdiction and business domains extracted in step 4 in the FSI_RT_RAW_DATA and FSI_RT_ALERTS tables.