US SAR- 8125: Miscalculation Of Suspicious Activity Date Range (Doc ID 3027308.1)

Last updated on AUGUST 23, 2024

Applies to:

Symptoms

On CRR 8.1.2.5.0: The suspicious activity date range is currently populating based on the oldest and newest transaction date for all of the transactions added to the corresponding ECM case, not just the transactions marked as suspicious. The expected behavior is that only the transactions marked as suspicious would be calculated in the date range.

Steps:

1. In ECM, take AML_SUR case
2. Check transaction tab having label 'Suspicious' 'evented' and 'surrounding'
3. Generate a use case which has one 'evented' transaction date is different than 'suspicious'
4. post it from ECM to CRR
5. Login to USSAR and check 'Suspicious Activity information'
6. start date and end date considered evented transaction date

Expected: it should calculated date range for only transactions marked as suspicious.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.