Eng De Esp Ru Pt

3KEYS Connector CIS is a solution provided by 3KEYS GmbH. The Connector CIS helps companies fulfill the reporting requirements to the CIS Federal Databases for Medications, Tobacco, Footwear, Tires, Light industry products, and upcoming regulations, such as Water, Dairy, and other goods.

The supported CIS reporting systems are: Kazakhstan – OMS/IS MPT, Uzbekistan – OMS/NIS MPT, and Russia – GIS MPT/MDLP.

The Connector is the combination of an ABAP SAP ATTP add-on and a Java-based middleware used to transfer digitally signed reporting messages from SAP Advanced Track & Trace (SAP ATTP) to the CIS systems using a secure connection. Moreover, it downloads incoming messages from CIS reporting systems and forwards them to SAP ATTP / ATT for further processing, and provides the monitoring for outbound and inbound messages. The Connector CIS is available both on-premises and as a cloud version. Learn how to get compliant with CIS regulations for Track and Trace by using the 3Keys Connector CIS – the proven solution!

White Paper

14 COMPANIES FROM DIFFERENT INDUSTRIES OPTED FOR 3KEYS CONNECTOR CIS AS A SOLUTION

WHY IS THE CONNECTOR NEEDED?
The current Country Package for SAP ATTP 3.0 allows to generate reports in XML/JSON formats and either automatically upload them to a file share or send them to Russian reporting systems after manual approval and locally-applied digital signature. The 3Keys Connector CIS enables bi-directional (inbound and outbound) integration between SAP ATTP and GIS MT, IS MDLP, IS MOTP, NIS MTP, and IS MPT systems in a fully automated mode without installing digital signature software on user machines.
HOW WILL THE CONNECTOR
BE USED?
The Connector CIS will be installed on SAP ATTP as a pre-delivered ABAP code implementing standard ATTP BADIs. The BADIs call Java components which are then used to communicate with the reporting systems. The BADIs call HTTPs endpoints of the Java component, which communicate with the reporting systems. Vice versa, the ABAP code implements a set of function modules that are then exposed as HTTPs endpoints from ATTP and are called from the Java component to push notifications and update report statuses. The Java component of the Connector provides secured connectivity with the IS MPT/ NIS MPT/ GIS MT APIs and integrates with CryptoPro JCP/ NC Layer / E-Imzo libraries to support digital signatures, and enables polling IS/ NIS/ GIS APIs for incoming messages.

The 3KEYS Connector CIS for SAP ATTP provides the following functionalities:

  • Implements fully featured communication & authentication layer, security features (document signature, certified based authentication) required by the regulator
  • Provide Digital signature functionality via CryptoPro JCP/ NC Layer / E-Imzo libraries or another certified cryptographic provider
  • Auto digital signature of crypto code ordering (non-pharma industries)
  • Automatically send reports from ATTP to IS/NIS/GIS APIs
  • Provide secured connection (TLS)
  • Poll reporting systems for processing status of sent outbound reports
  • Poll reporting systems for new inbound messages and downloads them into ATTP
  • ATTP transaction to monitor inbound and outbound messages
SECURITY
  • The solution is secured proven and GxP validated by an external independent professional company.
  • It has been proven that there is no possibility to bypass access control list and gain unauthorized access to API for the legitimate clients of the Connector Cloud.
  • The overall security level has been evaluated as high.
  • Additional client-side middleware (such as SAP PO) and security mechanisms (Gateways, Firewalls, Proxies) can be used.

THE CONNECTOR CIS FOR SAP ATTP IS AVAILABLE BOTH ON-PREMISES AND AS A CLOUD VERSION.

Data flow
simplified
3KEYS Connector CIS: SaaS on Yandex Cloud
HOW IS
THE СONNECTOR
VALIDATED?
The 3KEYS Connector CIS is developed in line with the best practices of computerized system validation (CSV).
HOW DO I MIGRATE
FROM CONNECTOR
TO SAP STANDARD IF NEEDED?
The 3KEYS Connector CIS 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 Connector implementation without programming.