Two-way sync
Changes in BigQuery or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.
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.
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.
Sales Orders and Billing Documents (Invoices) sync into partitioned BigQuery Tables for revenue recognition analysis.
Purchase Orders and Deliveries land in a BigQuery Dataset for lead-time and fulfillment reporting.
Business Partners and Products / Materials replicate to clustered BigQuery Tables as conformed dimensions.
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. |
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.
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.
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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–SAP S/4HANA connection.
Changes in BigQuery or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery or SAP S/4HANA data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single BigQuery or SAP S/4HANA record.
Track your BigQuery ⇄ SAP S/4HANA sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery and SAP S/4HANA.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between BigQuery and SAP S/4HANA: authenticate both systems, choose the objects to sync (such as BigQuery's Partitioned tables and Clustered tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for BigQuery and SAP S/4HANA: Order-to-invoice pipeline; Supply chain visibility; Master data warehouse. Sales Orders and Billing Documents (Invoices) sync into partitioned BigQuery Tables for revenue recognition analysis.
BigQuery: 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. SAP S/4HANA: 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. Stacksync manages authentication, retries, and rate limits on both sides.
BigQuery: The Storage Write API supports high-throughput streaming ingestion, which suits continuous sync loads better than legacy streaming inserts. SAP S/4HANA: Cloud and on-premise editions expose different API allowlists, so field availability depends on the edition. Stacksync's field mapping accounts for these differences between BigQuery and SAP S/4HANA without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means BigQuery and SAP S/4HANA records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 545 integrations available for BigQuery and SAP S/4HANA.