Automate SAP and ERP screens — no scripting, no API
Drive the SAP GUI for Windows client the way a clerk does — entering transactions, tabbing between fields, posting from a spreadsheet — through the operating system's accessibility layer. It works even when SAP GUI Scripting is disabled, and every commit waits for your approval.
- 1-click uninstall
- Cancel anytime
- Files never leave your computer
At a glance
| Scripting / RPA | Lapu AIRecommended | |
|---|---|---|
| Needs sapgui/user_scripting = TRUE | ||
| Works when Basis disables scripting | ||
| Connects via | COM Scripting API | Windows UI Automation |
| Security popup on attach | ||
| Approval before commits |
Impact
What changes
The same task, two ways — how it plays out by hand today, and what changes once Lapu AI runs it for you.
Without Lapu AI
With SAP GUI Scripting disabled, the RPA tool cannot attach, so a finance clerk re-keys every invoice and master-data change into SAP by hand, cross-checking a spreadsheet against the screen line by line.
With Lapu AI
Lapu AI reads the SAP window through accessibility, types each transaction the way the clerk would, reconciles against the spreadsheet, and pauses for confirmation before every commit — with the Scripting API left switched off and a full audit trail.
The challenge
Most SAP automation advice assumes a door a well-run Basis team keeps locked. SAP GUI Scripting — the COM interface that VBScript recorders, Winshuttle-style tools, and classic RPA bots attach to — is disabled by default, and security teams keep it off in regulated finance and procurement environments. When the profile parameter sapgui/user_scripting is FALSE, those tools cannot connect at all, so teams fall back to re-keying invoices and master-data changes into SAP by hand.
How Lapu AI solves this
Lapu AI treats the SAP GUI for Windows client as what it is: a standard Windows desktop application. It reads the window through the operating system's UI Automation accessibility tree — the same structured view a screen reader uses — and drives the keyboard and mouse the way a person does. Because it never calls the Scripting API, sapgui/user_scripting can stay FALSE and there is no security popup to suppress. It also drives the legacy Windows apps around SAP that no connector reaches. For the full mechanism and the governance caveats, read SAP GUI automation without scripting.
The agent acts under your own SAP authorizations — it can only do what your user already can. Get security and Basis sign-off before deploying; irreversible steps wait for confirmation and every action is logged locally.
Workflow
How it works
Read the SAP screen through UI Automation
The agent locates the command field, the input fields, the toolbar buttons, and the grid rows by their accessibility labels — no SAP-side API and no scripting handle.
Enter the transaction and navigate
It types the transaction code into the command field, presses Enter, and tabs between input fields exactly as a keyboard user would. Real keystrokes, no COM calls.
Reconcile against your source of truth
For posting from a spreadsheet, the agent reads the Excel file row by row, matches each value into the right SAP field, and checks the confirmation message before moving to the next row.
Ask before it commits, then record the trail
Posting a document, saving a master-data change, or releasing an order waits for your confirmation. Every action — transaction opened, field typed, message returned — is written to a local audit log you can review afterward.
Under the hood — for the technically curious
The mechanism is the computer-use pattern: read the SAP window through UI Automation to locate the command field, toolbar buttons, and grid cells by their labels, then send real keystrokes and clicks. From the SAP application server's point of view the input is indistinguishable from a person typing, so no S_SCR grant or scripting flag is required. Sensitive steps run under a permissioned-execution model and every action lands in a local audit trail. Honest limits: this is not an SAP-certified integration and is not tested against any specific SAP release; SAP Fiori and the Web GUI are a different browser surface; and genuinely high-volume unattended posting still favours deterministic, purpose-built tooling.
Permissions it asks for
- Screen Read — to read the SAP GUI window through the OS accessibility layer
- Keyboard Input — to enter transaction codes and field values (requires permission for commits)
- File Read — to reconcile against spreadsheets and source files
- Audit Log — to record every action locally for review
Each is permission-gated — Lapu AI asks before it runs.
Just ask
Say it in plain words
No commands to learn. Tell Lapu AI what you want the way you would tell a coworker.
You
Open XK02, update the payment terms for vendor 100045 to NT30, and stop for my confirmation before saving.
You
Post the invoices in ~/finance/sap-batch-may.xlsx into FB60 one row at a time, checking the confirmation message after each, and flag any row SAP rejects.
You
Read the vendor master screen for 100045 and tell me the current bank details and payment terms — do not change anything.
Ready to try this workflow?
Download Lapu AI and run it on your own machine. Free to start — see exactly what it looks like first.
- 1-click uninstall
- Cancel anytime
- Files never leave your computer
FAQ
Common questions
Does this need SAP GUI Scripting turned on?
No — that is the entire point. The Scripting API and the profile parameter sapgui/user_scripting govern the COM scripting channel. Lapu AI does not use that channel; it reads the rendered SAP GUI for Windows window through the OS accessibility tree and sends real keyboard and mouse input. From SAP's perspective the input is indistinguishable from a person typing, so no server-side or client-side scripting flag has to change.
Is it safe to let an agent operate SAP under my login?
The agent acts under your own SAP authorizations, so it can only do what your user is already allowed to do — but governance still matters. Low-risk steps like reading a screen run quietly; sensitive steps like posting a document or saving a master-data change wait for explicit confirmation, and every action lands in a local audit log. Get security and Basis sign-off before deploying, and treat it like any other privileged access to production SAP.
Is Lapu AI an SAP-certified integration?
No. Lapu AI is a general desktop AI agent for macOS and Windows; it drives the SAP GUI for Windows window as a standard Windows application through the OS accessibility layer. It is not SAP-certified and is not tested or warranted against any specific SAP release, S/4HANA or ECC version, or support-package level. Validate it in a non-production client, involve Basis and security, and confirm it fits your change-control requirements first.
Will this work with SAP Fiori or the Web GUI?
Not through the same path. SAP Fiori and the Web GUI are browser-based surfaces, not the SAP GUI for Windows desktop client, so they render as web pages rather than native Windows controls. A desktop agent can still drive a browser, but the technique and reliability characteristics differ. This use case is specifically about the classic GUI for Windows client — the surface where disabled Scripting most often blocks automation.
Explore more
Related use cases
Desktop Automation
Stop copy-pasting between apps. The agent sees your screen, clicks buttons, fills forms, and moves data between applications — so you do not have to.
See how it worksDataData Processing
Describe the transformation you need in plain English. The agent writes and runs the Python script, shell pipeline, or Node job — you just approve and get clean output.
See how it worksAutomationCross-App Workflows
One prompt, multiple apps. The agent reads a spreadsheet, runs a script, pastes results into a presentation, and logs the outcome — all in a single workflow.
See how it works