Two-way sync
Changes in SAP Hana or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep SAP Hana and Servicemax in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Engineers integrate with tools like Servicemax through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in SAP Hana.
Stacksync mirrors Work Orders, Work Details, Installed Products, Service Contracts from Servicemax into Calculation views, SQL views, Schemas, Sequences in SAP Hana and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Servicemax, so the tool and the database never disagree.
Write to the synced tables in SAP Hana and Stacksync propagates the change into Servicemax, replacing custom integration code.
Updates in Servicemax arrive as row changes in SAP Hana, so triggers, jobs, and services can respond in near real time.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
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 | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Work Orders SVMXC__Service_Order__c; the core field-service job record for install, repair, and maintenance; synced two-way with databases and pushed to ERPs at close. | Column store tables is specific to SAP Hana and Work Orders to Servicemax — 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. | Work Details SVMXC__Service_Order_Line__c; line items on a Work Order for labor, parts used, and expenses; read out for billing or written back with usage. | Row store tables is specific to SAP Hana and Work Details to Servicemax — 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. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Calculation views is specific to SAP Hana and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | SQL views is specific to SAP Hana and Service Contracts to Servicemax — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Schemas is specific to SAP Hana and Stock History to Servicemax — each maps to any object or custom field on the other side. | |
| Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | Sequences is specific to SAP Hana and Accounts to Servicemax — 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.
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 Servicemax through its API, with automatic retries and rate-limit backoff.
DetectionChanges in Servicemax are captured at the source via change data capture — no polling loop against its API. Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object.
DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SAP Hana–Servicemax connection.
Changes in SAP Hana or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever SAP Hana or Servicemax data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single SAP Hana or Servicemax record.
Track your SAP Hana ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between SAP Hana and Servicemax.
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 SAP Hana and Servicemax 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 SAP Hana and Servicemax 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 SAP Hana and Servicemax: authenticate both systems, choose the objects to sync (such as SAP Hana's Column store tables and Row store tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed SAP Hana and Servicemax connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom SAP Hana–Servicemax integration in-house.
Yes — Stacksync ships production-grade connectors for both SAP Hana and Servicemax. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection 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. On Servicemax: Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Servicemax side: Work Orders, Work Details, Installed Products, Service Contracts, plus custom fields where Servicemax exposes them. On the SAP Hana side: Calculation views, SQL views, Schemas, Sequences. 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.
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 545 integrations available for SAP Hana and Servicemax.