Real-time
Two-way sync
Changes in Reltio or SAP instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ ERP
Reltio to SAP integration — real-time, two-way sync
Keep Reltio and SAP 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 Reltio and SAP
Give your engineers SAP's data in Reltio: 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 Outbound Deliveries, Billing Documents, GL Accounts and Journal Entries, Production Orders from SAP into Reltio and keeps both sides consistent in real time. Whatever SAP is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Reltio sync back into SAP with its validations respected.
Common use cases
- 01 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
- 02 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
- 03 Publish plant-level inventory to e-commerce and planning systems on change or on schedule.
- 04 Replicate journal entries and billing documents to a warehouse for finance analytics without loading the ERP.
Common sync patterns
React to ERP changes
Updates in SAP arrive as row changes in Reltio, so jobs and triggers can respond as the business record changes.
Where SAP is the HR system of record: people data for internal systems
Worker and org records stay current in Reltio for provisioning, access, and reporting systems that read from the database.
Controlled write-back
Choose exactly which tables and fields may flow from Reltio back into SAP, keeping the ERP authoritative.
What you can sync between Reltio and SAP
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.
| Reltio objects | SAP objects | How this pairing syncs | |
|---|---|---|---|
| Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. | Business Partners The unified customer and supplier master in S/4HANA, the anchor object for CRM and procurement syncs. | Relations is specific to Reltio and Business Partners to SAP — each maps to any object or custom field on the other side. | |
| Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. | Materials (Products) Item master with plant and sales views, synced to commerce, PLM, and CRM systems. | Crosswalks is specific to Reltio and Materials (Products) to SAP — each maps to any object or custom field on the other side. | |
| Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | Sales Orders Order documents written from external channels and read for status and fulfillment. | Interactions is specific to Reltio and Sales Orders to SAP — each maps to any object or custom field on the other side. | |
| Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Purchase Orders Procurement documents synced with supplier portals and spend tools. | Matches (Potential Matches) is specific to Reltio and Purchase Orders to SAP — each maps to any object or custom field on the other side. | |
| Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Outbound Deliveries Shipment documents synced to WMS, carriers, and customer portals. | Activity Log is specific to Reltio and Outbound Deliveries to SAP — each maps to any object or custom field on the other side. | |
| Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Billing Documents Invoices read for AR status and replicated for revenue reporting. | Data Change Requests (DCR) is specific to Reltio and Billing Documents to SAP — each maps to any object or custom field on the other side. |
How changes propagate between Reltio and SAP
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.
Reltio SAP Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is written to SAP through its API, with automatic retries and rate-limit backoff.
SAP Reltio Sub-second propagation
DetectionSAP notifies Stacksync of record changes through webhook events. Business events via SAP Event Mesh on S/4HANA.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
- SAP: Throttling is configured at the gateway and tenant level rather than as a single published rate limit.
What ships with Reltio ⇄ SAP
Connect Reltio and SAP for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–SAP connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Reltio or SAP 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 Reltio or SAP record.
Observability
Monitoring
Track your Reltio ⇄ SAP sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Reltio and SAP.
How the Reltio and SAP connectors work
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
SAP
- Integration surface
- OData (v2/v4) APIs on S/4HANA; BAPI/RFC and IDoc on ECC and on-prem systems; SOAP services
- Authentication
- OAuth 2.0 or basic auth via communication arrangements on cloud editions; SAP user credentials for RFC on-prem
- Change detection
- Business events via SAP Event Mesh on S/4HANA; change pointers with IDocs or timestamp polling on ECC
- Capabilities
- read · write · webhooks
- Rate limits
- Throttling is configured at the gateway and tenant level rather than as a single published rate limit
How it works
How to connect Reltio to SAP — 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.
- 01
Connect your apps
Authenticate Reltio and SAP with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Reltio
connected
SAP
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Reltio and SAP 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.
objects · Reltio ⇄ SAPCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Reltio SAPCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Reltio and SAP integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Reltio and SAP: authenticate both systems, choose the objects to sync (such as Reltio's Relations and Crosswalks), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Reltio and SAP. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Reltio: Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks. On SAP: Business events via SAP Event Mesh on S/4HANA; change pointers with IDocs or timestamp polling on ECC. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Reltio side: Activity Log, Data Change Requests (DCR), Reference Data (RDM), Entities, plus custom fields where Reltio exposes them. On the SAP side: Outbound Deliveries, Billing Documents, GL Accounts and Journal Entries, Production 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 Reltio and SAP: React to ERP changes; Where SAP is the HR system of record: people data for internal systems; Controlled write-back. Updates in SAP arrive as row changes in Reltio, so jobs and triggers can respond as the business record changes.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 455 integrations available for Reltio and SAP.
Popular · 5 of 455
No integrations match .
