8.1.3 External Attributes Screening Configuration for ISO20022 Batch

For the external attributes screening configuration for the ISO20022 Batch follow the subsequent steps:

1. Add the attribute names (case-sensitive) to FCC_TF_XML_EXTERNAL_ATTR, FCC_TF_XML_EXTERNAL_ATTR_MLS table in the Atomic Schema.
2. Login to OFSAA Transactions Filtering application as TFADMN.
3. Navigate to ISO20022/XML Configuration Admin screen.
4. Open any ISO20022 Message Provider and configure the external attributes for each screening type separately. For reference, see Step 6 in section 8.1 and Table 25.

Expected JSON Format and keywords by Transaction Filtering Application:

• The filename of external attributes should be in the format filename_external_attributes.json, where The filename stands for the corresponding ISO20022 batch xml filename. OFS TRANSACTION FILTERING ADMINISTRATION GUIDE | 101 CONFIGURATIONS FOR THE ISO20022 MESSAGE PARAMETERS CONFIGURING THE ISO20022 MESSAGE PARAMETERS.

  For Example, If the batch xml filename is pacs.003.001.02.xml, then the external attributes filename should be pacs.003.001.02_external_attributes.json.

• External Attributes JSON file must be placed in the same folder (INPUT folder) where the batch XML file is located.
• The subsequent JSON format must be followed to screen the external attributes.
  1. JSON format for Batches of Transactions XML:

     {

     "batch_external_attributes": [{

     "batch_id": [batch id given in PmtInfId tag],

     "external_attributes": {

     "jurisdiction":"All",

     "business_domain":"GEN",

     "priority":"Medium",

     […configured external attributes with attribute value as key-value pair…]

     }

     }, {

     "batch_id": [batch id given in PmtInfId tag],

     "external_attributes": {

     "jurisdiction":"EMEA",

     "business_domain":"All",

     "priority":"Medium",

     […configured external attributes with attribute value as key-value pair…]

     }

     }, …..,.

     ]

     }

  2. JSON format for single Transaction XML:

     { "batch_external_attributes": [{ "batch_id": "", "external_attributes": { "jurisdiction":"EMEA", "business_domain":"GEN", "priority":"High", OFS TRANSACTION FILTERING ADMINISTRATION GUIDE | 102 CONFIGURATIONS FOR THE ISO20022 MESSAGE PARAMETERS CONFIGURING THE ISO20022 MESSAGE PARAMETERS […configured external attributes with attribute value as key-value pair…] } }] }

     (OR)

     {

     "batch_external_attributes": [{

     "external_attributes": {

     "jurisdiction":"EMEA",

     "business_domain":"GEN",

     "priority":"High",

     […configured external attributes with attribute value as key-value pair…]

     }

     }]

     }

Note:

• If payment contains single transaction, batch_id label is not mandatory. If a payment contains multiple batches of transactions, batch_id label is mandatory.
• The jurisdiction, business_domain and priority labels are optional. If you provide these labels in JSON, application will take these values. Otherwise, the application will take the value from SETUP_RT_PARAMS table.
• The Message Direction will be taken based on the folder structure (either OUTBOUND or INBOUND) under which you place the files.
• The batch_external_attributes, batch_id, external_attributes, jurisdiction, business_domain, and priority labels should not be changed.
• The value of jurisdiction must be a value of JRSDCN_NM column from KDD_JRSDCN table.
• The value of business_domain must be a value of TF_BUS_DMN_NM column from DIM_KDD_BUS_DMN table.
• The value of priority must be a value of V_ALERT_PRIORITY_NAME column from DIM_ALERT_PRIORITY_TYPE table.