AML REPORTING DEPLOYMENT
DOCUMENT
Version 2.1
Owner
PSCC
AML 7.x Reporting Deployment Guide
DOCUMENT HISTORY
Document Version Control
Version Status Date Changed by Change description
1.0 Draft 02/05/2017 Subin Initial draft
1.1 Draft 11/02/2017 John York Updated Images, directories, and steps
1
AML 7.x Reporting Deployment Guide
Contents
DOCUMENT HISTORY..................................................................................................................................1
Purpose.......................................................................................................................................................3
Overview of Deployment Steps...................................................................................................................3
Steps for AMLR Code deployment...............................................................................................................4
Steps to deploy AMLR raw parameters table..............................................................................................6
Steps to create LASR tables.........................................................................................................................7
Steps to configure Autoload........................................................................................................................7
Steps to Autoload the LASR tables..............................................................................................................8
Steps for Reports Deployment....................................................................................................................8
Steps to view the VA reports.....................................................................................................................11
VA Report Verification...............................................................................................................................11
Index..........................................................................................................................................................12
Link to the AML Environment (AML-E) Deployment Document............................................................12
2
AML 7.x Reporting Deployment Guide
Purpose
AML-R provides a rich collection of out-of-the-box interactive reports on SAS Visual Analytics (SAS VA
7.x) multi-tenant platform.
The professional service collection of reports has been derived from years of customer experience. This
operational management reporting package can be extended to develop custom reports to meet
specific reporting business requirements.
These reports can be accessed and viewed after installation and deployment. AML-R schema tables can
be easily used to create new custom reports.
Overview of Deployment Steps
AMLR Deployment consists of high-level steps, 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 and AMLR_CASES)
4. Configure the Autoload for VA (if required)
5. Autoload of the LASR tables
6. AMLR Reports Deployment
7. View the VA reports
8. VA report verification
The following sections explains each of the above steps in detail.
3
AML 7.x Reporting Deployment Guide
Steps for AMLR Code deployment
AML-R deployment assumes that AML Environment package has also been deployed. The AML
Environment package is a PSD setup process that configures a standard project directory structure, and
code base.
Follow these instructions to deploy the AML-E package if needed:
1. Login to AML71 machine as ‘sas’ user (or any user who has the appropriate privileges to do so).
2. Validate AML Environment has been setup according to AML-E instructions above.
3. Validate fcsausotexec() is functioning, and runs without generating any errors by running the
following code in Enterprise Guide: %fcsautoexec(aml_auto=1,bnk=BANK1BU);
4. Below we have the link to the AML-R Git repository.
a. https://gitlab.sas.com/SI-Tools/AMLR
5. Download the complete zip for AMLR repository from the below link.
a. If you are a SAS employee, then you can log into gitlab by using your Active Directory
(LDAP or Windows userid/password (not your email address)). You do not need to
request an account; simply log on. This project is available to all SAS employees.
b. External users will have to get in touch with their SAS representative.
4
AML 7.x Reporting Deployment Guide
6. Unzip to your compute server into your project directory. For testing purposes, we will rename
the unzipped folder to ‘AML-R’.
7. Copy and extract the global macro codes to the appropriate folders based on your AML-
Environment setup. For testing purposes, copy the extracted global macro codes from AML-
R\ETLCodes\GLOBAL\macros (of the downloaded repository) to
D:\opt\sasinside\fcs\GLOBAL\macros.
NOTE: the \GLOBAL\macros path is for Windows, however Unix should follow a similar
process
The \GLOBAL\macros directory holds all the global macros that will be called during the
processing of sas code. The GLOBAL directory houses the code-base that can be used by
multiple banking units/tenants. The code-base is not tenant-specific. The macros below can be
used across all tenants in your environment.
a. amlr_create_lasr_table_alert.sas
b. amlr_create_lasr_table_cases.sas
c. amlr_custom_reporting_formats.sas
d. amlr_fsk_lov_formats.sas
e. amlr_load_reporting_parameters.sas
f. amlr_raw_extract_alert.sas
g. amlr_raw_extract_case.sas
h. amlr_raw_extract_rr.sas
i. amlr_user_mapping_formats.sas
j. declarelasrlibrary.sas
5
AML 7.x Reporting Deployment Guide
8. Copy the extracted codes from AML-R\ETLCodes\BANK1BU\programs (of the downloaded
repository) to D:\opt\sasinside\fcs\BANK1BU\programs location.
a. AML-R_alerts.sas
b. AML-R_cases.sas
c. AML-R_create_reporting_extracts.sas
Steps to deploy AMLR raw parameters table
NOTE: The user must have appropriate permissions to create tables in the KC Schema.
This guide assumes AML-R system is installed and working in an Oracle Database. At least one AGP
has to be run before this process can be executed.
1. Open SQLDeveloper application
2. Setup the oracle connection for BANK1KC by providing appropriate values for the following:
a. Connection Name: BANK1KC
b. Username: Oracle Schema name (BANK1KC)
c. Password: Orion123
d. Hostname: server on which oracle is running (localhost)
e. Port: 1521
f. Service Name: Oracle database instance name (sasbap)
3. Login to Knowledge Center database of the corresponding business unit (E.g. BANK1KC).
4. Take the AML-R_PARAMETERS_CREATE_DDL.sql DDL from the downloaded AMLR/DDL folder
and run it on the KC schema of the respective Business Unit (E.g. BANK1KC) to create the
corresponding AMLR_PARAMETERS table.
a. The AML-R_PARAMETERS table is used for labeling and creating custom calculations for
alert and other metrics used in reporting. Updating the values in this table will updates
the reports. The reports themselves don’t have to be touched.
5. Take the AML-R_PARAMETERS_INSERT_SCRIPT.sql insert script from the downloaded
AMLR/DDL folder and run it on the KC schema of the respective Business Unit (E.g. BANK1KC) to
insert data into the corresponding AMLR_PARAMETERS table.
a. Below is an image of the populated AMLR_PARAMETERS table
6
AML 7.x Reporting Deployment Guide
Steps to create LASR tables
1. If there is no AML AGP data available to the environment, the test data generation code
‘create_mock_data_for_demo.sas’ should be executed. This file is found by opening AML-
R/MockData.
NOTE: open AML7.x Reporting Test-data User Guide by clicking on the link below, for a deeper
understanding of how the mock data is being created.
http://smteam.sas.com/psd/GFFC/_layouts/15/WopiFrame.aspx?sourcedoc=/psd/GFFC/Knowledge
%20Base/Reporting%20and%20Visualization%20(AMLR)/AML%207.x%20Reporting%20Test-data
%20User%20Guide%20Windows%20v1.0.docx&action=default
2. Open a new Enterprise Guide session.
3. Type the following command to run the fcsautoexec macro. This macro runs the code used for
initializing the SAS AML libraries and Databases.
a. %fcsautoexec(aml_auto=1,bnk=BANK1BU);
4. Navigate to ‘D:\opt\sasinside\fcs\BANK1BU\programs’ (or whatever path is relative to the
opted bank unit) and load the following sas programs into Enterprise Guide and verify that they
run without any errors:
a. AML-R_create_reporting_extracts.sas
b. AML-R_alerts.sas
c. AML-R_cases
Steps to configure Autoload
Please refer to the below link for information on configuring Autoload for SAS VA application (if it’s not
configured already)
http://support.sas.com/training/tutorial/gel/gelva03.html
7
AML 7.x Reporting Deployment Guide
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\BANK1BU\AutoLoad
2. Execute the batch script ‘runsas.bat’ and verify its completed successfully with no errors by
checking the latest log, found in
“D:\opt\sasinside\Config\Lev1\Applications\SASComplianceSolutions\BANK1BU\AutoLoad\L
ogs”
Steps for Reports Deployment
1. Open SAS Management Console. Login with user sas.
2. Navigate to below folder:
a. /Products/SAS Compliance Solutions BANK1BU/Reports
3. Right-click on Reports and select “Import SAS Package…” to import AML-R_VA_REPORTS.spk
(from the downloaded repository folder AML-R/spk).
8
AML 7.x Reporting Deployment Guide
4. Once the reports are imported, the AMLR Reporting folder should contain the reports as below.
9
AML 7.x Reporting Deployment Guide
10
AML 7.x Reporting Deployment Guide
Steps to view the VA reports
1. Login to VA with sasdemo user (or any valid user) -> Click on ‘Browse’ -> Choose ‘AML-R
Reports’ ->Choose the report from the AML-R Reports folder. (Follow the below highlighted root
path)
VA Report Verification
1. Login to Visual Analytics as ‘sasdemo’ user.
2. Ensure that there are 8 reports available
3. Open each report and navigate through the sections, ensuring that each section is has
charts/grid-data visible
11
AML 7.x Reporting Deployment Guide
Index
Link to the AML Environment (AML-E) Deployment Document
https://gitlab.sas.com/SI-Tools/AMLPackageDeployDocs/tree/master/AML-E
12
