Skip to content
Data warehouse ⇄ ERP

BigQuery to SAP S/4HANA integration — real-time, two-way sync

Keep BigQuery and SAP S/4HANA in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect BigQuery and SAP S/4HANA

Put SAP S/4HANA's records in BigQuery as live tables for reporting and analysis, without extract jobs, and write results back where SAP S/4HANA can use them.

Enterprises running SAP S/4HANA replicate it into BigQuery to open ERP data to analytics teams without direct access to the SAP system. Sales Orders, Billing Documents, and Business Partners sync into BigQuery Datasets, becoming the fulfillment and revenue source of truth for warehouse reporting.

Stacksync syncs Purchase Orders, Products / Materials, Billing Documents (Invoices), Deliveries from SAP S/4HANA into tables in BigQuery continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in BigQuery can be written back to fields in SAP S/4HANA where that is useful.

Common use cases

  • 01 Analyze Deliveries against Sales Orders in BigQuery to measure on-time fulfillment.
  • 02 Give analysts governed access to S/4HANA Billing Documents without SAP GUI access.
  • 03 Join Products / Materials with e-commerce and CRM data in a shared BigQuery Dataset.
  • 04 Activate modeled BigQuery tables by syncing computed attributes back into sales and marketing tools

Common sync patterns

Order-to-invoice pipeline

Sales Orders and Billing Documents (Invoices) sync into partitioned BigQuery Tables for revenue recognition analysis.

Supply chain visibility

Purchase Orders and Deliveries land in a BigQuery Dataset for lead-time and fulfillment reporting.

Master data warehouse

Business Partners and Products / Materials replicate to clustered BigQuery Tables as conformed dimensions.

What you can sync between BigQuery and SAP S/4HANA

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

BigQuery objects SAP S/4HANA objects How this pairing syncs
Partitioned tables Synced like regular tables; partition columns map to target fields. Products / Materials Material master data distributed to e-commerce, PIM, and CRM catalogs. Partitioned tables is specific to BigQuery and Products / Materials to SAP S/4HANA — each maps to any object or custom field on the other side.
Clustered tables Supported; clustering is transparent to the sync. Billing Documents (Invoices) Invoice data pushed to CRMs and payment or collections tools for finance visibility. Clustered tables is specific to BigQuery and Billing Documents (Invoices) to SAP S/4HANA — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. Deliveries Outbound delivery status synced to customer-facing systems for order tracking. Datasets is specific to BigQuery and Deliveries to SAP S/4HANA — each maps to any object or custom field on the other side.
Projects Connection scope: the service account grants access per project. Journal Entries Financial postings read into warehouses and consolidation tools for reporting. Projects is specific to BigQuery and Journal Entries to SAP S/4HANA — each maps to any object or custom field on the other side.
Tables The syncable unit: only tables can be synced per the Stacksync docs. Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. Tables is specific to BigQuery and Customer / Supplier Roles to SAP S/4HANA — each maps to any object or custom field on the other side.

How changes propagate between BigQuery and SAP S/4HANA

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

BigQuery SAP S/4HANA Sub-second propagation

DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").

DeliveryEach detected change is written to SAP S/4HANA through its API, with automatic retries and rate-limit backoff.

SAP S/4HANA BigQuery Interval-based propagation

DetectionStacksync polls SAP S/4HANA for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change timestamps exposed by the OData services.

DeliveryEach detected change is applied to BigQuery as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with BigQuery ⇄ SAP S/4HANA

Connect BigQuery and SAP S/4HANA for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–SAP S/4HANA connection.

Real-time

Two-way sync

Changes in BigQuery or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever BigQuery or SAP S/4HANA data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single BigQuery or SAP S/4HANA record.

Observability

Monitoring

Track your BigQuery ⇄ SAP S/4HANA sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between BigQuery and SAP S/4HANA.

How the BigQuery and SAP S/4HANA connectors work

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide

SAP S/4HANA

Integration surface
OData REST APIs (v2/v4), with SOAP, BAPI/RFC, and IDoc interfaces on on-premise editions
Authentication
OAuth 2.0 with communication arrangements on cloud editions; basic auth or certificate-based on-premise
Change detection
Polling on change timestamps exposed by the OData services; business events can be emitted through SAP's event infrastructure on cloud editions
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits, which vary by edition and communication arrangement
How it works

How to connect BigQuery to SAP S/4HANA — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate BigQuery and SAP S/4HANA with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    BigQuery connected
    SAP S/4HANA connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the BigQuery and SAP S/4HANA objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · BigQuery ⇄ SAP S/4HANA
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    BigQuery SAP S/4HANA
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

BigQuery and SAP S/4HANA integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 545 integrations available for BigQuery and SAP S/4HANA.

Popular · 7 of 545
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.