AML 7.

x Reporting Deployment Document

Version 2.0

December 12, 2017

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 AML Reporting Deployment Document

Copyright Copyright © 2017, SAS Institute Inc., Cary, NC, USA. All rights reserved.
Produced in the United States of America.

Style Version: 1.0 July 2008.

Content Version: 1.0 February 2009.

Disclaimer No part of this publication may be reproduced, stored in a retrieval system,

or transmitted, in any form or by any means, electronic, mechanical,
photocopying, or otherwise, without the prior written permission of the
publisher, SAS Institute Inc.

U.S. Government Restricted Use, duplication, or disclosure of this software and related documentation
Rights Notice by the U.S. government is subject to the Agreement with SAS Institute and
the restrictions set forth in FAR 52.227-19, Commercial Computer
Software-Restricted Rights (June 1987).

Trademarks and Patents SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513.

SAS® and all other SAS Institute Inc. product or service names are
registered trademarks or trademarks of SAS Institute Inc. in the USA and
other countries. ® indicates USA registration.

Other brand and product names are registered trademarks or trademarks

of their respective companies.

Confidentiality This document is provided for informational purposes. SAS’ contractual

commitments are contained solely in the agreement for professional
services executed between SAS and the Client. This document is the
confidential and proprietary property of SAS Institute Inc. This document
may contain approaches, techniques and other information proprietary to
SAS. This document shall not be disclosed in whole or in part to third
parties without the prior written consent of SAS.
 2

AML REPORTING DEPLOYMENT DOCUMENT

Contents

1 Document Information.................................................................3
1.1 Revision History..............................................................................................................3
1.2 Document Distribution....................................................................................................3

2 AML Reporting Deployment Overview.......................................4

2.1 Steps for AMLR Code deployment................................................................................4
2.2 Deploy AMLR raw parameters and AMLR SAR REASON tables................................6
2.3 Steps to create LASR tables..........................................................................................7
2.4 Steps to configure Autoload..........................................................................................9
2.5 Steps to Autoload the LASR tables...............................................................................9
2.6 Steps for Reports Deployment.......................................................................................9
2.7 Steps to view and Verify VA reports............................................................................12

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 3

AML REPORTING DEPLOYMENT DOCUMENT

1 Document Information

1.1 Revision History

Version By Date Description
V 1.0 Subin Velleringatt May 2, 2017 Initial draft and AMLR Release 1
V 2.0 Abhinandan Goswami December 11, 2017 Release 2 – Added SAR and CTR
Swapnil Pasalkar Reports
Jagjit Singh
Ashok Mirchandani
V 2.01 Ashok Mirchandani Dec 18, 2018 Renamed reports from AML Reporting
– xxx to AMLR – xxx convention

1.1 Document Distribution

Each new version of this document is to be distributed to the following people.

Global Security Intelligence Solutions

Professional Services Competency Center (PSCC)

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 4

AML REPORTING DEPLOYMENT DOCUMENT

2 AML Reporting Deployment Overview

This document describes the deployment of AML Operational Reports (AMLR) in SAS Visual
Analytics (VA) on AML 7.x platform.

An overview of the deployment steps is listed below:

1. AMLR Code deployment

a. Deployment of FCS file directory for AML71 multibank configuration
b. Deployment of AMLR codes
2. AMLR Raw parameters deployment
3. Create LASR tables(AMLR_ALERTS, AMLR_CASES,
AMLR_RR_BRANCH,AMLR_SAR and AMLR_CTR)
4. Configure the Autoload for VA(if required)
5. Autoload the LASR tables
6. AMLR Reports Deployment
7. View and Verify VA reports

2.1 Steps for AMLR Code deployment

The code deployment step assumes that fcs deployment steps have been completed. If the
deployment has not been completed, follow the steps in https://gitlab.sas.com/SI-
Tools/AMLEnvDeploy to complete deployment.

1. Login to AML71 machine as “sas” or any user with standard privileges.

2. Ensure that AML71 machine has fcs folder setup for multibank exists.
3. Download the complete zip package for AMLR repository from the following link
a. https://gitlab.sas.com/SI-Tools/AMLR
b. To download click Download.zip as shown in the image below

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 5

AML REPORTING DEPLOYMENT DOCUMENT

4. Copy the extracted global macro codes from AMLR\ETLCodes\Global\macros (of the
downloaded repository) to D:\opt\sasinside\Projects\global\macros path.

a. amlr_create_lasr_table_alert.sas
b. amlr_create_lasr_table_cases.sas
c. amlr_create_lasr_table_rr_branch.sas
d. amlr_custom_reporting_formats.sas
e. amlr_fsk_lov_formats.sas
f. amlr_load_reporting_parameters.sas
g. amlr_raw_extract_alert.sas
h. amlr_raw_extract_case.sas
i. amlr_raw_extract_rr.sas
j. amlr_user_mapping_formats.sas
k. declarelasrlibrary.sas
l. fcsautoexec.sas

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 6

AML REPORTING DEPLOYMENT DOCUMENT

m. amlr_create_lasr_table_ctr.sas
n. amlr_create_lasr_table_sar.sas

5. Copy the extracted codes from AMLR\ETLCodes \programs (of the downloaded
repository) to D:\opt\sasinside\Projects\bank1bu\programs path.

a. amlr_alerts.sas
b. amlr_cases.sas
c. amlr_create_reporting_extracts.sas
d. amlr_rr_branch.sas
e. amlr_sar.sas
f. amlr_ctr.sas

2.2 Deploy AMLR raw parameters and AMLR SAR

REASON tables

1. Open SQLDeveloper application.

2. Setup the oracle connection for BANK1KC by providing appropriate values for username (oracle
schema name – BANK1KC), hostname (server on which oracle is running) and service name
(oracle database instance name)
3. Login to Knowledge Centre database of the corresponding business unit. i.e BANK1KC
4. Run AMLR_PARAMETERS_CREATE_DDL.sql and amlr_sar_reason_create_ddl.sql DDL
from the downloaded AMLR/DDL folder on the KC schema of the respective BU to create the
corresponding AMLR_PARAMETERS and AMLR_SAR_REASON tables. The following
output shows successful execution of the DDL statements.
5. Run AMLR_PARAMETERS_INSERT_SCRIPT.sql and amlr_sar_reason_insert_script.sql insert

script from the downloaded AMLR/DDL folder on the KC schema of the respective BU to insert
data into the corresponding AMLR_PARAMETERS and AMLR_SAR_REASON tables

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 7

AML REPORTING DEPLOYMENT DOCUMENT

1.2 Steps
to create
LASR
tables

1. Check fcsautoexec.sas (or other file(s) which may be used for initializing the SAS libraries) for
the code shown below. This code may be added to fcsautoexec before executing the file.
The specific code changes made to fcsautoexec.sas is shown below. The code has been attached
in a text file for ease of use.

fcsautoexec AMLR code.sas

Add lines to derive the bnkval from the parameter passed and format library path for autoload
/*To access pre-installed BANKXBU folders for config exec files, extracting the numeric value from
BNK macro variable and replacing as BANK1BU,BANK2BU,etc*/
%let num=%sysfunc(compress(&bnk,,kd));
%let bnkval=BANK&num.BU;

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 8

AML REPORTING DEPLOYMENT DOCUMENT

 %let
fmts_global_format_path=&sasbase.\AppData\SASComplianceSolutions\&bnkval.\AutoLoad\Formats;

The rpt block must be having the FMTS_G library reference

%if %length(&rpt) gt 0 and &rpt ne 0 %then %do; /* rpt is name variable checked for executing
rpt_autoexec.sas */
libname FMTS_G "&fmts_global_format_path";
/*Declare BANK1BU LASR library*/
%LET AL_META_LASRLIB=%str(Compliance Solutions &bnkval LASR Library);
%declarelasrlibrary(libref=LASRSRV, name=%str(&AL_META_LASRLIB));
%include "&cshome.\&bnkval.\custom\config\rpt_autoexec.sas";
%end;

2. Optional Step: Execute ‘AML 7.x Reporting Test-data User Guide Windows v1.0’ to generate
mock data if no AML AGP data is available.

AML 7.x Reporting

Test-data User Guide Windows v1.0.docx

Note: If no AML AGP data available to the environment, the test data generation code
‘create_mock_data_for_demo.sas’ should be executed.

3. Open a new Enterprise Guide session.

4. Load the codes ‘amlr_create_reporting_extracts.sas’,‘amlr_alerts.sas’ and ‘amlr_cases’ into E-
Guide from ‘D:\opt\sasinside\Projects\bank1bu\programs’ (path relative to the opted bank
unit)
5. Run amlr_create_reporting_extracts.sas and verify it is completed without any errors.
6. Run amlr_alerts.sas and verify it is completed without any errors.
7. Run amlr_cases.sas and verify it is completed without any errors.
8. Run amlr_rr_branch.sas and verify it is completed without any errors.
9. Run amlr_sar.sas and verify it is completed without any errors.

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 9

AML REPORTING DEPLOYMENT DOCUMENT

10. Run amlr_ctr.sas and verify it is completed without any errors.

1.3 Steps to configure Autoload

Optional step: Please refer to the below link for information on configuring Autoload for SAS VA
application. This step is only necessary is autoload has not been configured.

http://support.sas.com/training/tutorial/gel/gelva03.html

1.4 Steps to Autoload the LASR tables

1. Navigate to the below path (path relative to the opted bank unit),
D:\opt\sasinside\Config\Lev1\Applications\SASComplianceSolutions\BANK(n)BU\AutoLoad
2. Execute the batch script ‘runsas.bat’ and verify its completed successfully by checking the latest
log in
“D:\opt\sasinside\Config\Lev1\Applications\SASComplianceSolutions\BANK(n)BU\AutoLoad\
Logs” for no errors.

1.5 Steps for Reports Deployment

Step1: Launch SAS Management Console (SMC) and login using “sas” user credentials.

Step2: Navigate to the folder /Products/SAS Compliance Solutions BANK1BU/Reports

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 10

AML REPORTING DEPLOYMENT DOCUMENT

Step3: Import AMLR_REPORTS.spk (from the downloaded repository folder AMLR/spk) in the newly
created AMLR Reporting folder of the SMC.

Right click on AMLR Reports folder -> Click on Import SAS package -> Choose the downloaded
AMLR_REPORTS.spk from your local machine where you have the downloaded AMLR repository
AMLR/spk.

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 11

AML REPORTING DEPLOYMENT DOCUMENT

Once the reports are imported, the AMLR Reporting folder should contains two folders

1. Alerts and cases reports.

2. SAR and CTR Reports.

1.6 Steps to view and Verify

VA reports

1. Login to VA with sasdemo user(or any valid user) -> Click on ‘Browse’ -> Choose ‘AMLR-
Reporting’ ->Choose the reports from the Alerts and cases Reports folder or SAR and CTR
Reports Folder.(Follow the below highlighted rootpath)
2. Ensure that there are 18 reports available
3. Open each report and navigate through the sections, ensure that each section has charts and grid
data.

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.

 12

AML REPORTING DEPLOYMENT DOCUMENT

CONFIDENTIAL – Copyright © 2017 SAS Institute Inc. All Rights Reserved.