Hi @MG18, I'm addressing both of your queries below:
1) How to test this scenario SAS10079 and what kind of data should be in FSC_PARTY_DIM table so it will generate alert for SAS10079 scenario ?
Do you know the functionality of any OOB watchlist scenario (SAS10079-82)? The matching logic is almost same in all these scenarios except for their types i.e. Scenario SAS10079 is for PEP on watchlist, SAS10082 is for Terrorist on watchlist and so on.
Coming to scenario SAS10079, below is the functionality of this scenario (copied from guide):
This scenario compares all customers, not already designated as politically exposed persons (PEPs) in the customer table, to the entity watch list table. For an individual, when checking for a full name match, both the full name columns (party_name and entity_name) as well as the first/middle/last name columns are compared. If a match is found on either exact name or name match code, then the scenario checks additional match components for potential matches. For individuals, the scenario checks for matches on country, state/province, and city match codes, as well as exact matches for birthdate or birth year and tax ID. For organizations, the scenario checks for matches on country, state/province, and city match codes, as well as exact matches for tax ID. A match is found if a customer is designated as a PEP in the entity watch list table and the minimum number of conditions to match for the entity is met. Note: this scenario requires that match codes are built for both the customer table and the entity watch list table. This scenario checks only for politically exposed persons who are not already marked as PEPs in the customer table.
Above description tells you almost everything about the scenario. Coming to your query, to test this scenario ideally you should have customers in your Party Table with (Full Name/Name+Match Code)+Additional Parameters matches as configured in scenario. Additionally, these customers should not be predefined as PEP 'Y' and in the watchlist table (Entity Watch List Dim) the respective record should have PEP flag as 'Y'. Then, there will be a match found for this customer against watch list data for PEP category.
2) Currently we are loading DOW Jones daily and monthly data in SAS AML system and i want to know how to load monthly data in AML system means whether we need to do truncate and load data for each month load or we need incremental load or already defined sas macro will take care it ?
I believe, you would have loaded complete dump once then going forward you will have to load incremental data only. You can choose to load daily or weekly or monthly incremental files and your scenarios should also be run in the same frequency. I didn't get why are you loading both the files? I have worked mostly with Worldcheck files and there the data used to be like this.
Now, the question is how to load these incremental files? It depends on you scenarios. If you simply want to screen all your customers against the incremental data as you have already screened all your customers against existing watch list data, then you should simply update change_current_ind for all old records as 'N'. It will be 'Y' only for incremental watch list data. While scenario processing, it will pick records only with Change_Current_Ind 'Y'. Please note here you might miss screening of new customers against old watch list data. So, to avoid this you can chose another method to load incremental watch list data in which only those old records will be marked as 'N' where there is some update available in the incremental data. So, for scenario execution you will have at least one active record for all watchlist entities. This all can be done using OOB watch list data loading scripts.
Hope this will be helpful. Feel free to comment in case of any further queries.
