This looks like a new question, so you may want to create a new post rather than replying to this one with more information. The documentation on AML 7.1 has an Alerts section that might answer your question. https://support.sas.com/en/software/sas-anti-money-laundering-support.html#0e61fe39-4010-49dd-bf5b-b2791ed4f72b ... View more

Glad I could be of help. If you have any concerns I would look at this log: root_folder/sas/viya/config/var/log/svi-indexer/default/sas-svi-indexer_xxxx.log or take a closer look at the tables in the postgres schema "svi_indexer".  ... View more

As we have written in the description for the meeting, these meetings is for knowledge sharing between users of the SAS’s AML solution!   If we cannot see that you have access to the SAS AML solution, we will not sent you a link to the meeting. But if this is a mistake please contact me or Henrik.Koch@sas.com.   Regards, Frans Holm ... View more

@AbdulGhani I can't see anything wrong in your SCD2 configuration. SCD2 in your DIS version should do the job. I've set up a sample DIS job which I'm attaching here. The job is "self contained" and the only thing you need to do is assign a library to the target table during import (Just remove the .zip extension from the file name. That was necessary in the filename for attaching the file here).   As @LinusH already mentioned it's weird that your valid_to_dttm column shows a date and not a datetime value. Is that just the format you're using or is there something else going on? Given that you've got an issue with the date alignments that's eventually the place where you need to fully investigate and explain why we only see a date value.   On a side note: Your target table is called Financial_Account_Chng. I believe the purpose of this table is to hold account information which changes rather frequently (so not really slowly). For not blowing up table Financial_Account. such account attributes get stored in the _chng table. If so then the _chng table needs to be narrow and you have to reduce the number of columns to the minimum required (only the columns which change too frequently for storing in Financial_Account). You also shouldn't have any unmapped business columns in the _chng table or you're just asking for performance issues (as the table will quickly grow). If that's the SAS DDS you're loading into then from my experience the _chng tables are the ones where you'll be facing performance challenges. It might be worth to consider to create a reusable custom transformation which does the job more efficiently than the SCD2 loader. Happy to elaborate further if that's of interest to you.   ... View more

Hi Erik, I am working in the virtual lab and from the virtual lab I cannot open files from my own computer. Regards, Lyanne ... View more

Thanks for your reply Erik!! ... View more

Hi Erik,   thank you for your reply. I found the problem: I was downloading and uploading to and from the same database server. So even if it had worked I wouldn't have had the data where I wanted it (in the LASR server). I chose the correct library and now everything is working as expected.   Regards, David ... View more

It is only the final report(s) for the end-users that have this limit (that's what the Designer is for), and that should be fine. It should not be necessary to create a report with more than a few thousand rows to look at. When the users want to look at / search the detail data, I create a list report with a control object at the top (a drop down filter etc, or a text search box) with a default value that returns less than 40 000 rows. You can add multiple filters so the users are always able to return less rows than the limit (and add a text box with a warning about the limit). This works fine, your list report will always show a default filtered table, and the users can search or drill down to retrieve the rows they need.   ... View more

Hi Filip, you are correct - with read access to a table you can create a report based on it, but you are not able to save the report unless you have write access to the folder you want to save it to. Unless the data are sensitive, I give all users read access - but create a separate folder for "official reports" that only data administrators have write access to. That way users can get to know the data, play around with it, but only save the results/reports to their own personal folder (or a shared folder for drafts). Re-reading your original question, I see I was to quick - to open a report (view), you also need read permission on the table. That implies you can create a report based on the table, you are only able to restrict where the report can be saved. ... View more

You can also try this code in the expression field (functions are usually most efficient):   IFN(CLAIM.CLAIM_AMT_TYPE_CD = '2' AND CLAIM.SUBTYPE_CD = '2', F_CL_CLAIM.AMT, 0)   This IFN function returns the result (AMT) if condition is true, otherwise returns 0 (or any other value you want). Remember to map all input fields to the expression (using the SQL Join). ... View more

A simple solution would be to create a VA front page (your portal) with a list of all the reports (use text and images with links to the reports to make this look nice) from a regular report. This first page can be customized using SAS Theme Designer to get the right "look and feel" (as well as all the reports). User can access this portal page directly, or from the hub (where the admin have created a portlet for this front page and published to all users). ... View more