1. Home
  2. SAP integration
  3. Salesforce and SAP

Salesforce and SAP connect four ways, and the SAP product you run decides which door each route uses

Salesforce and SAP connect four ways: MuleSoft, SAP Integration Suite, Salesforce Connect or your own build. Which one fits depends on the SAP product you run: Business One, S/4HANA or ECC. We read both vendors' documents on 18 November 2026 for what each route needs.

Checked 18 November 2026

MuleSoft’s templates show what moves: customers and products from SAP, won deals from Salesforce

MuleSoft’s own templates show the usual pattern. Its Salesforce to SAP templates cover accounts, opportunities and products. Its SAP to Salesforce ones cover customers and product materials. It also lists two-way sync templates for accounts and products. Its SAP and Salesforce page adds one more use: won opportunities sent to SAP so SAP can create the invoice.

Scroll the table sideways to see every column.

What moves Direction Salesforce record SAP record
Customer SAP to Salesforce Account Business One BusinessPartners
Product and price SAP to Salesforce Product2 and PricebookEntry Product material, in MuleSoft’s templates
Won deal Salesforce to SAP Opportunity and OpportunityLineItem Sales order: Business One Orders, or the S/4HANA Sales Order (A2X) API
Quote Your choice Quote Business One Quotations

SAP should own customers and the price list, because SAP builds the invoice from them. Salesforce should own leads and opportunities. Write that split down before anyone maps a field.

MuleSoft, Salesforce’s own platform, sells two SAP connectors

MuleSoft is Salesforce’s own tool for linking systems. It has two connectors for SAP.

The SAP Connector works with SAP systems built on SAP NetWeaver. MuleSoft says ECC and CRM run on that base, so the connector reaches them. It uses SAP’s Java Connector libraries to call remote function modules and to read IDocs, SAP’s Intermediate Documents. MuleSoft lists sales order automation between SAP ERP and a CRM such as Salesforce as a common use.

Before you start, MuleSoft lists what you need:

  • A separate license. MuleSoft says the SAP Connector needs its own license, beyond the platform.
  • An SAP ID. You need one to download SAP’s libraries.
  • An SAP service user. Its roles must allow every RFC, BAPI and IDoc the flow calls.

The second connector works through the OData APIs of S/4HANA, in the cloud or on site. It needs a communication user, set up for each API you call.

SAP says Integration Suite connects SAP with Salesforce, Workday, AWS and ServiceNow without custom code. For S/4HANA Cloud Public Edition, SAP points other apps to SAP BTP and Integration Suite. SAP says a BTP trial account lasts 90 days; ask SAP whether yours includes Integration Suite.

We could not read SAP’s guide to its Salesforce adapter. The SAP Help page we fetched for it on 18 November 2026 loads by script and gave our fetcher no text. So we cannot tell you which Salesforce objects and events SAP’s adapter covers. Ask SAP for that list before you choose. For the rest of SAP’s own route, see SAP integration.

Salesforce Connect reads OData sources live, but test Business One first

Salesforce Connect shows SAP records inside Salesforce as external objects. Salesforce says they reach the data in real time through web service callouts, instead of copying it into your org. Its own guide names SAP as an example source for the OData adapters.

This route fits a rep who needs to see SAP data on an account without a copy. Salesforce says external objects suit large data you cannot or do not want to store, when you need only a little at a time. Its own example is ERP data stored on premises.

SAP has to expose the data as an OData service. S/4HANA Cloud lists OData APIs on SAP’s Business Accelerator Hub. The Business One Service Layer speaks OData version 4. But it signs in with a session cookie, and its basic sign-in works only for its Semantic Layer. We found no SAP or Salesforce document that shows Salesforce Connect reading Business One directly. Test the sign-in in a sandbox first. External objects need Salesforce API version 32.0 or later.

A custom build listens for Salesforce changes and posts to SAP’s APIs

A direct build suits one or two flows. The build goes against each vendor’s published API.

On the Salesforce side, Change Data Capture tells your code when a record is created, updated, deleted or undeleted. You listen for opportunity changes on the channel /data/OpportunityChangeEvent. Salesforce keeps change events for three days, so a listener that was down can catch up. For loads over 2,000 records, Salesforce points to Bulk API 2.0.

On the SAP side, the door depends on the product:

Scroll the table sideways to see every column.

SAP product Where a won deal lands Rules that shape the build
S/4HANA Cloud Sales Order (A2X) API, path /sap/opu/odata/sap/API_SALES_ORDER_SRV Calls need a CSRF token. A communication user signs in with Basic or X.509 authentication.
Business One Service Layer, a POST to /Orders No more than 10 operations in one transaction. A session ends after 30 minutes idle by default.
Business One with approvals on The order becomes a draft SAP returns error code -2028 unless the call asks for no content back.

Business One can now push changes too. Since 10.0 FP 2602, the Service Layer can send webhooks when a business object is created or updated. So SAP can tell your code about a new delivery. Nobody has to poll.

Every call your code makes to Salesforce counts against the org’s daily allocation. Salesforce says Enterprise Edition starts at 100,000 calls a day, plus more per license.

Salesforce users can count as SAP Business One named users

On SAP Business One, an integration user may not be the only one who needs a license. SAP’s license guide is dated 11 November 2019. It defines a named user as an employee of yours, of a subsidiary or of a third party who uses the software directly or indirectly. That can include the Salesforce reps whose clicks create SAP orders.

The guide says Indirect Access rights must be ordered in your contract. The license types that include them are listed on SAP integration. We found no S/4HANA rule on indirect use at a source we could read. Ask SAP or your reseller to put your position in writing before go-live.

Your SAP product and your team pick the route

Scroll the table sideways to see every column.

If this is you Start with
ECC on premises, many systems, an integration team MuleSoft with its SAP Connector, or SAP Integration Suite
S/4HANA Cloud, and other SAP cloud products SAP Integration Suite, or direct calls to the OData APIs
Reps only need to see S/4HANA data in Salesforce Salesforce Connect with an OData adapter
Business One, one or two flows A custom build on the Service Layer

Agentforce and Joule Agents both speak A2A

Both vendors now support the same agent protocol. Salesforce says Agent2Agent (A2A) support lets Agentforce connect to third-party agents. SAP says its Joule Agents use MCP and A2A for work across systems, and that Integration Suite connects Joule with outside agents such as Claude.

Inside Salesforce, Agentforce Builder connects agents to Flows, Apex and MuleSoft APIs. In SAP Cloud ERP Private, SAP says agents inherit role-based access and approval strategies, like a person would.

One agent job here: a deal is marked Closed Won, the agent drafts the sales order in SAP, and a person approves it.

Our team has built Salesforce agents in Agentforce and as custom agents through Salesforce’s API. For that work, see Salesforce AI agents. For agents inside SAP, see SAP AI agents.

If you run ECC, plan the Salesforce link for the day you leave it. SAP’s maintenance page says mainstream maintenance for Business Suite 7 runs to the end of 2027; the later dates are on SAP integration.

If you move to S/4HANA Cloud Public Edition, plan the link on its ready-made APIs, such as Sales Order (A2X). On the private edition, test each BAPI and IDoc call again before the move. Either way, keep the field mapping and business rules apart from the SAP connector, so the move swaps one piece, not the whole link.

Our team has implemented both Salesforce and SAP

We take Salesforce implementation end to end: the org set up, data moved in, the team trained. And we have taken SAP Business One, SAP S/4HANA and SAP ECC live, and can run an SAP implementation end to end.

For Salesforce’s own limits and routes, see Salesforce integration. The first call is free.

Questions

What is SAP and Salesforce?

Two systems that sit on either side of a sale. Salesforce is a CRM: leads, accounts, opportunities and quotes. SAP is an ERP: it runs orders, stock, invoices and the books. SAP Business One is SAP's product for small and midsize firms, and S/4HANA is for firms of all sizes. MuleSoft's own SAP and Salesforce page names one job that links them: sending won opportunities to SAP for invoice creation.

What are the different types of Salesforce integration with SAP?

Four, in practice. MuleSoft, Salesforce's own platform, with its SAP connectors. SAP Integration Suite, SAP's own platform. Salesforce Connect, which reads SAP data live through OData without copying it. Or a custom build on both APIs, often driven by Salesforce change events. Any route that calls Salesforce's APIs spends from your org's daily allocation.

How does SAP integrate with other systems?

It depends on the SAP product. SAP Business One opens its Service Layer, a web API that speaks OData. S/4HANA Cloud publishes OData APIs on SAP's Business Accelerator Hub, such as the Sales Order (A2X) API. Older SAP ERP systems built on NetWeaver, such as ECC, use BAPIs, RFCs and IDocs. MuleSoft's SAP connector calls them through SAP's Java libraries.

Do Salesforce users need SAP licenses when the integration writes to SAP?

They may, and you should ask before go-live. SAP's Business One license guide, dated 11 November 2019, counts people who use the software indirectly as named users too. It says indirect access rights must be ordered in your contract. We found no S/4HANA license rule at a source we could read, so for S/4HANA ask SAP or your reseller in writing.

Should we pick MuleSoft or SAP Integration Suite?

Pick the one your team will run. Each is its vendor's own platform, and each says it connects to the other side. MuleSoft's SAP Connector needs a separate license, an SAP ID to download SAP's libraries and an SAP service user. SAP says Integration Suite connects SAP to Salesforce without custom code. If you have one flow and Business One, a direct build on the Service Layer may be enough.

Can Salesforce show SAP data without copying it?

Yes, through Salesforce Connect. It turns SAP records into external objects that Salesforce reads live through web service callouts. Salesforce's own guide names SAP as an example source for its OData adapters. It suits large data you need only a little of at a time. SAP must expose the data through an OData service. For Business One, we found no document that shows Salesforce Connect reading it directly.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Talk to us about Salesforce and SAP

Tell us which SAP product you run and which record should move first. The first call is free.

Book a Salesforce and SAP call