5.7.4.1 AML Scenario Processing batch
- This is a pre-seeded batch and will be available in all workspaces (Production and Sandboxes).
- This Batch can be executed in the Sandbox and Production workspaces.
- This Batch executes scenario logic and generates events in fcc_am* tables.
- Sandbox is mainly used for scenario tuning, and what-if analysis and main execution are done in Production.
Batch and Task Parameters
The Batch contains the following task named as:
- Execute_Scenario
- ECM_Event_Processing
Task 1: Execute_Scenario, Task Parameters
- Objective folder for this task:
Home / Modeling / Pipelines / AML Scenario / Scenario / Shell / Customer
- The Shell or Human Trafficking folder needs to change based on execution requirements.
- The objective parameter and Optional parameter can be changed based on the requirement. No other parameter needs to change.
- Optional Parameters:
- threshold_set_id: ID of the threshold set, Example AMEA_GENERAL.
- lookback: Number of days to look back for data. Example
30
Example: threshold_set_id=AMEA_GENERAL,lookback=30
- Edit Task Parameters and Save.
Task 2: ECM_Event_Processing, Task Parameters
- Objective folder for this task:
Home / Modeling / Pipelines / AML Scenario / Event Processing
This task does not take any optional parameters.
- Do not change any other batch/task parameters.
- AMLES event score outputs are available in the following tables:
- AMLES_EVENT_SCORES
- AMLES_EVENT_SCORE_DETAILS
- Use the following schema for the table structure to insert into the
document:
TNS: ML4AMLPRODREST/password@ofss-mum- 3629.snbomprshared1.gbucdsint02bom.oraclevcn.com:1521/fccmdb