HOW THE CONNECTOR WILL BE USED?

The Connector will be installed on ATTP as pre-delivered ABAP

code implementing standard ATTP BADIs. The BADIs call Java

Programs (SAP JCO) installed on the Java stack which will then

be used to communicate with the MDLP system.

Haugerglacisstraße 5a

97080 Wuerzburg P: +49 931 32 90 71 88

F: +49 931 32 90 91 26

www.3keys.com

WHY THE CONNECTOR IS NEEDED?

The current Country Package FP4 allows to generate reports in

XML Format and store them in the file share. The files then need

to be uploaded manually to the MDLP portal by a user and signed

with a digital signature one by one. The 3Keys MDLP Connector

enables this automated integration between SAP ATTP and

MDLP in both directions (inbound and outbound).

The MDLP-Connector is a solution provided by 3Keys

GmbH to help Pharmaceutical Companies to fulfil the

requirements of reporting to the Russian Federal

Database for Pharma goods circulation.

The Connector is the combination of pre-developed

ABAP and Java programs which are used to transfer

Russian reporting messages from SAP ATTP to the

MDLP system using a secure connection. It will also

download incoming messages from MDLP and

forward them to SAP ATTP for further processing.

The 3Keys Connector provides the monitoring for

outbound and inbound messages. The pre-

developed programs can be adopted to the client

needs.

MDLP CONNECTOR

3Keys

Automatically send reports from ATTP to MDLP API

Provide GOST TLS connection

Provide GOST Digital signature functionality via CryptoPro

library or another certified cryptographic provider

Poll MDLP for processing status of sent outbound reports

Poll MDLP for new inbound messages (6xx notifications)

and download them into ATTP

Transaction to monitor inbound and outbound Russian

reporting messages within SAP ATTP

3Keys MDPL Connector provides following

functionality:

The SAP Java Connector (SAP JCO) is a

development library that enables a Java

application to communicate with on-

premise SAP systems via SAP RFC protocol.

The SAP JCO supports both communication

directions: inbound Remote Function Calls

(Java calls ABAP) as well as outbound

Remote Function Calls (ABAP calls Java).

The Java component of the 3Keys MDLP

Connector provides GOST TLS connectivity

with the MDLP API, integrates with

CryptoPro JCP library to support digital

signatures and enables polling MDLP API for

incoming messages.

Contact details: Ulrich Schild (Sales Director) ulrich.schild@3keys.com +49 175 8905008

HOW THE CONNECTOR IS VALIDATED? HOW TO MIGRATE FROM CONNECTOR TO

SAP STANDARD IF NEEDED?

The 3Keys MDLP Connector is developed in line with the best

practices of computerized system validation (CSV).

The 3Keys MDLP Connector provides parameters which can be

set active or inactive at any time without making changes to

the code. This allows customers to return to SAP standard and

deactivate the 3Keys Connector implementation without

programming.

RUSSIA MDLP REPORTING COCKPIT

Contact details: Ulrich Schild (Sales Director) ulrich.schild@3keys.com +49 175 8905008

AVAILABLE IN ENGLISH AND RUSSIAN LANGUAGE

MONITORING PROCESSING RESULTS IN MDLP

HANDLING MULTIPLE MDLP CONNECTIONS / ACCOUNTS WITH ONE CONNECTOR

Contact details: Ulrich Schild (Sales Director) ulrich.schild@3keys.com +49 175 8905008

Contact details: Ulrich Schild (Sales Director) ulrich.schild@3keys.com +49 175 8905008

DOWNLOAD INBOUND MESSAGES FROM MDLP

PROCESSING INBOUND MESSAGES WITH AIF

EXTENDING MISSING DATA FOR EVENT