Two-way sync
Changes in Sage X3 or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Keep Sage X3 and SAP Hana 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 Products, Sales Orders, Purchase Orders, Work Orders from Sage X3 into SAP Hana and keeps both sides consistent in real time. Whatever Sage X3 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 Sage X3 with its validations respected.
Worker and org records stay current in SAP Hana for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from SAP Hana back into Sage X3, keeping the ERP authoritative.
Records from Sage X3 live in SAP Hana as ordinary tables or collections, joinable with the rest of your data.
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.
| Sage X3 objects | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Sales Orders Order documents written from external channels and read for fulfillment status. | 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. | Sales Orders is specific to Sage X3 and Row store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents synced with supplier-facing systems. | Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. | Purchase Orders is specific to Sage X3 and Calculation views to SAP Hana — each maps to any object or custom field on the other side. | |
| Work Orders Production orders read by MES and scheduling integrations. | SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Work Orders is specific to Sage X3 and SQL views to SAP Hana — each maps to any object or custom field on the other side. | |
| Stock / Inventory by site On-hand and allocated quantities per site, synced to storefronts and WMS. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Stock / Inventory by site is specific to Sage X3 and Schemas to SAP Hana — each maps to any object or custom field on the other side. | |
| Bills of Material Product structures read for planning and costing. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Bills of Material is specific to Sage X3 and Sequences to SAP Hana — each maps to any object or custom field on the other side. | |
| GL Journals Financial entries replicated to warehouses for group reporting. | 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. | GL Journals is specific to Sage X3 and Triggers to SAP Hana — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Sage X3 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.
DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.
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 applied to Sage X3 as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Sage X3–SAP Hana connection.
Changes in Sage X3 or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Sage X3 or SAP Hana data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Sage X3 or SAP Hana record.
Track your Sage X3 ⇄ SAP Hana sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Sage X3 and SAP Hana.
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 Sage X3 and SAP Hana 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 Sage X3 and SAP Hana 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 Sage X3 and SAP Hana: authenticate both systems, choose the objects to sync (such as Sage X3's Sales Orders and Purchase Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Sage X3: Scheduled polling; no general webhook surface on the classic web services layer. On SAP Hana: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the SAP Hana side: Calculation views, SQL views, Schemas, Sequences, plus custom fields where SAP Hana exposes them. On the Sage X3 side: Products, Sales Orders, Purchase Orders, Work Orders. 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 Sage X3 and SAP Hana: Where Sage X3 is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in SAP Hana for provisioning, access, and reporting systems that read from the database.
Sage X3: SOAP and REST web services published from X3 business objects; direct SQL access to the underlying database on-prem. Authentication: Dedicated web-service user credentials (Basic auth) against configured connection pools. SAP Hana: 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. 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 542 integrations available for Sage X3 and SAP Hana.