Salesforce SAP
integration.
Connect Salesforce with SAP S/4HANA or SAP ECC so accounts, products, orders and invoices agree across CRM and ERP.
Salesforce SAP integration connects Salesforce with SAP S/4HANA or SAP ECC so accounts, products, prices, orders and invoices move between CRM and ERP. SAP systems expose interfaces such as OData, SOAP, IDoc, BAPI and RFC. Most teams connect them through middleware, such as MuleSoft Anypoint Platform or SAP Integration Suite, which both offer SAP and Salesforce connectors.
How it works
How does Salesforce integrate with SAP S/4HANA?
Usually through middleware. MuleSoft offers SAP S/4HANA OData and SOAP connectors and an SAP connector that uses IDoc or BAPI over RFC. SAP Integration Suite offers Salesforce sender and receiver adapters, including adapters for the Salesforce Pub/Sub API. The middleware maps records and handles errors between the two.
The connector
Every SAP program is also a Salesforce program.
Techila Global Services is a Salesforce Summit Partner. We design and build the Salesforce side of SAP integrations, and the middleware flows between the two, working with your SAP team on the ERP side.
We start by agreeing which system owns each record, then pick the SAP interface and middleware that fit your SAP release and your volumes. For the wider CRM and ERP split, see is Salesforce an ERP?
For manufacturers, these flows feed Manufacturing Cloud sales agreements and forecasts.
Read about our MuleSoft services
Which SAP interfaces can Salesforce integrations use?
| Interface | What the vendor docs say | Where it fits |
|---|---|---|
| OData | MuleSoft's SAP S/4HANA OData connector supports OData APIs exposed by SAP S/4HANA. SAP Integration Suite has OData adapters for OData 2.0 and 4.0. | S/4HANA, cloud or on-premise |
| SOAP | MuleSoft's SAP S/4HANA SOAP connector supports the SOAP APIs exposed by SAP S/4HANA ERP. | S/4HANA on-premise |
| IDoc | MuleSoft's SAP connector sends and receives IDocs over tRFC and qRFC. SAP Integration Suite has IDoc sender and receiver adapters. | Master data and document flows, ECC or S/4HANA |
| BAPI over RFC | MuleSoft's SAP connector runs BAPI functions over synchronous and asynchronous RFC and needs the SAP JCo libraries from SAP. | ECC and on-premise S/4HANA |
| RFC adapter | SAP Integration Suite's RFC receiver adapter connects on-premise ABAP systems through SAP Cloud Connector and supports SAP NetWeaver 7.31 or higher. | On-premise SAP reached from the cloud |
MuleSoft says its connectors for SAP NetWeaver were certified by the SAP Integration and Certification Center (SAP ICC).
MuleSoft or SAP Integration Suite?
| Option | SAP and Salesforce pieces | Good fit when |
|---|---|---|
| MuleSoft Anypoint Platform | SAP, S/4HANA OData and S/4HANA SOAP connectors, plus the MuleSoft Accelerator for SAP with pre-built APIs and templates for ECC and S/4HANA, including real-time account and product sync to Sales Cloud and quote-to-cash | Salesforce is at the center and many non-SAP systems share the same data |
| SAP Integration Suite | Salesforce sender and receiver adapters, Salesforce Pub/Sub API adapters, plus IDoc, OData and RFC adapters | Your SAP team already runs SAP Integration Suite for other SAP flows |
| Custom build | Salesforce APIs called directly against SAP OData services | One or two simple flows with low volumes |
We help you choose the option, then build, test and support it as part of our Salesforce integration services. See Salesforce integrations, or talk to us about your setup.
Which flows should go live first?
- Customer and product master data from SAP into Salesforce, so quotes use the right accounts and materials.
- Orders from won opportunities or quotes into SAP, so sales orders are not re-keyed.
- Order, delivery and invoice status back into Salesforce, so sales and service can answer customers.
- Credit and pricing checks called from Salesforce at quote time, once the first flows are stable.
Which way do the first SAP flows go?
- Customer and product master data (from SAP S/4HANA or ECC to Salesforce)
- Orders from won deals or quotes (from Salesforce to SAP S/4HANA or ECC)
- Order, delivery and invoice status (from SAP S/4HANA or ECC to Salesforce)
- Credit and pricing checks at quote time (both ways)
To plan the order with your SAP team, talk to an integration architect.
What does a Salesforce SAP integration architecture look like?
Three layers, with the middleware in the middle doing the mapping, routing and error handling, so neither Salesforce nor SAP has to know the other's data model.
Salesforce SAP integration architecture
- SalesforceAccounts, opportunities, quotes and orders. Publishes changes as events, for example through the Pub/Sub API or Change Data Capture.System of engagement
- MuleSoft Anypoint Platform or SAP Integration SuiteMaps and routes records, retries failures and logs every message. MuleSoft adds the Accelerator for SAP; SAP Integration Suite adds Salesforce sender, receiver and Pub/Sub API adapters.Integration layer
- SAP S/4HANA or SAP ECCCustomers, materials, prices, sales orders and invoices, reached through OData or SOAP on S/4HANA, or IDoc and BAPI over RFC on ECC and on-premise S/4HANA.System of record
On-premise SAP reached from the cloud needs a secure path in: SAP Integration Suite's RFC receiver adapter uses SAP Cloud Connector, and MuleSoft's SAP connector needs the SAP JCo libraries from SAP.
How do you monitor a Salesforce SAP integration?
In the middleware, because that is where every message passes. Both platforms ship monitoring, and both sides of the business need to see it.
- Alert a named owner for each flow, not a shared inbox, and agree who fixes CRM-side and ERP-side errors.
- Keep the SAP document number on the Salesforce record, and the Salesforce ID in SAP, so either team can trace a record across.
- Watch volumes and API use after go-live, and again after month-end and price-list loads.
- Write a runbook for replaying failed messages, so a retry does not create a second sales order.
| Platform | What the vendor documents | Use it to |
|---|---|---|
| MuleSoft Anypoint Monitoring | Built-in application and API dashboards, custom dashboards, alerts, log search, traces and API functional monitoring. MuleSoft says Integration Advanced adds custom metrics, alerts, custom dashboards and log points over Integration Starter. | Alert when a flow fails or slows, and trace one order from Salesforce to SAP |
| SAP Integration Suite | A message processing monitor with a log of each message's processing steps, at selectable log levels, plus an overview of deployed integration content. SAP says logs are kept for a defined retention time. | Find a failed IDoc or OData call and see the step where it stopped |
What affects the timeline of a Salesforce SAP integration?
Scope and readiness on the SAP side usually matter more than the Salesforce build. The main drivers:
- SAP release. S/4HANA usually exposes OData and SOAP APIs; ECC usually means IDoc or BAPI over RFC, which needs the SAP JCo libraries and more SAP-side work.
- Middleware already in place. A team that already runs MuleSoft or SAP Integration Suite skips platform setup and reuses existing APIs.
- Number of flows and objects. Customer and product master data is one scope; adding orders, delivery and invoice status, credit and pricing checks multiplies mapping and testing.
- Record ownership decisions. Field-by-field agreement on which system owns customers, materials and prices is often the slowest step.
- Master data quality. Duplicate customers or inconsistent materials in SAP have to be cleaned or matched before they reach Salesforce.
- Connectivity and security. On-premise SAP needs Cloud Connector or a similar secure path, plus network and security approvals.
- Test environments. End-to-end tests need SAP and Salesforce sandboxes with realistic data, and time from the SAP team.
To size these drivers for your landscape, talk to an integration architect.
Architecture
How does data move between Salesforce and SAP?
Salesforce
Middleware
SAP S/4HANA or ECC
What's included
What does a Salesforce SAP integration project cover?
Looking for delivered work? See case studies
FAQ
Frequently asked questions.
What architects ask before commissioning a Techila integration.
Usually through middleware such as MuleSoft or SAP Integration Suite. MuleSoft offers S/4HANA OData and SOAP connectors; SAP Integration Suite offers Salesforce sender, receiver and Pub/Sub API adapters.
Yes. MuleSoft says it connects to SAP through IDoc or BAPI over RFC, which covers ECC as well as S/4HANA, and its Accelerator for SAP includes system APIs for both ECC and S/4HANA.
No. SAP Integration Suite has its own Salesforce adapters, and a small flow can call SAP OData services directly. MuleSoft suits programs where Salesforce and many other systems share data.
A set of pre-built APIs, connectors and templates on Anypoint Exchange for SAP ECC and S/4HANA, including real-time account and product sync to Sales Cloud and a quote-to-cash flow with S/4HANA.
In the middleware. MuleSoft's Anypoint Monitoring provides dashboards, alerts, log search and traces, and SAP Integration Suite provides a message processing monitor with a log of each message's processing steps.
It depends on the SAP release and the flow. OData suits S/4HANA APIs; IDoc and BAPI over RFC are common for ECC and document flows. Your SAP team's existing interfaces often decide it.
Sources
Last reviewed:
- MuleSoft, SAP integration solutions (read 10 November 2026)
- MuleSoft, SAP Connector documentation (read 10 November 2026)
- MuleSoft (Anypoint Exchange), MuleSoft Accelerator for SAP (read 10 November 2026)
- SAP Help Portal, Feature Scope Description for SAP Integration Suite (22 September 2026) (read 10 November 2026)
- MuleSoft, Anypoint Monitoring overview (read 11 November 2026)
- Salesforce Architects, Integration patterns (read 10 November 2026)
Talk to an expert about SAP Salesforce integration
Tell us what you need. We reply within 1 business day.
Let's plan your next Salesforce program.
We reply within 1 business day · +1 617-777-9873
See case studies