Skip to content
Database ⇄ ERP

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

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

Give your engineers SAP S/4HANA's data in SAP Hana: 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 Customer / Supplier Roles, Production Orders, Business Partners, Sales Orders from SAP S/4HANA into SAP Hana and keeps both sides consistent in real time. Whatever SAP S/4HANA is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in SAP Hana sync back into SAP S/4HANA with its validations respected.

Common use cases

  • 01 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
  • 02 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.
  • 03 Replicate material master and pricing data to e-commerce and quoting tools.
  • 04 Feed S/4HANA financial and logistics documents into a data warehouse for reporting without custom ABAP extracts.

Common sync patterns

Read ERP records with a query

Records from SAP S/4HANA live in SAP Hana 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 S/4HANA interface, limits, and retries.

React to ERP changes

Updates in SAP S/4HANA arrive as row changes in SAP Hana, so jobs and triggers can respond as the business record changes.

What you can sync between SAP Hana 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 Hana objects SAP S/4HANA objects How this pairing syncs
Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. Products / Materials Material master data distributed to e-commerce, PIM, and CRM catalogs. Triggers is specific to SAP Hana and Products / Materials to SAP S/4HANA — each maps to any object or custom field on the other side.
System-versioned temporal tables Column store tables with a history table tracking each row's validity period; used to reconstruct update and delete history for change capture. Billing Documents (Invoices) Invoice data pushed to CRMs and payment or collections tools for finance visibility. System-versioned temporal tables is specific to SAP Hana and Billing Documents (Invoices) to SAP S/4HANA — each maps to any object or custom field on the other side.
System views (SYS schema) Catalog and monitoring views such as SYS.TABLES and TABLE_COLUMNS; read to discover schema and auto-generate field mappings for new tables. Deliveries Outbound delivery status synced to customer-facing systems for order tracking. System views (SYS schema) is specific to SAP Hana and Deliveries to SAP S/4HANA — each maps to any object or custom field on the other side.
Column store tables HANA's default table type, optimized for analytics; synced two-way as rows over the SQL interface with the primary key driving upserts and delete tracking. Journal Entries Financial postings read into warehouses and consolidation tools for reporting. Column store tables is specific to SAP Hana and Journal Entries to SAP S/4HANA — each maps to any object or custom field on the other side.
Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. Row store tables is specific to SAP Hana and Customer / Supplier Roles to SAP S/4HANA — each maps to any object or custom field on the other side.
Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. Production Orders Manufacturing order status surfaced in planning and operations tools. Calculation views is specific to SAP Hana and Production Orders to SAP S/4HANA — each maps to any object or custom field on the other side.

How changes propagate between SAP Hana 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 Hana SAP S/4HANA Sub-second propagation

DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.

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

SAP S/4HANA SAP Hana 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 SAP Hana as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with SAP Hana ⇄ SAP S/4HANA

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

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

Real-time

Two-way sync

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

Observability

Monitoring

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

How the SAP Hana and SAP S/4HANA connectors work

SAP Hana

Integration surface
SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
Authentication
Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
Change detection
Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
Capabilities
read · write · CDC
Rate limits
No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.

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

    Choose tables

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

SAP Hana 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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

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

Popular · 7 of 543
All SAP Hana integrations All SAP S/4HANA integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own