Sanctions Screening for SAP®

Please follow the steps below for a quick and easy implementation of our SAP client:

Download the ABAP transport 

from our GitHub repository: https://github.​com/REMEDYNE/Sanctions.io and import it to your SAP systems.

Please note the report is intended to be used as a template for creating your own client for the sanctions.io API: there is no AUTHORITY-CHECK implemented, which means everyone with permission to run ABAP reports in SAP can use the report. Appropriate controls should be added to enforce access control.

Two steps are required to use the data for sanctions lists screenings:

Getting an API key

Please register for a free trial account at api.sanctions.io. Once you have signed up you will get access to an API key which you will need to maintain in the parameters for this check. 

Enabling the SSL connection

The SAP system has to connect as SSL client to api.sanctions.io and therefore requires an active SSL service and has to trust the SSL server.

To enable this:

a. Check the SSL server status of the SAP system in transaction SMICM -> Goto -> Services:there must be an active HTTPS service.

b. In transaction SM59, create an HTTP Connection to External Server (type G):Name of the connection= SANCTIONS.IOTarget Host:Port= api.sanctions.io:​8443Logon Procedure=No Logon (authentication uses the API key that is sent via HTTPS)SSL Status: ActiveSSL Client Certificate: SSL Client (Anonymous)

c. In transaction STRUST, establish a trust relationship to the SSL server at https://api.sanctions.io:8443Download the self-signed X.509 certificate from https://api.sanctions.io:8443

Import this certificate to the certificate list of the SSL Client (Anonymous).

We use a self-signed certificate with extended lifetime so that maintenance of the trust relationship in STRUST becomes minimal and you do not have to renew the certificate every few months. If you prefer a CA-issued SSL server certificate, you can use port 443.