Two-way sync
Changes in BigQuery or SAP instantly reflect in both systems. No stale data, no manual imports.
Keep BigQuery and SAP in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
ERP data is some of the most asked-for data in the warehouse and some of the hardest to get: the record types are many, the APIs are strict, and extract jobs are brittle. Whether SAP carries financials, operations, workforce data, or all three, the analysis belongs in BigQuery next to everything else the company measures.
Stacksync syncs Billing Documents, GL Accounts and Journal Entries, Production Orders, Inventory / Stock from SAP 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 where that is useful.
Operational records become queryable tables in BigQuery, joinable with sales and finance data.
Combine SAP's records with data synced from other systems in BigQuery for consolidated views no single system can produce.
Classifications or reference values computed in BigQuery sync back onto the corresponding records in SAP.
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 objects | |
|---|---|---|
| Datasets Organizational container — you pick which dataset’s tables to sync. | Outbound Deliveries Shipment documents synced to WMS, carriers, and customer portals. | |
| Projects Connection scope: the service account grants access per project. | Billing Documents Invoices read for AR status and replicated for revenue reporting. | |
| Tables The syncable unit: only tables can be synced per the Stacksync docs. | GL Accounts and Journal Entries Financial postings replicated to warehouses for group finance analytics. | |
| Partitioned tables Synced like regular tables; partition columns map to target fields. | Production Orders Manufacturing orders exchanged with MES and scheduling systems. | |
| Clustered tables Supported; clustering is transparent to the sync. | Inventory / Stock Plant and storage-location quantities synced to storefronts and planning tools. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–SAP connection.
Changes in BigQuery or SAP instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery or SAP 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 record.
Track your BigQuery ⇄ SAP sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery and SAP.
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 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 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: authenticate both systems, choose the objects to sync (such as BigQuery's Datasets and Projects), map fields visually, and changes propagate both ways in milliseconds — no code required.
BigQuery: Views and materialized views are not supported — only tables. SAP: On ECC, writes go through BAPIs or IDocs so document flow and posting logic are enforced; direct writes to database tables are not a supported path. Stacksync's field mapping accounts for these differences between BigQuery and SAP 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 records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed BigQuery and SAP connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom BigQuery–SAP integration in-house.
Yes — Stacksync ships production-grade connectors for both BigQuery and SAP. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on BigQuery: 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. On SAP: Business events via SAP Event Mesh on S/4HANA; change pointers with IDocs or timestamp polling on ECC. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 386 integrations available for BigQuery and SAP.