DatriseAI-first ETL

SAP Google BigQuery

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

How Datrise loads SAP into Google BigQuery

Datrise syncs SAP's finance, procurement, operations, and master-data entities into Google BigQuery as a partitioned table per source entity. Flexible or custom fields land in JSON or nested/repeated (STRUCT) columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.

Sync is incremental: Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target, so re-runs update only what changed. Partition by ingestion or event date and cluster by entity id to keep scanned bytes low. BigQuery bills by bytes scanned, so Datrise partitions and clusters every table to keep query costs predictable.

Ideal for Google-stack analytics and ML on serverless infrastructure.

Endpoints

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

Google BigQuery: Serverless analytics warehouse on GCP.

How SAP entities map to Google BigQuery

SAP entityGoogle BigQuery objectNotes
financesap_financeid PK · custom fields → JSON or nested/repeated (STRUCT) 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 Google BigQuery?

Flexible values are stored as JSON or nested/repeated (STRUCT) columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Google BigQuery types.

How does the SAP to Google BigQuery sync stay up to date?

It runs incrementally — Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target.

Related pipelines

Early access

Connect SAP to Google BigQuery 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.