1. Home
  2. Systems
  3. SAP integration

SAP integration starts with which SAP you run, because Business One, S/4HANA and ECC each open a different door

SAP has no single integration API, because each SAP product opens its own door. Business One uses the Service Layer, S/4HANA Cloud uses OData APIs, and ECC uses BAPIs, RFCs and IDocs. SAP Integration Suite, other vendors' connectors or a custom build sit on top.

Checked 18 November 2026

Which door each SAP product opens

Start from your SAP product, because the API, the sign-in and the limits all change with it. The table sums up what SAP’s own documents say for each one.

Scroll the table sideways to see every column.

SAP product Main API How software signs in Limits we found
SAP Business One The Service Layer, an HTTP and OData API. OData version 4 is the main protocol since feature package 2405 Log in with the company database, user name and password, then send the B1SESSION cookie. A Windows domain account works since 10.0 FP 2305 At most 10 operations in one transaction. A session ends after 30 minutes idle by default
SAP S/4HANA Cloud Ready-made APIs listed on the Business Accelerator Hub, such as Sales Order (A2X) at /sap/opu/odata/sap/API_SALES_ORDER_SRV A communication user with Basic or X.509 authentication, or OAuth 2.0 with a SAML bearer assertion. Calls need a CSRF token We found no published rate limit we could read
SAP ECC and other NetWeaver systems BAPIs called over RFC, and IDocs sent over tRFC or qRFC An SAP service user whose roles allow those calls, through SAP’s connector libraries such as JCo or NCo We found no published limit in what we read

Three Business One details shape a build. SAP says the Service Layer API and the older DI API have identical definitions for objects and object properties. A new user-defined field or table does not show up in the Service Layer until it restarts. And since 10.0 FP 2602, the Service Layer checks an access token’s audience by default for Single Page Apps. A token without the Service Layer client ID gets a 401 error.

Business One also has a separate tool for links, called B1i. In FP 2608 it gained automatic rotation of the keys and certificates it uses to sign in.

SAP Integration Suite is SAP’s own route, with API management built in

SAP calls Integration Suite an integration platform as a service. It connects apps, data and AI agents across SAP and other vendors’ systems. SAP says the one platform also covers API management, events, B2B and EDI. Its API layer lets teams publish and watch every connection from one place. SAP says it links 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.

It now serves agents too. SAP says Integration Suite can turn your APIs into MCP servers that agents can use. It also links Joule with outside agents such as Microsoft Copilot, Claude and LangChain. It applies sign-in, rate limits and policy controls to that agent traffic.

To try it, SAP says a BTP trial account lasts 90 days. SAP also offers a free tier account with no time limit and more than 90 services across its plans. Ask SAP which of those include Integration Suite.

Each SAP product can push changes out, so your code need not keep asking

Each SAP product has its own way to tell other software that a record changed.

  • Business One webhooks. Since 10.0 FP 2602, the Service Layer can notify an outside app when a business object is created or updated. Webhooks are off by default for each company. They need a new piece, the Webhook Messenger Service, and they arrive in batches by default. With HMAC sign-in, the handshake carries a signature header.
  • Event Mesh. SAP’s tutorial says a queue links two apps point to point, while topics do not keep messages. Deleting a queue deletes its messages too.
  • Event Hub for S/4HANA Cloud. You set it up in the Maintain Extensions on SAP BTP app, with the Eventing Between SAP Cloud Systems scenario group.
  • Advanced Event Mesh. SAP says it lets apps publish and subscribe to business events from SAP and other sources, across clouds and on site.

MuleSoft and Microsoft sell SAP connectors that call BAPIs over RFC

Two other vendors sell SAP connectors.

MuleSoft is Salesforce’s integration platform. Its SAP Connector works with SAP systems built on NetWeaver. MuleSoft says it runs BAPI functions over synchronous and asynchronous RFC, and sends and receives IDocs over tRFC and qRFC. It uses SAP’s Java Connector libraries, and it needs a separate license. MuleSoft’s second connector works with the OData APIs of S/4HANA Cloud and S/4HANA on-premise.

Microsoft Power Automate has an SAP ERP connector. Microsoft says it calls RFC and BAPI functions through an on-premises data gateway. It needs the SAP NCo 3.1 64-bit library, and a gateway at version October 2023 (3000.194) or later. Downloading NCo needs a valid SAP S-user.

For SAP data in Databricks, SAP’s own route runs through Business Data Cloud, which SAP built with Databricks inside. See SAP and Databricks integration.

SAP licenses: integration users can count in Business One

Check licensing before you design the link. SAP’s Business One 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. So staff who create SAP records from another system may count.

The guide says the Professional, Limited CRM, Limited Financials, Limited Logistics and Starter license types include Indirect Access rights. Those rights must be ordered in your contract. From version 9.2, the logon limit for a named user covers Indirect Access licenses too.

We found no S/4HANA rule on indirect use at a source we could read. Ask SAP in writing.

Will SAP be supported after 2027?

Yes for S/4HANA, and on a clock for ECC. SAP’s maintenance page says SAP will keep at least one S/4HANA release in maintenance until 2040.

Scroll the table sideways to see every column.

SAP product What SAP says about support
S/4HANA At least one release in maintenance until 2040
Business Suite 7, including ECC Mainstream maintenance to the end of 2027. Optional extended maintenance from 2028 to the end of 2030, for two more percentage points on the maintenance basis. After that, customer specific maintenance
The largest Business Suite 7 customers A Transition Option covers business continuity from 2031 through 2033
SAP Business One 10.0 Mainstream maintenance until 31 December 2028, a date SAP marks as subject to change. Version 11 follows. No extended maintenance

SAP News, in October 2026, told customers to plan to finish their move to SAP Cloud ERP by the end of 2030. For integration, that matters now. If you move to S/4HANA Cloud Public Edition, plan the link on the ready-made APIs SAP lists on the Business Accelerator Hub. On the private and on-premise editions, test each BAPI and IDoc call again before the move. Either way, keep your field mapping and rules apart from the SAP connector, so the move swaps one piece.

Joule Agents and a Business One MCP server now reach outside SAP

SAP says its Joule Agents use MCP and the A2A protocol. They work across SAP and non-SAP systems.

Business One has its own path. Its 10.0 FP 2608 added support for an open source MCP server that connects AI agents to the Service Layer. MCP is a standard way for AI tools to use other software. Joule Studio, SAP’s tool for custom agents, can act across SAP and non-SAP systems too. But the AI in the Business One Web client cannot read or change Business One data, SAP says.

For SAP Cloud ERP Private, SAP says agents inherit role-based access and approval strategies. There, each AI action is logged in the ERP change log, like a person’s.

See SAP AI agents for agent jobs, and our research note on SAP Business One and Joule.

SAP’s API catalog and S/4HANA help gave our fetcher no text

Some SAP facts sit behind pages our fetcher could not read. SAP’s API catalog, api.sap.com, gave our fetcher no text, because it loads through a sign-in redirect. The help.sap.com/docs pages for S/4HANA Cloud load by script and gave us no text either.

So this page does not state any S/4HANA API rate limit, the supplier invoice API names, or the full list of S/4HANA business events. On a project, we read those in your own SAP system and on the Hub.

Two SAP pairings have their own pages

Each has its own page:

Our team has taken Business One, S/4HANA and ECC live

Our team has taken SAP Business One, SAP S/4HANA and SAP ECC live, and can run an SAP implementation end to end. Across all ERPs, we have taken nine live, from SAP to QuickBooks. The first call is free.

Questions

Does SAP have API access?

Yes, but each product has its own. SAP Business One has the Service Layer, a web API that speaks OData, plus the older DI API. S/4HANA Cloud comes with ready-made APIs that SAP lists on its Business Accelerator Hub, such as the Sales Order (A2X) API. Older SAP ERP systems built on NetWeaver, such as ECC, open BAPIs and RFCs, and swap IDocs.

What are the different types of interfaces in SAP?

SAP's interfaces fall into four families. Web APIs: REST, OData and SOAP, which SAP lists on the Business Accelerator Hub, and the Business One Service Layer. Function calls: BAPIs called over RFC in ECC and other NetWeaver systems. Documents: IDocs, SAP's Intermediate Documents, sent over tRFC or qRFC. Events: Event Mesh, Event Hub and Business One webhooks, which tell other software when something changes.

Will SAP be supported after 2027?

S/4HANA, yes: SAP says it will keep at least one S/4HANA release in maintenance until 2040. The older Business Suite 7, which includes ECC, is different. Its mainstream maintenance runs to the end of 2027, and optional extended maintenance runs to the end of 2030. SAP Business One 10.0 is in mainstream maintenance until 31 December 2028, a date SAP marks as subject to change, and version 11 follows it.

What is API full form?

API stands for application programming interface. In plain words, it is the door one piece of software opens so another can read and write its records. In SAP's case, the doors differ by product: the Service Layer in Business One, OData APIs in S/4HANA Cloud, and BAPIs over RFC in ECC. SAP's Business Accelerator Hub is where SAP lists them.

Do we need SAP Integration Suite to connect SAP to other systems?

No. Integration Suite is SAP's own platform, and SAP says it connects SAP with systems such as Salesforce and Workday without custom code. You can also use another vendor's connector, such as MuleSoft's or Microsoft's, or build straight on SAP's APIs. For SAP Business One and one or two flows, a direct build on the Service Layer is often the lighter choice.

Does an SAP integration need extra SAP licenses?

It can. SAP's Business One license guide, dated 11 November 2019, counts people who use the software indirectly as named users. It says indirect access rights must be ordered in your contract. So users of the other system may count. We found no S/4HANA rule on this at a source we could read. Ask SAP or your reseller in writing before go-live.

Do we need an official SAP partner to do this?

Not for this work. What decides an integration or a go-live is a team that knows SAP from the inside. That team builds on SAP's published APIs, such as the Business One Service Layer and the S/4HANA OData APIs. Our team has taken SAP Business One, S/4HANA and ECC live. You license SAP from SAP or its reseller, and we take the build from there.

Sources

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

Pages in this section

  • Salesforce and SAPConnect Salesforce to SAP Business One, S/4HANA or ECC through MuleSoft, SAP Integration Suite, Salesforce Connect or your own build. What each needs.
  • SAP and DatabricksSAP Databricks runs inside SAP Business Data Cloud. BDC Connect links the Databricks you already run. What each needs, from SAP and Databricks docs.

Talk to us about your SAP integration

Tell us which SAP product and release you run, and what must connect to it. The first call is free.

Book an SAP integration call