Two-way sync
Changes in Citus or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.
Keep Citus 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.
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 Sales Orders, Purchase Orders, Products / Materials, Billing Documents (Invoices) from SAP S/4HANA into Citus 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 Citus sync back into SAP S/4HANA with its validations respected.
Updates in SAP S/4HANA arrive as row changes in Citus, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in Citus for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from Citus back into SAP S/4HANA, keeping the ERP authoritative.
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.
| Citus objects | SAP S/4HANA objects | |
|---|---|---|
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Business Partners Unified customer and supplier master records, the anchor entity for CRM-to-ERP account syncs. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Sales Orders Order headers and line items synced to CRMs and fulfillment systems as they are created or amended. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Purchase Orders Procurement documents shared with supplier portals and spend-management tools. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Products / Materials Material master data distributed to e-commerce, PIM, and CRM catalogs. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Billing Documents (Invoices) Invoice data pushed to CRMs and payment or collections tools for finance visibility. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Deliveries Outbound delivery status synced to customer-facing systems for order tracking. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–SAP S/4HANA connection.
Changes in Citus or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus or SAP S/4HANA data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Citus or SAP S/4HANA record.
Track your Citus ⇄ SAP S/4HANA sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus and SAP S/4HANA.
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 Citus 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.
Pick the Citus 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.
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 Citus and SAP S/4HANA: authenticate both systems, choose the objects to sync (such as Citus's Distributed tables and Reference tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. On SAP S/4HANA: Polling on change timestamps exposed by the OData services; business events can be emitted through SAP's event infrastructure on cloud editions. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Citus side: Views, Sequences, Distributed tables, Reference tables, plus custom fields where Citus exposes them. On the SAP S/4HANA side: Sales Orders, Purchase Orders, Products / Materials, Billing Documents (Invoices). Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Citus and SAP S/4HANA: React to ERP changes; Where SAP S/4HANA is the HR system of record: people data for internal systems; Controlled write-back. Updates in SAP S/4HANA arrive as row changes in Citus, so jobs and triggers can respond as the business record changes.
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). SAP S/4HANA: 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. Stacksync manages authentication, retries, and rate limits on both sides.
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 Citus and SAP S/4HANA.