9.7 Create Event API
The Create Event API generates events at the end of a scenario Notebook or Model for transfer to the Enterprise Case Management Application for correlation into a Case.
It accepts inputs from two tables to generate alerts that are populated in the event tables. The syntax to call the Create Event API is as follows:
SELECT FUNC_CREATE_EVENT(,) FROM DUAL;
For information on Table_1 and Table_2, see Table 9-12 and Table 9-13.
Table 1 Details
Table 1 contains information related to the direct focus. This information is
aggregated for focus. For example, the account number and the total transaction
amount for that account will be stored in the Table 1. One record is inserted for
each focus (account or customer).
Table 9-12 Table 1 Details
| Column Name | Sample Values | Description |
|---|---|---|
| V_FOCUS_TYPE | ACCOUNT | The main focus of the scenario. The value can be obtained from the kdd_dataset_base table. |
| V_ENTITY_NAME | ANDERSON | Name of the focused entity, that is, account display name and customer display name. |
| V_DATA_ORIGIN | AMLBIG | Data origin, that is, MAN, DLY, etc. |
| V_STATUS_CD | NEW | Event status code. Default value: New. |
| D_EVENT_CREATED_DATE | 3/11/2019
15:02 |
Event creation date |
| V_JURISDICTION_CD | AMEA | Jurisdiction |
| V_BUSINESS_DOMAIN_CD | a | Business domain |
| V_COMMENTS | - | General comment for the scenario |
| V_SCENARIO_CLASS | AML | Class to which the scenario belongs to, that is, AML, TC, and BC |
| V_FOCUS_CD | ACMLTERR ORFINFAC- 005 | Code for focus, that is, account internal ID in case of account |
| V_ENTITY_CD | 832 | Focus sequence ID, that is, account sequence ID in case of account focus |
| MAX_DATA_DUMP_DT | 12/10/2015 | Data Dump date for which business data is involved |
| MAX_NOT_EFT_TRANS | 0 | Specific for an account. This column can be ignored for other scenarios. |
| TOT_TRXN_AMT | 10500 | |
| TOT_TRXN_CNT | 2 | |
| EFFECTIVERISK | 9 | |
| ACTIVITYRISK | 20 | |
| RISK_CATEGORY | HR | |
| ACCT_TYPE | Seasoned | |
| TRUSTED_PRCTG | 0 | |
| PASS_THRU_PRCTG | 0 | |
| LRF_PRCTG | 0 | |
| HR_PRCTG | 0 | |
| ACT_TOT_CREDIT_TRXN_ AMT | 5400 | Threshold specific for an account. It can be different for other scenarios. |
| TH_TOT_MIN_CREDIT_TR XN_AMT | 50 | |
| TH_TOT_MAX_CREDIT_T RXN_AMT | 10000000 | |
| ACT_TOT_CREDIT_TRXN CT | 2 | |
| TH_TOT_MIN_CREDIT_TR XNCT | 1 | |
| TH_TOT_MAX_CREDIT_T RXNCT | 20 | |
| ACT_TOT_DEBIT_TRXNC T | 2 | |
| TH_TOT_MIN DEBIT_TR XNCT | 1 | |
| TH_TOT_MAX_DEBIT_TR XNCT | 20 | |
| ACT_TOT_DEBIT_TRXN_A MT | 5100 | |
| TH_MIN_DEBIT_TRXN_A MT | 20 | |
| REMARK | - | |
| SCENARIO_CD | 10000 | |
| SCENARIO_MN | RMF Account(sql) | Name of scenario notebook |
| N_RUN_ID | 84 | The Create Event API automatically creates this value |
| N_EVENT_CD | 366 | - |
| V_ENTITY_CD | 25291 | Transaction sequence ID |
| V_FOCUS_CD | ACMLNOA AC- 302 | Account Internal ID in case of account focus |
| N_ENTITY_ID | FOMLNOA AC- 301 | Transaction Internal ID |
| TRXN_DATADUMP_DT | 12/10/2015 | Transaction Data Dump date |
| TRXN_PRDCT_TYPE | WIRE_TRXN | Transaction Product type. The value can be obtained from the kdd_dataset_base table. |
Table 2 Details
Table 2 details contains information on all the transactions involved in
alert generation.
Table 9-13 Table 2 Details
| Columns | Sample Values | Description |
|---|---|---|
| V_ENTITY_C D | 25291 | Transaction sequence ID |
| V_FOCUS_C D | ACMLNOAAC-302 | Account Internal ID in case of account focus |
| N_ENTITY_ID | FOMLNOAAC-301 | Transaction Internal ID |
| TRXN_DATA DUMP_DT | 12/10/2015 | Transaction data dump date |
| TRXN_PRDC T_TYPE | WIRE_TRXN | Transaction Product type. The value can be taken from the kdd_dataset_base table. |