5.1.3 Using Scenario Conversion Utility for ASC

Scenario Conversion Utility (SCU) converts BD scenarios to Compliance Studio notebooks for the scenarios and respective thresholds.

Note:

• The utility converts only BD AML scenarios to Compliance Studio notebooks based on the rule matcher algorithm.
• This section is applicable only if you are using Scenario Conversion Utility and Automated Scenario Calibration use case.

Prerequisites

• Ensure that the OFS Compliance Studio v8.1.2.9.0 is installed and running.
• Make sure that all the Compliance Studio patches are applied.
• Ensure that the OFS BD v8.1.2.x.x is installed and running.
• Ensure that the following tables and sequence exist in the Compliance Studio Schema:
  • Tables:
    • ds_notebook
    • ds_paragraph
  • Sequence:
    • seq_paragraph

Calendar Notebook

The calendar notebook is used to set calendar information and processing batch date for execution of the scenario notebook.

Import SCU_Set_Calendar.dsnb notebook into the sandbox workspace and pointing to the non-prod BD atomic schema.

The following jars are available in the <OFS_COMPLIANCE_STUDIO_INSTALLATION_PATH>/ deployed/ficdb/Scenario-Conversion-Utility/db_tools/lib directory.

• dbtools.jar
• kddcore.jar
• log4j-api-<version>.jar
• log4j-core-<version>.jar

Note:

A few OOB scenarios use re-alert lookback, which helps to avoid redundant alerts in AML. To incorporate the same in SCU, VW_REVIEW is used as a union of alerts in AML and events in SCU.

To ensure that previously alerted entities from AML are still considered in these scenarios, users can customize VW_REVIEW by creating it as shown below.

"CREATE OR REPLACE FORCE EDITIONABLE VIEW VW_REVIEW ("REVIEW_ID", "PRCSNG_DT", "CNTRY_KEY_ID") AS 
    SELECT
        e.v_event_cd  review_id,
        e.prcsng_dt,
        m.v_entity_cd cntry_key_id
    FROM
        fcc_am_events e,
        fcc_am_event_entity_map m
    WHERE
        e.v_event_cd = m.v_event_cd
        AND m.v_focus_flag = 'Y';"