Skip to content
ERP

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

Keep SAP 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 SAP and SAP S/4HANA

Two ERPs, one set of facts: Stacksync keeps SAP and SAP S/4HANA consistent in real time, whether they split the business or one is replacing the other.

Companies run two ERPs for structural reasons: a two-tier setup with subsidiaries on lighter systems, an acquisition that brought its own stack, a split by function or region, or a migration that will take quarters. In all of these, some of the same organizations, people, and transactions exist in both systems, and keeping them aligned by hand is a standing tax on the back office.

Stacksync syncs Outbound Deliveries, Billing Documents, GL Accounts and Journal Entries, Production Orders in SAP with Sales Orders, Purchase Orders, Products / Materials, Billing Documents (Invoices) in SAP S/4HANA bi-directionally and in real time, with field-level mapping across the two data models and conflict rules you define. A record changed in either system is reflected in the other within seconds, not at the next interface run.

Common use cases

  • 01 Keep MES and WMS systems aligned with production orders and goods movements.
  • 02 Expose sales order and delivery status to customer portals through a synced Postgres database instead of direct SAP access.
  • 03 Feed S/4HANA financial and logistics documents into a data warehouse for reporting without custom ABAP extracts.
  • 04 Keep supplier records aligned between S/4HANA procurement and third-party spend platforms.

Common sync patterns

Two-tier roll-up

Where subsidiaries run one system and headquarters runs the other, shared records and transactions flow up continuously, so consolidation starts from live data.

Migration in parallel

When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.

Shared master data

Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.

What you can sync between SAP 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.

SAP objects SAP S/4HANA objects How this pairing syncs
Business Partners The unified customer and supplier master in S/4HANA, the anchor object for CRM and procurement syncs. Business Partners Unified customer and supplier master records, the anchor entity for CRM-to-ERP account syncs. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Sales Orders Order documents written from external channels and read for status and fulfillment. Sales Orders Order headers and line items synced to CRMs and fulfillment systems as they are created or amended. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Purchase Orders Procurement documents synced with supplier portals and spend tools. Purchase Orders Procurement documents shared with supplier portals and spend-management tools. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Production Orders Manufacturing orders exchanged with MES and scheduling systems. Production Orders Manufacturing order status surfaced in planning and operations tools. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Inventory / Stock Plant and storage-location quantities synced to storefronts and planning tools. Deliveries Outbound delivery status synced to customer-facing systems for order tracking. Inventory / Stock is specific to SAP and Deliveries to SAP S/4HANA — each maps to any object or custom field on the other side.
Cost Centers Controlling masters read for mapping costs in finance integrations. Journal Entries Financial postings read into warehouses and consolidation tools for reporting. Cost Centers is specific to SAP and Journal Entries to SAP S/4HANA — each maps to any object or custom field on the other side.

How changes propagate between SAP 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.

SAP SAP S/4HANA 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 written to SAP S/4HANA through its API, with automatic retries and rate-limit backoff.

SAP S/4HANA SAP 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 written to SAP through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • SAP: Throttling is configured at the gateway and tenant level rather than as a single published rate limit.
  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with SAP ⇄ SAP S/4HANA

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

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

Real-time

Two-way sync

Changes in SAP 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 SAP 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 SAP or SAP S/4HANA record.

Observability

Monitoring

Track your SAP ⇄ 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 SAP and SAP S/4HANA.

How the SAP and SAP S/4HANA connectors work

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

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 SAP 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 SAP 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
    SAP connected
    SAP S/4HANA connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the SAP 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 · SAP ⇄ 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
    SAP SAP S/4HANA
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

SAP 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:

Coworkers laughing in front of a laptop in a casual office setting

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