Skip to content
ERP ⇄ Analytics

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

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

Put SAP S/4HANA's records into Treasuredata as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Treasuredata computes back where SAP S/4HANA can use them.

ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether SAP S/4HANA carries financials, operations, workforce data, or all three, those numbers belong in Treasuredata, next to the product, behavioral, and web data the team already measures.

Stacksync syncs Business Partners, Sales Orders, Purchase Orders, Products / Materials from SAP S/4HANA into Treasuredata continuously, handling API limits and schema drift as it goes, so each record type arrives as Query Jobs, Databases, Tables, Master (Parent) Segments ready to report on. The connection is bi-directional, so segments, scores, and metrics computed in Treasuredata can be written back to fields in SAP S/4HANA where that is useful.

Common use cases

  • 01 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
  • 02 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
  • 03 Surface invoice and payment status from S/4HANA inside the CRM so account teams see open balances.
  • 04 Replicate material master and pricing data to e-commerce and quoting tools.

Common sync patterns

Where SAP S/4HANA holds the books: revenue and finance dashboards from live data

Financial records from SAP S/4HANA land in Treasuredata as they change, so revenue, margin, and spend dashboards read current figures rather than last night's export.

Where SAP S/4HANA runs order-to-cash: customer and account analytics

Orders, invoices, and account records from SAP S/4HANA join the behavioral and usage data Treasuredata already tracks, so customer analysis spans activity and dollars in one view.

Where SAP S/4HANA runs operations: inventory and fulfillment metrics

Operational records from SAP S/4HANA become measurable in Treasuredata, joinable with the rest of what the company tracks for supply and fulfillment reporting.

What you can sync between SAP S/4HANA and Treasuredata

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 S/4HANA objects Treasuredata objects How this pairing syncs
Business Partners Unified customer and supplier master records, the anchor entity for CRM-to-ERP account syncs. Master (Parent) Segments Unified customer profiles assembled from multiple source tables in Audience Studio; read out to push enriched attributes onto CRM or warehouse records. Business Partners is specific to SAP S/4HANA and Master (Parent) Segments to Treasuredata — each maps to any object or custom field on the other side.
Sales Orders Order headers and line items synced to CRMs and fulfillment systems as they are created or amended. Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. Sales Orders is specific to SAP S/4HANA and Segments to Treasuredata — each maps to any object or custom field on the other side.
Purchase Orders Procurement documents shared with supplier portals and spend-management tools. Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. Purchase Orders is specific to SAP S/4HANA and Journeys to Treasuredata — each maps to any object or custom field on the other side.
Products / Materials Material master data distributed to e-commerce, PIM, and CRM catalogs. Predictive Segments AI/ML-scored segments; propensity scores read out and written onto customer records in a CRM or database for prioritization. Products / Materials is specific to SAP S/4HANA and Predictive Segments to Treasuredata — each maps to any object or custom field on the other side.
Billing Documents (Invoices) Invoice data pushed to CRMs and payment or collections tools for finance visibility. Scheduled Queries Cron-scheduled Presto/Trino (or Hive) jobs that materialize results into result tables; Stacksync reads those materialized tables downstream. Billing Documents (Invoices) is specific to SAP S/4HANA and Scheduled Queries to Treasuredata — each maps to any object or custom field on the other side.
Deliveries Outbound delivery status synced to customer-facing systems for order tracking. Query Jobs Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems. Deliveries is specific to SAP S/4HANA and Query Jobs to Treasuredata — each maps to any object or custom field on the other side.

How changes propagate between SAP S/4HANA and Treasuredata

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

Treasuredata SAP S/4HANA Interval-based propagation

DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.

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

Rate-limit considerations

  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
  • Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with SAP S/4HANA ⇄ Treasuredata

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

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

Real-time

Two-way sync

Changes in SAP S/4HANA or Treasuredata instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever SAP S/4HANA or Treasuredata 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 S/4HANA or Treasuredata record.

Observability

Monitoring

Track your SAP S/4HANA ⇄ Treasuredata sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between SAP S/4HANA and Treasuredata.

How the SAP S/4HANA and Treasuredata connectors work

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

Treasuredata

Integration surface
TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
Authentication
API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
Change detection
Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
Capabilities
read · write
Rate limits
TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
How it works

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

    Choose tables

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

SAP S/4HANA and Treasuredata 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
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 383 integrations available for SAP S/4HANA and Treasuredata.

Popular · 8 of 383
All SAP S/4HANA integrations All Treasuredata 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