AML Cases Are Not Getting Created After Running Newly Created Batches.
(Doc ID 2875835.1)
Last updated on APRIL 24, 2023
Applies to:
Oracle Financial Services Crime and Compliance Management Transaction Monitoring Cloud Service - Version 10.0.0.0.0 to 10.0.0.0.0 [Release 10.0.0.0.0]Information in this document applies to any platform.
Symptoms
AML cases are not getting created after running newly created batches.
Steps to reproduce/followed
Answer: 1. Created the below new batches..
TESTbank_AMLDataLoad------New Batch for TM
TESTbank_CustomerChangeLog_May
TEST_Ingestion------New Batch for TM
TESTTMScenario_weekly------New Batch for TM
TESTTMScenario_Biweekly------New Batch for TM
TESTTMScenario_Monthly------New Batch for TM
TESTbank_CMIngestion------New Batch for TM
TEST_TM_ECMProcess_310522------New Batch for TM
TESTbank_KYCDaily_090522------New Batch for KYC
TEST_KYCToCaseManagement------New Batch for KYC
TESTbank_FullLoadCustomer_090522------New Batch for CS
TESTbank_IndividualScreening------New Batch for CS
TESTbank_ScreeningToCaseManagement_310522------New Batch for CS
2.We are using copied pipelines for all the batches(Please find the attached document with the details of pipeline and job name).
3.Run the batches.
4.AML Cases are not getting generated.
5.Verify the alerts through threshold simulator.
6.We can see that alerts are getting generated in threshold simulator and no cases in UI.
7.If we are running the batches in below order we are getting the alerts,
AMLDataLoadBatch(OOB)
CustomerChangeLog(OOB)
Ingestion
TMScenario_weekly
TMScenario_Biweekly
TMScenario_Monthly
CM Ingestion(OOB)
TM_ECMProcess(OOB)
KYCDaily(OOB)
KYCToCaseManagement(OOB)
FullLoadCustomer(OOB)
IndividualScreening(OOB)
ScreeningToCaseManagement(OOB)
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |