How can we add additional details for cdd review page?  I can see your screenshot is for alert, accout and customer pages. Thanks ... View more

Alert generation in AML and CDD 8.3 is governed by the VI 10.8 Scenario Admin. Scenario flows generate alerting events, that role up into alerts. There is typically only one alert per actionable entity per Domain. The flow, including the summary scenario, will only create an alert if the alerts does not already exists and conditions stipulated in the flow are met. If an alert already exists, it is more a question if the alert gets re-activated, i.e. a new alert version being created.   There are few limitations to the logic one can include in the summary scenario. The way you describe your use case seems something that can either be set as conditions in the summary scenario or by executing some of that business logic in the prep tables.    If you feel this does not answer your question, feel free to reach to me directly (maarten.van.dijck@sas.com) so that we can address any specific questions you're encountering. ... View more

Hi @Maarten_at_SAS , thank you for sharing your valuable suggestions.   I have explored around this. We can insert records in Lookup tables using DB query. There won't be any history in this case, as you highlighted. It works normally and whenever there will be any change for this value from VI, history will be created against it. System doesn't throw any errors. I thing, we can make entry in the history table as well along with current table, although I didn't test this.   Regarding ID, system generates alpha-numeric ID. I kept numeric values and tested same. It's working fine, it should not conflict ever with system generated alpha-numeric ID.   ... View more

@manishiiita wrote:   We are using UTF-8 encoding on SAS Server end. On SQL DB, the encoding is SQL_Latin1_General_CP850_CI_AS. Ideally, we should have UTF-8 encoding on DB side as well to resolve this issue I think you've probably identified the issue right there.  I think you need to change the encoding of the database so that it matches, at least that's the first thing that I would try.   The alternative is to experiment with the various encoding options.  Here's a recent paper that discusses some of the options:  https://www.sas.com/content/dam/SAS/support/en/sas-global-forum-proceedings/2020/4530-2020.pdf   Jim ... View more

Hi MSMM, We have found the root cause of the issue and the account number mentioned in error is not having account_key or party_key present in the fsc_party_account_bridge table. You need to check for those key in fsc_party_account_bridge table. ... View more

To me, this looks like you are dealing with AML (Anti-Money Laundering) requirements that are specified in law by many governments. SAS has specific products for this, as do other vendors. If so, then providing more context to what you are doing would be helpful. ... View more

Are you saying that you will create separate users for Branch Manager or OM at Branch to execute this process? How many branches do your bank have?   Yes, viewing alerts individually is difficult here. As routing is only possible at Entity level, you can't route individual alerts. You can propose users to take actions on all alerts except those where RMs / OMs feedback is required and then route it to them. Still, it will have conflicts as next day new alerts will be clubbed under same Entity.   I would propose to go with my previous comment that there is no Work Flow available in SAS AML system to reach out to Branch/RM. Compliance Analysts / Investigators have to reach out to Branch/RM for additional information through outlook / emails (i.e. outside SAS AML system).   I find, below approach difficult in terms of hardware sizing as well. Have you done hardware sizing, there is a question there for number of concurrent users as well. There you might face problem. ... View more

@BabarSThis should be simple.   There are two parts of job: write a job to select alerts older than defined period and extract in Excel / CSV format. Another part of job will be for Email by attaching above extracted file. Add all User IDs in the email who are to be notified.  Above Job will run at the end of AGP and notify all users about the pending alerts older than a certain period.   I hope this will be helpful. ... View more

@afzalbaig  - Unfortunately @manishiiita has given you advice which applies to VA 7.x not VA 8.3. SAS Management Console isn't available under SAS Viya, the platform VA 8.3 runs on. Unfortunately we don't have VA 8.3 so I'd only be able to help by searching documentation.   I suggest you start reading up on the Viya documentation regarding administration: https://documentation.sas.com/?cdcId=calcdc&cdcVersion=3.4&docsetId=calchkcfg&docsetTarget=n00004saschecklist0000config.htm&locale=en   Environment Manager could be where you set up user permissions. ... View more