Fraud Blocker

Clarity Connect integration

Dynamics 365 SAP Integration

Keep Dynamics 365 Sales and Customer Service in step with SAP S/4HANA, so accounts, products, orders and invoices match in both, with Clarity Connect running the sync.

Dynamics 365 and SAP S/4HANA kept in sync through Clarity Connect

What moves between Dynamics 365 and SAP

The usual pairing is Microsoft's CRM apps, Dynamics 365 Sales and Customer Service, with SAP as the ERP. Most searches for it name SAP S/4HANA, so that is the SAP described here; ECC estates follow the same pattern with different SAP interfaces.

Dynamics 365 is where sellers manage accounts, opportunities and quotes, and where service agents handle cases. SAP is where the order is priced, fulfilled, billed and booked. The integration makes the account and product data the same in both, hands accepted quotes or orders to SAP, and returns order and invoice status to the people who talk to the customer.

CRM

Dynamics 365 Sales and Customer Service

Data stored in Microsoft Dataverse

  • Accounts and contacts
  • Products
  • Opportunities and quotes
  • Orders
  • Invoices
  • Cases
Clarity Connectreal time or scheduled
ERP

SAP S/4HANA

Where orders are fulfilled and billed

  • Business partners (customers)
  • Products (materials)
  • Sales orders
  • Deliveries
  • Billing documents

Dynamics 365 to SAP S/4HANA record mapping

Dynamics 365 names are Dataverse table names; SAP names are plain descriptions of the S/4HANA business objects. Discovery confirms which fields and rules apply.

Dynamics 365 (Dataverse table)SAP S/4HANADirection
accountBusiness partner (customer)SAP to Dynamics 365, or both ways
contactContact personBoth ways
productProduct (material) and priceSAP to Dynamics 365
quote / salesorderSales orderDynamics 365 to SAP
salesorder statusDelivery statusSAP to Dynamics 365
invoiceBilling documentSAP to Dynamics 365

How the Dynamics 365 sync runs

Accounts and products, one version

SAP is usually the master for customers and products, because credit limits, prices and tax settings live there. Connect writes SAP business partners and materials into Dataverse as accounts, contacts and products, with the SAP number stored on each row, so sellers never quote an item or a customer the ERP doesn't know.

Won business goes to SAP as a sales order

When a quote is accepted or an order is submitted in Dynamics 365 Sales, Connect reads it through the Dataverse Web API and creates the sales order in S/4HANA through SAP's sales order API. The SAP order number is written back to the Dynamics 365 order, so either team can find it.

Order, delivery and invoice status for sales and service

Delivery and billing status from SAP flows back onto the Dynamics 365 order and invoice rows. A service agent working a case in Customer Service can see whether the order shipped and whether it was invoiced, without a login to SAP.

See Clarity Connect move an order

Watch an online order travel into the ERP and its status come back in our Clarity Connect demo, or book a live walkthrough on your own systems.

Book a demo

Microsoft's own SAP connectors, and dual-write

Dynamics 365 Sales and Customer Service store their data in Dataverse, whose Web API implements OData 4.0. On the SAP side, S/4HANA's APIs, including its sales order and business partner APIs, are catalogued on the SAP Business Accelerator Hub.

Microsoft also offers SAP connectors. The Power Platform SAP ERP connector calls SAP RFCs and BAPIs through an on-premises data gateway and needs SAP's .NET Connector 3.1, 64-bit; the Azure Logic Apps SAP connector adds IDoc support. They suit individual flows built in Power Automate or Logic Apps. A full order-to-invoice integration also needs mapping, queuing and retries across many flows, which is the job Clarity Connect does.

If you run Dynamics 365 Finance or Supply Chain Management rather than SAP, Microsoft links it to Dataverse with dual-write, and you don't need this page. For SAP ECC, SAP's mainstream maintenance for Business Suite 7 runs to the end of 2027, so an ECC integration should be planned with the S/4HANA move in mind.

How Clarity Connect runs it

Clarity Connect is Clarity's integration platform. It keeps a persistent, two-way connection between Dataverse and SAP and runs each flow, such as accounts to Dynamics 365 or orders to SAP, as its own task, in real time or on a schedule. For SAP inside your network, Connect can run behind the firewall and reach Dynamics 365 in the cloud outbound only. Clarity has built more than 3,000 integrations on Connect; recorded demos are in the Clarity Connect video playlist.

How a Clarity Connect project runs
  1. Discovery

    A Clarity business analyst documents the data fields and workflows each system can share and which ones you need.

  2. Tasks and mapping

    Each flow becomes a Connect task, such as orders to the ERP or stock to the store, set to run in real time or on a schedule.

  3. Testing

    Orders and updates are run end to end, including the return trip of statuses back to the customer-facing system.

  4. Live, with a dashboard

    Queues and scheduled tasks show in Connect's Hangfire dashboard. A job whose target is offline is retried 10 times, every 30 minutes, and can be re-queued once the cause is fixed.

Clarity Connect is sold as a SaaS subscription at $599 a month or as a one-time license at $15,000 with no ongoing fees, and larger projects are priced to scope. See pricing.

Questions

Which Dynamics 365 apps does this cover?

Dynamics 365 Sales and Customer Service, which store their data in Dataverse. Dynamics 365 Finance and Supply Chain Management link to Dataverse through Microsoft's dual-write instead.

Can we use Microsoft's SAP connector instead?

For a handful of calls, perhaps. The Power Platform SAP ERP connector calls RFCs and BAPIs through an on-premises data gateway. A complete integration also needs field mapping, queues and retries across every flow.

Does it work with SAP ECC as well as S/4HANA?

Yes. The Dynamics 365 side is the same; ECC is usually reached through BAPIs and IDocs rather than S/4HANA's OData APIs.

Which system owns the customer record?

Usually SAP, because credit, pricing and tax data live there. Discovery confirms it, along with whether new accounts may start in Dynamics 365.

Related resources

Connect Dynamics 365 and SAP

Tell us where your sales process ends and SAP takes over. A Clarity business analyst will map accounts, products, orders and invoices with your team before anything is built.

Book a demo