Source connector

SAP connector

SAP integration for databases, warehouses and BI tools

ERP source for finance, operations, and procurement entities. Datrise captures SAP entities such as finance, procurement, operations, and master-data entities, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The SAP S/4HANA Cloud OData APIs (OData v2 and v4, published on SAP Business Accelerator Hub) authenticates with OAuth 2.0, HTTP Basic, incremental runs key on Change-tracking field exposed per API (commonly `LastChangeDateTime` or `ChangedOn`); the exact field name is service-specific, not a platform-wide standard.

Of the 4 objects, 4 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `sap_finance`) with a schema derived from the SAP API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the SAP pipeline page, and join the waitlist to get the SAP connector (ERP) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What SAP data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
finance	sap_finance	Upsert by primary key, incremental on updated-at
procurement	sap_procurement	Upsert by primary key, incremental on updated-at
operations	sap_operations	Upsert by primary key, incremental on updated-at
master-data entities	sap_master_data_entities	Upsert by primary key, incremental on updated-at

SAP API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	SAP S/4HANA Cloud OData APIs (OData v2 and v4, published on SAP Business Accelerator Hub)
Authentication	OAuth 2.0, HTTP Basic — APIs listed on SAP Business Accelerator Hub support OAuth 2.0 Client Credentials for system-to-system access; on-prem/private-cloud OData services also commonly accept HTTP Basic Auth with a dedicated communication user.
Pagination	offset — OData v2 services page with `$top`/`$skip`; OData v4 services can additionally return server-driven paging via an `@odata.nextLink` in the response body instead of client-supplied skip values.
Rate limit	Not published
Incremental cursor	Change-tracking field exposed per API (commonly `LastChangeDateTime` or `ChangedOn`); the exact field name is service-specific, not a platform-wide standard — There is no single delta field across all S/4HANA OData APIs; each published API package documents its own change-tracking field, or lacks one entirely and requires a full reload.
Webhooks	Yes — SAP Event Mesh (event-driven integration; S/4HANA Cloud publishes business events that Event Mesh can push to an HTTPS webhook endpoint)
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating SAP

SAP does not publish one universal OData rate limit; per-API guidance (e.g. the Journal Entry Post API's own performance notes) instead recommends caps like 15 parallel synchronous calls, and getting a hard number for your tenant requires opening an SAP incident.
There is no single `LastChangeDateTime`-style field shared across all S/4HANA OData APIs; the change-tracking field name, and even its presence, must be checked per API package on the Business Accelerator Hub.
Outbound change notifications require provisioning a separate `SAP Event Mesh` service instance and an HTTPS-reachable endpoint (e.g. a Cloud Integration `iFlow`) — S/4HANA Cloud itself has no built-in webhook configuration screen.
OData v2 and OData v4 packages for the same business object (e.g. Business Partner) can expose different field sets and paging behavior, so a v2-built extractor cannot be pointed at the v4 endpoint without remapping.

Compare this against every other documented API

Popular destinations for SAP

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

SAP connector FAQ

What SAP data does the connector extract?: 4 objects: finance, procurement, operations and master-data entities. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the SAP integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load SAP data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each SAP → destination pair has its own page with the object-to-table mapping.

Related ERP sources

Other sources in the same category, each with its own connector page.

Early access

Launch your SAP pipeline with guided onboarding

Join the waitlist to get priority access for SAP integrations with guided setup, schema-aware mapping, and production-grade incremental sync.