Power Automate Has No SAP Business One Connector: What the SAP ERP Connector Covers

No, Power Automate does not offer a standard connector for SAP Business One. Microsoft ships two SAP connectors, the SAP ERP connector and the SAP OData connector. The SAP ERP connector speaks exclusively RFC and BAPI and targets SAP ECC, S/4HANA, and products on the NetWeaver stack. Business One does not come with these interfaces.

What Does the SAP ERP Connector Actually Cover?

The SAP ERP connector is an RFC connector, not a general-purpose SAP connector. Microsoft states the boundary right in the connector reference itself: "The connector supports only RFCs and BAPIs". Anything a SAP system does not expose as a remote-callable function module is unreachable through this path. That is the decisive point, not the question of the product name.

• Scope: SAP ECC, S/4HANA, and according to Microsoft's FAQ any SAP product running on the NetWeaver stack
• Requirements: an on-premises data gateway from version 3000.194 (October 2023) and the SAP .NET Connector NCo 3.1 in the 64-bit build, 32-bit is not supported
• License tier: Premium in Power Automate, Power Apps, and Copilot Studio
• Throttling: 2,500 calls per connection within 60 seconds

For SAP products outside the NetWeaver stack, Microsoft names the alternative path in the same FAQ: "use custom REST and SOAP connectors". That is exactly where Business One lands.

Why Does SAP Business One Fall Outside the Standard?

SAP Business One is its own product line with its own interfaces. Its documented programming interfaces are the Service Layer and the DI API, not RFC and BAPI. SAP's own Service Layer guide even includes a section on the functional differences between the Service Layer and the DI API, treating both as valid paths into the system. Business One does not appear anywhere in Microsoft's entire SAP connector documentation.

Which Path Leads to Business One Instead?

Through the Service Layer, SAP Business One's REST interface based on the OData standard. It runs over HTTPS by default and is available both for the Microsoft SQL Server variant (from 10.0 PL01) and the HANA variant. Since Feature Package 2405, OData version 4 has been the primary protocol: /b1s/v1/ serves the deprecated version 3, /b1s/v2/ serves version 4.

The point that determines the architecture is the login. The Service Layer authenticates on a session basis: a POST to /b1s/v1/Login with company, user, and password returns a cookie named B1SESSION, which, according to SAP's guide, must be sent with every subsequent call. The session expires by default after 30 minutes of inactivity. A simple Basic authentication per call does not exist for this purpose, it is explicitly reserved for the Semantic Layer and must not be reused for resources like BusinessPartners or Orders.

This means the SAP OData connector does not simply work either. Its documented login methods are Basic, an anonymous token, and Microsoft Entra ID via Azure API Management or via SuccessFactors. A B1SESSION cookie with an expiration time is not accounted for there. In practice, two paths remain: a custom connector built on the Service Layer or direct HTTP calls, in both cases with a self-built login and session renewal. Both paths are Premium territory, because access to Premium and custom connectors depends on a Power Automate Premium license.

We build such integrations first against a test company before real documents flow through. How the Service Layer, OData, and RFC middleware differ architecturally is covered in our comparison of connection paths. You'll find the framework for this on our page on SAP Business One consulting.

Frequently Asked Questions

Can I Simply Point the SAP OData Connector at the Service Layer?

Technically, the Service Layer speaks OData, the hurdle lies in the login. According to Microsoft's documentation, the SAP OData connector supports Basic, anonymous token, and Microsoft Entra ID via Azure API Management or SuccessFactors. Business One's session-based login with the B1SESSION cookie is not among them. Anyone who wants to take this path usually inserts a custom layer in between.

Do I Need an On-Premises Data Gateway for Business One?

The gateway is a prerequisite for the SAP ERP connector, that is, the RFC path. For the Service Layer over HTTPS, the question instead is one of reachability: it typically runs inside your own network. Without controlled access from outside, no cloud flow can reach it, and this access needs to be clarified before the first flow, not afterward.

Does Such an Integration Affect My SAP Licenses?

It can, and that needs to be on the table before you build anything. Business One is not billed according to the core SAP system's Digital Access model, but by named users. We've broken down what this means for automated access in RPA or SAP Process Automation. In the end, your contract is what governs, not a policy document.