---
title: Governed SAP Data Extraction with zapliance
description: Architectural separation between data extraction and processing, ensuring full customer control and transparency.
---

[Skip to content](https://knowledge.zapliance.com/sap-governance-data-extraction-with-zapliance#main-content)

- [English](https://knowledge.zapliance.com/sap-governance-data-extraction-with-zapliance)
- [Deutsch](https://knowledge.zapliance.com/de/sap-governance-data-extraction-with-zapliance)

English

Show submenu for translations

[![zapliance logo light bg](https://knowledge.zapliance.com/hubfs/zapliance%20logo%20light%20bg.svg)](https://knowledge.zapliance.com/migration)

Open main navigation

Close main navigation

- - [English](https://knowledge.zapliance.com/sap-governance-data-extraction-with-zapliance)
    - [Deutsch](https://knowledge.zapliance.com/de/sap-governance-data-extraction-with-zapliance)

  English
  
  Show submenu for translations
- [Contact us](https://zapliance.com/support/)

[Contact us](https://zapliance.com/support/)

 Hi. How can we help?

- There are no suggestions because the search field is empty.

1. [Knowledge Base](https://knowledge.zapliance.com/)
2. [Governance Onboarding](https://knowledge.zapliance.com/governance-onboarding)
3. [General Governance Information](https://knowledge.zapliance.com/governance-onboarding#general-governance-information)

# Governed SAP Data Extraction with zapliance

### **1. zapliance Solution Architecture**

The zapliance operating model is built on a clear technical separation of two layers:

1. Data extraction
2. Data processing

Data extraction uses RFC to create copies of customer-approved SAP data, stored in a zapAnalytics project database. All subsequent processing performed by agents, including AI-supported analysis and result generation, operates exclusively on these data copies and does not interact with SAP production systems.

**Key takeaway:** RFC talks to SAP. Agents talk to the extracted dataset.

---

### **2\. Role of SAP RFC**

Remote Function Call (RFC) is a long-established SAP communication architecture and the standard mechanism used by zapAnalytics to communicate with SAP systems.

Within the zapliance architecture, RFC is used exclusively for **deterministic extraction** of customer-approved SAP data.

Every extraction is initiated by an authorized customer user, either manually or through a customer-configured schedule.

#### SAP Reference

SAP documents RFC-based extraction for SAP Signavio Process Intelligence, including RFC\_READ\_TABLE as well as controls for table selection, filtering, partitioning, scheduling, monitoring, and security.

The official SAP documentation can be found here: 

- [SAP Help: Supported Systems and RFC Usage](https://help.sap.com/docs/signavio-process-intelligence/onboarding-and-data-integration-guide/supported-systems-and-rfc-usage)
- [/[:dynamic-slug]/%20https://help.sap.com/docs/signavio-process-intelligence/onboarding-and-data-integration-guide/supported-systems-and-rfc-usage](/[:dynamic-slug]/%20https://help.sap.com/docs/signavio-process-intelligence/onboarding-and-data-integration-guide/supported-systems-and-rfc-usage)[SAP Help: Connector - SAP ERP (RFC)](https://help.sap.com/docs/signavio-process-intelligence/onboarding-and-data-integration-guide/connector-sap-erp-rfc )

---

### **3\. Separation Between Extraction and Processing**

#### **Layer 1: Data Extraction**

During extraction:

- zapAnalytics connects to SAP through RFC
- Only standard RFC modules are used
- Customer-approved SAP data is extracted
- Copies of the extracted data are stored in the project database

The extraction process is deterministic and governed by predefined rules. Agents are not involved in deciding what data is extracted.

The customer defines:

- Which SAP systems are accessed
- Which data is extracted
- Which SAP user is configured for the extraction
- Which permissions are granted
- When extraction is executed

 

#### **Layer 2: Data Processing**

After extraction has been completed:

- Processing (performed by agents) operates on the data copies stored in the project database
- RFC is no longer used, and an SAP connection is no longer required

Agents **do not** autonomously:

- Establish SAP connections
- Initiate data extractions
- Execute additional RFC requests
- Expand the approved extraction scope

Their processing work is limited to the data that has already been extracted through the approved extraction process (layer 1).

---

### **4\. Governance and Control Principles**

**1. No autonomous agent access to SAP**

The extraction scope is defined by the customer, and every data extraction is initiated by the customer. Agents do not autonomously interact with SAP systems, perform self-initiated data extractions or expand the extraction scope.

Once extraction has been completed, agents work exclusively with copies of the extracted data stored in the project database.

**2. Use of standard SAP technology**

SAP connectivity uses RFC, a long-established SAP standard interface.

No proprietary or undocumented SAP access mechanisms are required.

**3. Deterministic data extraction**

The extraction process follows predefined rules.

The customer defines and controls:

- Which data is extracted
- When it is extracted
- Which RFC user is used
- Which RFC permissions are involved

**4. Governance remains under customer control**

The customer authorizes and controls:

- The creation of the RFC user
- The RFC permissions
- The SAP connection
- The data scope
- The execution of each extraction

---

### **5\. Wilma**

zapAgent Wilma is the user-driven conversational AI member of your governance team.

Wilma operates as a chat agent within LibreChat and is **part of the data processing layer** (layer 2). She is **not involved** **in data extraction** and has **no SAP connection**.

Wilma works exclusively with copies of the extracted data already existing in the project database.

---

### **Summary**

zapAnalytics uses standard SAP RFC connectivity for governed and deterministic data extraction. During subsequent processing, including AI-supported analysis, agents do not access SAP.

Instead, they operate exclusively within the processing layer and work on data copies stored in the project database.

This architectural separation ensures that processing and AI functionality remain isolated from SAP systems.

- [Agentic Teams](https://knowledge.zapliance.com/agentic-teams)
- [Product Descriptions](https://knowledge.zapliance.com/product-descriptions#main-content)

    - [Platforms](https://knowledge.zapliance.com/product-descriptions#platforms)
    - [Agentic Teams](https://knowledge.zapliance.com/product-descriptions#agentic-teams)
    - [Agentic Team Solutions](https://knowledge.zapliance.com/product-descriptions#agentic-team-solutions)
    - [Solution Bundles](https://knowledge.zapliance.com/product-descriptions#solution-bundles)
    - [Customer Success](https://knowledge.zapliance.com/product-descriptions#customer-success)
- [Technical Onboarding](https://knowledge.zapliance.com/technical-onboarding#main-content)

    - [zapHome](https://knowledge.zapliance.com/technical-onboarding#zaphome)
    - [Virtual Machine/Server](https://knowledge.zapliance.com/technical-onboarding#virtual-machine-server)
    - [Docker](https://knowledge.zapliance.com/technical-onboarding#docker)
    - [zapAnalytics Setup Guides](https://knowledge.zapliance.com/technical-onboarding#zapanalytics-setup-guides)
    - [SAP Setup Guides](https://knowledge.zapliance.com/technical-onboarding#sap-setup-guides)
    - [LibreChat Setup Guide](https://knowledge.zapliance.com/technical-onboarding#librechat-setup-guide)
    - [Microsoft Services Setup Guides](https://knowledge.zapliance.com/technical-onboarding#microsoft-services-setup-guides)
    - [Former Setups](https://knowledge.zapliance.com/technical-onboarding#former-setups)
- [Functional Onboarding](https://knowledge.zapliance.com/functional-onboarding#main-content)

    - [Project Workflows](https://knowledge.zapliance.com/functional-onboarding#project-workflows)
    - [zapAnalytics User Guides](https://knowledge.zapliance.com/functional-onboarding#zapanalytics-user-guides)
    - [Wilma User Guides](https://knowledge.zapliance.com/functional-onboarding#wilma-user-guides)
    - [SAP User Guides](https://knowledge.zapliance.com/functional-onboarding#sap-user-guides)
    - [Microsoft Services User Guides](https://knowledge.zapliance.com/functional-onboarding#microsoft-services-user-guides)
- [Governance Onboarding](https://knowledge.zapliance.com/governance-onboarding#main-content)

    - [General Governance Information](https://knowledge.zapliance.com/governance-onboarding#general-governance-information)
    - [Digital Audit Preparation (DAP)](https://knowledge.zapliance.com/governance-onboarding#digital-audit-preparation-dap)
    - [Cash Recovery AI (CRAI)](https://knowledge.zapliance.com/governance-onboarding#cash-recovery-ai-crai)

[![Favikon Color-1](https://knowledge.zapliance.com/hs-fs/hubfs/Favikon%20Color-1.png?width=30&height=30&name=Favikon%20Color-1.png "Favikon Color-1")](https://zapliance.com/)

Knowledge Base

Copyright © 2026, zapliance GmbH