Technical documentation
Updated 11 hours ago
by
Stephanie Krenz
Connections to the SAP system
General Requirements
In order for dab Nexus Loom to establish a connection to the SAP system, the RFC function module must be installed in the desired SAP system. Find more information about the RFC module here.
SAP Router
Customer Environment - provided by customer
The following components exist on the customer side:
- Server with SAP router
- SAP system (possibly on another server)
dab Environment
The following components exist on the dab side:
- dab Nexus Loom in the Azure environment
How it works
With the SAP router connection, dab Nexus Loom connects to the SAP router via a port (32xx). The router forwards the connection to the SAP system. This connection gives dab Nexus Loom access to the data in the SAP system so that the customer can use the data in the dab Nexus Loom environment.
Gateway
Customer Environment - provided by customer
- dab Gateway on your Gateway server (Installation Guide)
- SAP system
dab Environment
- dab Nexus Loom in the Azure environment
- Download Container
- Gateway Center
How it works
The Download Container opens a port connection to the Gateway Center. The Gateway Center then opens a connection through an encrypted tunnel to the dab Gateway on the customer side. The Gateway opens a port connection to the customer's SAP system before the dab Gateway sends the port back to the Gateway Center. The SAP data is then made available to the dab Nexus Loom via the tunnel.
Data Security
Where is customer data saved?
The data is stored in a data center in the zone Germany West Central and is located in the Azure tenant of dab GmbH. Data is stored here with strict separation between customers. You can find more information about the zone here.
If you want to see what a data center looks like, you can take a virtual tour here.
Compliance in the Germany West Central zone
Here is a list of all the compliance offerings from Microsoft. The compliance offerings described below are also described in detail there.
Regional Compliance | EU-US Privacy Shield, TISAX, IT-Grundschutz, C5, EU Model Clauses, GDPR, ENISA IAF, EN 301 549 |
Industrial Compliance | EBA, TruSight, Shared Assessments, PCI DSS, GxP, CDSA |
Global Compliance | SOC 3, SOC 2, SOC 1, ISO 9001, ISO 27701, ISO 27018, ISO 27017, ISO 27001, ISO 22301, ISO 20000 CSA STAR Self-Assessment, CSA STAR Certification, CSA STAR Attestation, CIS Benchmark |
Duration of Data Storage
It is necessary to make a distinction between the types of data:
- SAP Data: Data needed for the reports in dab Nexus Loom, for example, from your SAP tables
- User Data: Data required for your organization in dab Nexus Loom
SAP data is stored in the dab GmbH tenant as long as it is used in an active report in your organization in the dab Nexus Loom interface. If a report is deleted, the associated data (including pipeline, warehouse, etc.) is immediately deleted and cannot be restored.
User data is stored in the dab GmbH tenant as long as the user exists in your organization in dab Nexus Loom. If the user is deleted from your organization, the associated data is immediately deleted and cannot be restored.
Deletion of all customer data in case of cancellation of the dab Nexus Loom.
If you cancel your subscription to dab Nexus Loom, your organization in dab Nexus Loom and all related SAP data and user data will be deleted immediately. This process is irreversible!
Use customer data to train AI
If you use AI components such as AI Double Payment Analysis, the detection is trained with data from your SAP system to improve detection.
Your AI component will only be trained with data from your SAP system. Your data will not be used to train other customers' AI components, nor will their data be used to train your AI component!
