Skip to content
Database ⇄ ERP

Google Cloud Spanner to SAP integration — real-time, two-way sync

Keep Google Cloud Spanner 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.

  • 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 Google Cloud Spanner and SAP

Give your engineers SAP's data in Google Cloud Spanner: read it with normal queries, write back through the sync, and skip the ERP API entirely.

ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.

Stacksync mirrors Materials (Products), Sales Orders, Purchase Orders, Outbound Deliveries from SAP into Google Cloud Spanner and keeps both sides consistent in real time. Whatever SAP is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Google Cloud Spanner sync back into SAP with its validations respected.

Common use cases

  • 01 Run a two-way sync between Spanner and a SaaS tool so edits made by ops teams land back in the application database.
  • 02 Consolidate data from a globally distributed Spanner deployment into regional business systems.
  • 03 Replicate journal entries and billing documents to a warehouse for finance analytics without loading the ERP.
  • 04 Keep MES and WMS systems aligned with production orders and goods movements.

Common sync patterns

Read ERP records with a query

Records from SAP live in Google Cloud Spanner as ordinary tables or collections, joinable with the rest of your data.

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the SAP interface, limits, and retries.

React to ERP changes

Updates in SAP arrive as row changes in Google Cloud Spanner, so jobs and triggers can respond as the business record changes.

What you can sync between Google Cloud Spanner and 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.

Google Cloud Spanner objects SAP objects How this pairing syncs
Databases Top-level containers that scope schema and sync configuration. Materials (Products) Item master with plant and sales views, synced to commerce, PLM, and CRM systems. Databases is specific to Google Cloud Spanner and Materials (Products) to SAP — each maps to any object or custom field on the other side.
Tables Relational tables mapped one-to-one to sync targets. Sales Orders Order documents written from external channels and read for status and fulfillment. Tables is specific to Google Cloud Spanner and Sales Orders to SAP — each maps to any object or custom field on the other side.
Rows The unit of read and write in each sync cycle, keyed by primary key. Purchase Orders Procurement documents synced with supplier portals and spend tools. Rows is specific to Google Cloud Spanner and Purchase Orders to SAP — each maps to any object or custom field on the other side.
Interleaved tables Child rows physically co-located with parents; synced as related records. Outbound Deliveries Shipment documents synced to WMS, carriers, and customer portals. Interleaved tables is specific to Google Cloud Spanner and Outbound Deliveries to SAP — each maps to any object or custom field on the other side.
Secondary indexes Used to make incremental read queries efficient on non-key columns. Billing Documents Invoices read for AR status and replicated for revenue reporting. Secondary indexes is specific to Google Cloud Spanner and Billing Documents to SAP — each maps to any object or custom field on the other side.
Change streams Capture inserts, updates, and deletes for log-style change data capture. GL Accounts and Journal Entries Financial postings replicated to warehouses for group finance analytics. Change streams is specific to Google Cloud Spanner and GL Accounts and Journal Entries to SAP — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Spanner and SAP

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.

Google Cloud Spanner SAP Sub-second propagation

DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.

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

SAP Google Cloud Spanner Sub-second propagation

DetectionSAP notifies Stacksync of record changes through webhook events. Business events via SAP Event Mesh on S/4HANA.

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

Rate-limit considerations

  • Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
  • SAP: Throttling is configured at the gateway and tenant level rather than as a single published rate limit.
What ships with Google Cloud Spanner ⇄ SAP

Connect Google Cloud Spanner and SAP for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–SAP connection.

Real-time

Two-way sync

Changes in Google Cloud Spanner or SAP instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Google Cloud Spanner or SAP 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 Google Cloud Spanner or SAP record.

Observability

Monitoring

Track your Google Cloud Spanner ⇄ SAP sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and SAP.

How the Google Cloud Spanner and SAP connectors work

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.

SAP

Integration surface
OData (v2/v4) APIs on S/4HANA; BAPI/RFC and IDoc on ECC and on-prem systems; SOAP services
Authentication
OAuth 2.0 or basic auth via communication arrangements on cloud editions; SAP user credentials for RFC on-prem
Change detection
Business events via SAP Event Mesh on S/4HANA; change pointers with IDocs or timestamp polling on ECC
Capabilities
read · write · webhooks
Rate limits
Throttling is configured at the gateway and tenant level rather than as a single published rate limit
How it works

How to connect Google Cloud Spanner to SAP — 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 Google Cloud Spanner 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Google Cloud Spanner connected
    SAP connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Google Cloud Spanner 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Google Cloud Spanner ⇄ SAP
    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
    Google Cloud Spanner SAP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Google Cloud Spanner and SAP 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 451 integrations available for Google Cloud Spanner and SAP.

Popular · 4 of 451
Coworkers laughing in front of a laptop in a casual office setting

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