Technology

Inside SAP, Not Outside.

DataXover runs as native ABAP inside your SAP system — not middleware calling from outside. Direct access to the data dictionary, change documents, and transactional data. No RFCs. No BAPIs. No bottlenecks.

Architecture

Push-based. Outbound only.

The ABAP transport pushes data to our SaaS coordination layer via HTTPS. The engine loads to your target database. No inbound firewall rules. No polling.

SAP System
ABAP Transport
SaaS
Coordination
Your Network
Engine
DB Loader
Your Database
Internal
Mode 1: Internal Integration

SAP data flows to your internal analytics infrastructure. Snowflake, Databricks, BigQuery — your data, your destination. Everything stays within your control.

Full data sovereignty
Lowest latency
Single-tenant control

Extraction

Profile-driven. No custom ABAP.

Define what you want — tables, fields, filters, schedule. The transport handles the rest. Add a new table in minutes, not months.

1
Define Profile
Select tables, choose fields, set filters. The UI reads directly from your SAP data dictionary — no guessing at field names.
2
Choose Delta Method
Per table, select change document tracking or key date field detection. The system remembers watermarks automatically.
3
Set Schedule
Run on demand, on interval, or triggered by SAP events. Initial load runs first, then CDC takes over.
4
Activate
Data flows. The engine handles type conversion, null handling, and target schema creation.
Profile Configuration
1// Example: Extract sales orders
2table: "VBAK"
3fields: [VBELN, ERDAT, KUNNR, NETWR]
4filter: ERDAT >= "20240101"
5delta: change_document
6schedule: every 15m
7
8// Example: Extract materials
9table: "MARA"
10fields: [MATNR, MTART, MATKL, ERSDA]
11delta: key_date(ERSDA, LAEDA)
12schedule: daily 02:00

Change Detection

Dual delta detection.

Two methods, per table. Use whichever fits the data. The system tracks watermarks and handles deduplication automatically.

Change Documents

SAP's native audit trail. When users modify business objects, SAP writes to CDHDR/CDPOS. We read those records to identify exactly which rows changed — and which fields.

CHANGEDOCUMENT_READ → TCDOB → CDPOS

Key Date Fields

Many SAP tables have created/changed date fields (ERDAT/AEDAT pattern). We track the high-water mark and pull only records modified since last run.

WHERE AEDAT >= @last_run OR ERDAT >= @last_run

Destinations

Your data, your destination.

Cloud data warehouses, on-premise databases, partner platforms. The engine handles connection, schema creation, and incremental loading.

Snowflake
PostgreSQL
SQL Server
MySQL
Oracle
Aurora (RDS)

Governance & Security

Enterprise-grade from the ground up.

Built for SAP customers who run the world's most sensitive business data. Security isn't an add-on — it's how we architected.

PII Masking

Pseudonymization and redaction enforced before data leaves SAP. Configure per field. Mask customer numbers, names, addresses — the sensitive fields stay protected.

Cross-Border Compliance

EU SCCs, GDPR, LGPD, UK IDTA, China PIPL — compliance certificates managed in-platform. Profiles blocked until valid certificates are in place. Auto-deactivation on expiry.

Outbound Only

All SAP communication is outbound. No inbound firewall rules required. Push-based architecture means SAP initiates every connection — nothing reaches in.

Refresh Detection

When PRD is copied to QAS, the system detects the mismatch immediately. Auto-lockdown prevents test systems from corrupting production data flows.

Full Audit Trail

Every consent, every extraction, every termination — logged with timestamp, user, and IP. Compliance teams get the paper trail they need.

Cascading Filters

Parent table linking ensures child records inherit header filters. Consent to "2024 sales orders" means only 2024 line items — not everything in VBAP.

See it in action.

We're open to technical deep-dives with qualified partners and acquirers.

Strategic partnerships