8.1.2 Running the ISO20022 Batch

The ISO20022 messages are processed using batches. So, you must first create the following folders before you run the ISO20022 batch:

  1. Create a folder for the MIS date with the folder name as ##FIC_MIS_DATE## (the date on which we run the ISO20022 batch) in the following directory structure:

    ##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML

    For example, /scratch/fccmappchef/SANC807/ftpshare/SANCINFO/STAGE/SEPA/ inputXML/20200214.

    20200214 is the MIS Date folder.

  2. Create two folders called OUTBOUND and INBOUND inside the MIS Date folder and create a folder called INPUT inside both the folders.

    Note:

    All the ISO20022 XMLs must be either kept inside the INPUT folder inside the OUTBOUND folder or the INPUT folder inside the INBOUND folder based on the direction of the message XML. The ISO20022 batch takes these XMLs as input when it is run.

The directory structures for OUTBOUND and INBOUND are as follows:

##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML/##FIC_MIS_DATE##/OUT- BOUND/INPUT

##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML/##FIC_MIS_DATE##/INBOUND/ INPUT

For example,

    • /scratch/fccmappchef/SANC807/ftpshare/SANCINFO/STAGE/SEPA/inputXML/ 20200214/OUTBOUND/INPUT
    • /scratch/fccmappchef/SANC807/ftpshare/SANCINFO/STAGE/SEPA/inputXML/ 20200214/INBOUND/INPUT

After you run the ISO20022 batch, the following actions are performed:

  • The VAL_ERROR,PRCSNG_ERROR,PROCESSED, and FEEDBACK folders are created as part of the batch processing.
  • If any message XML fails during validation, then it is moved to the VAL_ERROR folder. The directory structures for OUTBOUND and INBOUND are as follows:

##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML/##FIC_MIS_DATE##/OUT- BOUND/VAL_ERROR

##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML/##FIC_MIS_DATE##/INBOUND/ VAL_ERROR

  • If any message XML fails during the parsing process after validation, then it is moved to the PRCSNG_ERROR folder. The folder structures for OUTBOUND and INBOUND are as follows:

    ##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML/##FIC_MIS_DATE##/OUT- BOUND/PRCSNG_ERROR

    ##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML/##FIC_MIS_DATE##/INBOUND/ PRCSNG_ERROR

  • If any message XML is successfully processed, then it is moved to the PROCESSED folder. The directory structures for OUTBOUND and INBOUND are as follows:

    ##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML/##FIC_MIS_DATE##/OUT- BOUND/VAL_ERROR

    ##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML/##FIC_MIS_DATE##/INBOUND/ VAL_ERROR

  • After the batch is run successfully, a ##FILE_NAME##_feedback.xml file is created for each file that is processed. The feedback is created inside the FEEDBACK folder. The directory structures for OUTBOUND and INBOUND are as follows:

    ##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML/##FIC_MIS_DATE##/OUT- BOUND/FEEDBACK

    ##FTPSHARE_PATH##/SANCINFO/STAGE/SEPA/inputXML/##FIC_MIS_DATE##/INBOUND/ FEEDBACK

  • The logs of the batch are available in the following path:

    ##FIC_DB_HOME##/log/TF_XML

    For example, /scratch/fccmappchef/SANC807/SANC807/ficdb/log/TF_XML

    Note:

    When we take an action (RELEASE/BLOCK) on an alert from the Investigation User Interface, a feedback XML is recreated for the corresponding file with the name ##FILE_NAME##_feedback.xml and the name of the previous file with the same name becomes ##FILE_NAME##_feedback_1.xml inside the FEEDBACK folder. So, the ##FILE_NAME##_feedback.xml is always the latest feedback file for a corresponding message XML.

To run the batch, follow these steps:

  1. Navigate to the Run page. For more information, see the Run Definition Menu.

    Figure 8-19 Run Page


    Description of Run Page follows This illustration shows the batch, TF_SEPA_messages_batch_process, that must be run in order to process the ISO20022 messages.

  2. Select the TF_SEPA_messages_batch_process batch and click Fire Run. The Fire Run page is displayed.

    Figure 8-20 Fire Run Page


    Fire Run Page

  3. Select Single as the Request Type.
  4. Select Create & Execute in the Batch field. The MIS Date field is displayed.
  5. Select the date on which you want to execute the run. This date must be the same as the folder you create before you run the ISO20022 batch. In the example shown, since the MIS Date folder name is 20190913, the date you must select is 09/13/2019.
  6. Click OK.

A message "Batch execution is in progress" is displayed. Click Close to go back to the Run

page. After the batch is executed, you can view the batch details on the Batch Monitor page.

To access the Batch Monitor page, click Operations , and then click Batch Monitor. The Batch Monitor page has details of all batches. The batch you have executed is the last in the Batch Details list. To run the batch, follow these steps:

  • Select the Batch and the MIS Date. After you select the MIS Date, the batch ID appears in the Batch Run ID field.

    Figure 8-21 Batch Monitor Page


    Batch Monitor Page

  • Select the batch ID.
  • Click Start Monitoring. The task details associated with the batch appears in the Task Details section. You can also view and export the event logs for the batch in the Event Log section.

    Figure 8-22 Tasks in the Batch Monitor Page


    Tasks in the Batch Monitor Page

    Note:

    If the batch run fails, you must restart the batch. In this case, the batch run ID changes.

The task details are as follows:

Table 8-4 Task Details

Task ID Task Name Task Description
Task1 TF_CallXMLParser Parses the XML data into the pre-pro- cessing tables.
Task2 TF_CallXMLEDQ Calls EDQ data to check if there are any matches.
Task3 Message Data Attributes NA
Task4 TF_CallXMLRTIPopulation Moves data from the ISO20022 configu- ration tables to the SWIFT configuration tables to generate OBI reports.
Task5 TF_CallXMLAlertGeneration Creates alerts and loads data into the alert tables.
Task6 TF_CallXMLImmediate- FeedbackCreation Populates the feedback table.
Task7 TF_CallXMLImmediate- FeedbackFileGeneration Generates the feedback in an XML for- mat in the INBOUND/feedback direc- tory for the date on which the run is triggered.
Task8 TF_CallXMLHighlight

Populates the highlighted column in the

fsi_rt_al_raw_data table.
Task9 TF_CallUpdateAddi- tionalMsgDtls Populates the post-processing alert table with the additional details provided for the alert.
Task10 TF_CallXMLStructuredSepa Populates the data in the Structured Message tab in the Investigation User Interface.