Real-time sync
Changes in Dun And Bradstreet or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Keep Dun And Bradstreet 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.
Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into SAP Hana, so SAP Hana always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in SAP Hana, where it can be queried and joined like everything else.
Field and stage updates in Dun And Bradstreet arrive as row changes in SAP Hana, ready to drive jobs and notifications.
Accounts, contacts, and custom objects from Dun And Bradstreet become tables in SAP Hana you can join with application data directly.
Signup, usage, or lifecycle changes written to SAP Hana sync onto the matching records in Dun And Bradstreet, giving go-to-market teams live product context.
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.
| Dun And Bradstreet objects | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Company Information (Data Block) Core firmographics for a D-U-N-S Number - legal name, addresses, industry codes, employees, sales, status. Retrieved read-only via the Enrich endpoint; blocks come in levels L1-L4. | Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. | Company Information (Data Block) is specific to Dun And Bradstreet and Calculation views to SAP Hana — each maps to any object or custom field on the other side. | |
| Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. | SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Principals & Contacts (Data Block) is specific to Dun And Bradstreet and SQL views to SAP Hana — each maps to any object or custom field on the other side. | |
| Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and Schemas to SAP Hana — each maps to any object or custom field on the other side. | |
| Financial Strength & Risk Insight (Data Block) D&B risk and credit signals - D&B Rating, PAYDEX, Failure Score, Delinquency Score, Viability - keyed by D-U-N-S Number; read-only. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Financial Strength & Risk Insight (Data Block) is specific to Dun And Bradstreet and Sequences to SAP Hana — each maps to any object or custom field on the other side. | |
| Identity Resolution (Match / cleanseMatch) Sends a company name and address and returns ranked candidate DUNS with confidence codes and a MatchGrade; read-only scored match, not an exact lookup. | 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. | Identity Resolution (Match / cleanseMatch) is specific to Dun And Bradstreet and Triggers to SAP Hana — each maps to any object or custom field on the other side. | |
| Criteria Search Query companies by firmographic criteria (industry, geography, size) and get back a list of D-U-N-S Numbers to enrich; read-only list building. | System-versioned temporal tables Column store tables with a history table tracking each row's validity period; used to reconstruct update and delete history for change capture. | Criteria Search is specific to Dun And Bradstreet and System-versioned temporal tables 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 Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).
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.
DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating SAP Hana records.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–SAP Hana connection.
Changes in Dun And Bradstreet or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dun And Bradstreet 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 Dun And Bradstreet or SAP Hana record.
Track your Dun And Bradstreet ⇄ SAP Hana sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dun And Bradstreet 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 Dun And Bradstreet 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 Dun And Bradstreet 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 integration between Dun And Bradstreet and SAP Hana — Dun And Bradstreet is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
On the Dun And Bradstreet side: Financial Strength & Risk Insight (Data Block), Identity Resolution (Match / cleanseMatch), Criteria Search, Monitoring Notifications, plus custom fields where Dun And Bradstreet exposes them. On the SAP Hana side: Sequences, Triggers, System-versioned temporal tables, System views (SYS schema). Stacksync auto-detects both schemas and converts types between the two systems.
Dun And Bradstreet is a read-only source, so this integration runs one-way: Stacksync reads from Dun And Bradstreet in real time and delivers into SAP Hana. Field mapping and monitoring work the same as for two-way pairs.
Common patterns for Dun And Bradstreet and SAP Hana: Trigger workflows from CRM changes; Query the CRM like a database; Product events onto CRM records. Field and stage updates in Dun And Bradstreet arrive as row changes in SAP Hana, ready to drive jobs and notifications.
Dun And Bradstreet: D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring. Authentication: OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours. 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.
Dun And Bradstreet: Auth is OAuth 2.0 client-credentials: Base-auth a key/secret to POST /v3/token for a bearer token, and access tokens expire after 24 hours. SAP Hana: System-versioned temporal tables are supported only on column store tables, not on the row store. Stacksync's field mapping accounts for these differences between Dun And Bradstreet and SAP Hana without custom code.
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 517 integrations available for Dun And Bradstreet and SAP Hana.