SAP Business One Web Client: what switching from the Windows client means

The SAP Business One Web Client is the browser-based alternative to the classic Windows client. According to the SAP Help Portal, it runs on both an MS SQL Server and an SAP HANA database and maps the same core business logic as SAP Business One, but with a new user interface in SAP Fiori design. Technically, the Web Client requires an installed Service Layer registered in the System Landscape Directory, runs by default over port 443, and supports Mozilla Firefox, Google Chrome, and Apple Safari on Mac and iPad as browsers. Anyone switching should above all check two things beforehand: whether existing extensions continue to work in the new model, and which processes are to be automated via the Service Layer in the future. As of: August 2026.

What does the Web Client need technically before it runs?

According to the SAP Business One Administrator's Guide, the Web Client requires an installed Service Layer with a valid registration in the System Landscape Directory (SLD). Installation also requires Windows PowerShell 5 or higher on the target machine, and anyone wanting to use the reporting functions or the Microsoft 365 integration in the Web Client must additionally install the Job Service. Installation itself runs via the ComponentsWizard: select the Web Client feature, specify the network address and security certificate, connect the landscape server, and determine a port, by default 443. Access then takes place via a URL following the pattern server name or IP address, followed by the chosen port. One point that often causes confusion in practice: the Web Client does not restart automatically after a Windows server reboot, but must be restarted manually.

Does the interface in the browser work exactly like in the Windows client?

The core processes are the same, but the interface has been rebuilt. According to the User Guide for SAP Business One, Web Client, the Web Client is based on the SAP Fiori design concept with a tile-based home page, from which modules such as Sales, Purchasing, Business Partners, Payments, Inventory, Production, Accounting, Service, and Human Resources can be accessed. For Web Client operation, SAP explicitly recommends Google Chrome or Mozilla Firefox as the default browser, ideally set centrally via Group Policy in Windows domains. Individual functions differ depending on the country version: the documentation points out in several places that certain fields or document types are not available in individual localizations such as India, Brazil, or China. Before switching, it is therefore worth comparing against your own country version.

Do existing add-ons and extensions continue to work in the Web Client?

Not automatically. The Web Client comes with its own extension model: tile links and extensions based on technologies such as SAPUI5, React, Vue, or Angular, connected via the Service Layer and a dedicated Web Client UI API. These extensions appear as new tiles in the Fiori Launchpad, which is fundamentally different from classic add-ons for the Windows client. An existing add-on therefore does not automatically carry over, but must be evaluated separately. How real this issue is in practice is shown by reports from the SAP Community: users there report error messages such as "Add-on is not compatible with current platform", triggered by a mismatched architecture between the add-on and the SAP Business One client. One more reason to check each extension individually before switching, rather than assuming functional equivalence.

What role does the Service Layer play in the switch?

According to the SAP Help Portal, the Service Layer is the central backend data service through which the Web Client, its extensions, and the SAP Business One app for Microsoft Teams run. Anyone who also wants to introduce automation as part of the switch, for example exchanging document data between SAP Business One and other systems, technically builds on the same Service Layer already used by the Web Client. For security reasons, the documentation states that the Service Layer's certificate should be stored as trusted within your own organization, which applies to the Web Client itself just as much as to the Teams integration or external automation workflows. We have described how SAP Business One can be technically connected via the Service Layer, OData, or RFC middleware in a separate article. If you also want to build automation workflows around SAP Business One as part of the switch, we support you with that as part of our automation consulting.

Frequently asked questions about SAP Business One Web Client

Is the Web Client a full replacement for the Windows client?

For most core processes, yes: Sales, Purchasing, Business Partners, Payments, Inventory, Production, Accounting, and Service are mapped in the Web Client according to the User Guide. However, individual fields and document types differ depending on the country version, and not every Windows client extension carries over automatically. A complete switch is therefore only worthwhile after a functionality and add-on check for your own installation.

What is the Service Layer, and why do I need it for the Web Client?

The Service Layer is the backend data service on which the Web Client technically relies. Without an installed Service Layer registered in the SLD, the Web Client cannot be installed at all, according to the Administrator's Guide. The same Service Layer is also used for extensions, the Teams integration, and external automation.

Do I need to rebuild my existing add-ons for the Web Client?

Probably yes, if they were classically developed for the Windows client. The Web Client uses its own extension model based on SAPUI5, React, Vue, or Angular. Before switching, check every business-critical extension individually rather than assuming automatic compatibility.

Can I use the Web Client in Microsoft Teams as well?

Yes, via the SAP Business One app for Microsoft Teams, which according to the User Guide is available for on-premise installations from version 10.0 FP 2111 onward. A trusted certificate for the Web Client and Service Layer, as well as a Microsoft Teams admin account, are required to install the app.