DatriseAI-first ETL

SAP ClickHouse

AI-first ETL from SAP into ClickHouse. Governed entities, incremental sync, typed landing tables.

How Datrise loads SAP into ClickHouse

Datrise syncs SAP's finance, procurement, operations, and master-data entities into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

SAP: ERP source for finance, operations, and procurement entities.

ClickHouse: Columnar OLAP engine for fast aggregations.

How SAP entities map to ClickHouse

SAP entityClickHouse objectNotes
financesap_financeid PK · custom fields → JSON or Map columns
procurementsap_procurementid PK · linked to sap_finance
operationssap_operationsid PK · linked to sap_finance
master-data entitiessap_master_data_entitiesid PK · linked to sap_finance

FAQ

How does Datrise handle SAP's custom fields in ClickHouse?

Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.

How does the SAP to ClickHouse sync stay up to date?

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

Connect SAP to ClickHouse the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.