# Forager: AI agent for SAP GUI

> Forager is an AI agent that uses SAP GUI for Windows like a person: it answers questions, performs transactions on screen, and (soon) turns recurring SAP work into workflows it runs by itself. It runs on a local LLM (Ollama), so SAP data stays inside the company. No OData, BAPI, BTP or integration project is needed. Made by BuzzSpire (https://buzzspire.net), founded by Mert Türkoğlu (https://www.mertturkoglu.com).

Website: https://forager.buzzspire.net (Turkish) · Demo requests: hello@buzzspire.net

## Who it is for

Companies running SAP ECC or S/4HANA with SAP GUI for Windows, where people spend time finding the right transaction code, table or report: finance, sales, purchasing, warehouse and IT/basis teams. In Turkish it is described as "SAP'deki işi ona bırakın" (leave the SAP work to it).

## Three levels

1. Ask (available): "Last month's invoices", "how many active users are there", "which transaction is the stock report". Forager finds the right screen and table and answers with a summary, a table and a chart. Results download to Excel in one click.
2. Do (available): performs transactions such as creating a sales order on SAP GUI screens, step by step, like a user. It asks for missing details and previews the change; nothing is saved until the user approves.
3. Automate (coming soon): describe a job you do often once and it becomes a workflow. Forager runs it at a set time or when an event happens and only calls the user when a decision is needed. Example: every Monday 08:00, overdue receivables → report.

## How it works

- Chat (web): the user asks in everyday language. No need to know technical terms, table names or transaction codes. If something is missing the agent asks one short question.
- Agent (local LLM): knows every transaction code of the system, including company-specific Z codes, and decides which screen or table is needed.
- SAP GUI (scripting): opens screens, fills fields and reads lists. SAP's authorization checks apply at every step.

Data queries use SE16N on the user's behalf: exact counts (without loading rows), filters including "not equal", sorting by the newest records, grouping and totals, and charts.

## Example (real conversation from an SAP IDES test system)

User: "Son faturaları getir" (get the latest invoices)
1. Tool `son_faturalar` (last 30 days) → no invoices; the agent says so.
2. Tool `son_faturalar` (wider range) → 64 billing documents from table VBRK.
3. Answer: "There are 64 sales invoices; the latest is from 03.04.2018", with the five newest in a table.

User: "Mart 2018 için faturaları müşteriye göre grafikle göster" (March 2018 invoices by customer, as a chart)
1. Tool `tablo_sorgula` on VBRK, FKDAT 01.03.2018–31.03.2018, grouped by customer (KUNAG), summing NETWR.
2. Tool `grafik_ciz` → bar chart of the totals per customer, then a summary table.

## Features

- Finds the transaction code by itself: catalogs all transaction codes of each connected system, Z/Y codes first.
- Like a normal user: no OData, RFC or BTP. Any screen reachable in SAP GUI can be used.
- Table, chart, Excel: results come as tables; ask for a distribution and a chart is drawn.
- Multiple systems: switch between development, test and production in one click; the active system is always shown.
- No made-up values: never invents document or customer numbers; only uses values given by the user or returned by SAP.
- Approval before saving: persistent actions such as creating an order are previewed first.

## Security

- Local model: the LLM runs on the company's own server; SAP data is not sent to any cloud service.
- Read-only in production: saving and change transactions are blocked in code on production systems.
- The user's own permissions: Forager works with the user's SAP user and cannot see anything the user cannot.
- Audit log: every action the agent takes in SAP is recorded with time, system and user.

## FAQ

Q: Does it need OData, BAPI or BTP?
A: No. Forager works through SAP GUI for Windows. No new server-side service or integration project is needed.

Q: What must be configured on the server?
A: Only SAP GUI Scripting must be enabled: in transaction RZ11, sapgui/user_scripting = TRUE.

Q: Can it use our company-specific Z screens?
A: Yes. It catalogs each system's transaction codes, including Z/Y codes, and considers them first when searching.

Q: Which AI model does it use?
A: Open models running locally through Ollama. The default model is small enough for a single workstation GPU.

Q: Can it accidentally change something in production?
A: Production systems are read-only: saving and change transactions are blocked in code, not left to the model. On test systems every persistent action waits for approval.

Q: Which languages does it support?
A: The interface and chat are Turkish. Transaction search uses SAP's Turkish and English texts.

## About

Forager is built by BuzzSpire, the studio founded by Mert Türkoğlu (https://www.mertturkoglu.com). Other BuzzSpire products: Waggle (https://waggle.buzzspire.net), a hand-drawn whiteboard for teams, and Nexar (https://nexar.buzzspire.net), a fluent HTTP client for .NET.