SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 69297: You receive a B18 filing type error message when validating Suspicious Activity Reports (SARX) in SAS® Anti-Money Laundering

DetailsHotfixAboutRate It

The error shown below might occur when you validate the SAS Anti-Money Laundering SARX after you change the Type of Filing in the report:

   image label

For example, you encounter the issue if you change the Type of Filing from Initial Report to Correct/Amend Prior Report and back to Initial Report in SARX. When the Type of Filing value is changed, the application initializes the underlying vm.report.priorAgencyRefId field to blank (''), which Microsoft SQL Server treats differently from null and causes the validation error.

This issue is encountered only when you use the Microsoft SQL Server database.

The workaround is to override the underlying SQL query. Note the use of NULLIF() function in prior_agency_ref_id:

sasaml.report.savereport.sql=UPDATE FSK_RC_REPORT SET report_status_code=?, report_ready_code=?, report_desc=?, form_config_key=?, parent_object_name=?, parent_object_key=?, parent_create_date=?, correction_ind=?, root_report_key=?, prev_report_key=?, prior_agency_ref_id=NULLIF(?,''), ui_json=?, narrative_long_desc=?, create_user_id=?, create_date=?, lstupdate_date=?, version_number=version_number+1, lstupdate_user_id=?, logical_delete_ind=?, owner_user_long_id=?, queue_code=? where report_key =?

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Anti-Money LaunderingMicrosoft® Windows® for x647.1
64-bit Enabled AIX7.1
64-bit Enabled Solaris7.1
Linux for x647.1
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.