SAP Business One.exe: the process name, the install path, and the one reason it gets looked up.

The SAP Business One process family

One name people remember is the client. In practice B1 is a set of binaries split across the operator desktop and the server. These are the ones you are most likely to see on the machine where a user actually works.

Server-side, for context

These do not run on an operator desktop. They matter because they are how the client finds its license and, in HANA editions, how a REST integration reaches B1 data. Neither one drives the actual client window, which is the gap the process name fills.

Finding the process and confirming it is the real one

Two commands cover almost everything. The first lists the process and its PID; the second resolves the full path so you can confirm it really is the signed SAP binary and not something parked in a temp folder with a familiar name.

The PID matters the moment you want to do anything with the window beyond looking at it: attach a debugger, point an accessibility inspector like inspect.exe at it, or scope an automation runtime to that exact process rather than to whatever window happens to be in focus.

Why automation people look up the exact process name

Most people who type the precise string "SAP Business One.exe" are not chasing a virus. They are trying to target it. To automate the B1 client, a runtime has to bind to a specific process, and the process name is how you scope that binding so the automation acts on the B1 window and nothing else.

Here is the part that makes B1 different from the big SAP ERP frontend. SAP GUI Scripting, the COM automation interface a lot of teams reach for, belongs to SAP GUI for Windows, the client for SAP ERP / S/4HANA. That is a separate product. The B1 client does not expose that scripting API. B1’s documented surfaces are the UI API (SAPbouiCOM, the sapbouicom.exe bridge), the DI API, and, in HANA editions, the Service Layer. Each of those is useful, and each only reaches what its object model chooses to expose. None of them drive the actual visible client the way a human does.

The surface that does cover the whole window is the one the operating system already publishes: the Microsoft UI Automation tree of the SAP Business One.exe process. It is the same interface a screen reader uses, so the B1 client exposes its fields, buttons, and matrix cells with stable names and control types. An automation runtime attaches to the process by name, reads that tree, and addresses the Customer field as name:Customer | role:Edit rather than as a pixel rectangle. That is why the process name is load-bearing: it is the entry point to the only automation surface that sees the entire B1 client.

This is the approach Mediar uses to drive B1. No SAP GUI Scripting, no screen scraping, no OCR, no hand-tuned coordinates that break when a patch reflows a form. The runtime watches a workflow once, then replays it against the accessibility tree of SAP Business One.exe. If you want the field-level mechanics, the accessibility-tree walkthrough picks up exactly where this reference leaves off.