Problem Note 62833: The transactions_prep.sas source code does not consider scenario duration parameters in the SAS10206, SAS10220, SAS10225, and SAS10230 scenarios
In SAS® Anti-Money Laundering, when you determine the number of days to include in the MST_PREP.PARTY_TRANSACTIONS preparation data set, the following scenario parameters are not considered:
- p10206_scen_duratn_bus_day_count (used for SAS10206, Large Total Cash Transactions by Risk Classification)
- p10220_scen_duratn_bus_day_count (used for SAS10220, Large Incoming Wires by Risk Classification)
- p10225_scen_duratn_bus_day_count (used for SAS10225, Transactions in Round Amounts by Risk Classification)
- p10230_scen_duratn_bus_day_count (used for SAS10230, Activity Dominated by Wires by Risk Classification)
These scenarios denote the number of business days to use in an interval in a scenario analysis.
As a workaround, modify the PROC SQL statement for the fcf_create_pty_trans_view macro routine in the transactions_prep.sas code. You should include a parameter name like "p%_scen_duratn_bus_day_count". An example follows:
proc sql noprint;
select max(input(sp.parm_value,best32.)) into :numdays
from seg_kc.fsk_header h,
seg_kc.fsk_scenario s,
seg_kc.fsk_scenario_parameter sp
where h.header_id=s.header_id and
upcase(h.denorm_table_name) = "PARTY_TRANSACTIONS" and
upcase(s.scenario_status_code) = "ACT" and
upcase(s.current_ind) = "Y" and
upcase(s.logical_delete_ind) ne 'Y' and
s.scenario_id = sp.scenario_id and
(sp.parm_name like 'p%_num_days' or sp.parm_name like 'p%_scen_duratn_bus_day_count') and
/* These scenarios do not need transactions */
scenario_name not in ('SAS10032','SAS10034','SAS10035');
quit;
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Anti-Money Laundering | Microsoft® Windows® for x64 | 6.3 | | 9.4 TS1M2 | |
64-bit Enabled AIX | 6.3 | | 9.4 TS1M2 | |
64-bit Enabled Solaris | 6.3 | | 9.4 TS1M2 | |
Linux for x64 | 6.3 | | 9.4 TS1M2 | |
*
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.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2018-09-12 09:34:40 |
Date Created: | 2018-08-28 13:28:58 |