ElectroNeek

Use case · Systems without an API

An SAP GUI report in Google Sheets or Power BI every morning — without an SAP project

A Studio bot logs into SAP GUI on a Bot Runner, runs the transaction with your variant (FBL5N, MB52, VA05, ZREPORT), exports to a file, and hands it to a workflow. The workflow normalizes the columns, appends or replaces the data in Google Sheets, Excel 365 or a Power BI dataset, and an agent writes a three-line summary of what changed to Slack or Teams. Nobody logs into SAP for the morning number.

Request a sandbox with this processBook a demo
Who it is for
Operations, finance and sales teams on SAP ECC or S/4HANA whose daily numbers live in a GUI transaction someone runs and pastes into a sheet — and whose IT team has no bandwidth for an integration project.
Systems involved
SAP GUI (Studio bot)Google Sheets / Excel 365 / Power BISlack / TeamsAI Workflows

How the run goes

5 steps · logged per run

  1. Trigger01

    06:30 daily

    Or on request from Slack

  2. Bot02

    Run SAP transaction

    GUI scripting or UI; variant and selection

  3. System03

    Export to file

    XLSX / CSV from the GUI

  4. Agent04

    Normalize and summarize

    Columns, deltas, three-line note

  5. System05

    Load and notify

    Sheets / Excel 365 / Power BI; Slack / Teams

Agent decidesDocument becomes fieldsBot does the clicksPerson approves

How it runs, step by step

  1. 1

    A schedule triggers the run (or a Slack command does, for "give me the open items now"). The workflow calls the bot on the Bot Runner, a Windows machine with SAP GUI installed — often the same VM the analyst used.

  2. 2

    The bot logs in with its own SAP user, runs the transaction with the stored variant, applies selection parameters the workflow passed (company code, date range), and exports the list to XLSX or CSV. Where SAP GUI scripting is enabled the bot uses it; where it isn't, it drives the UI.

  3. 3

    The workflow reads the file, maps SAP's column headers to yours, converts the number formats, and appends to or replaces the target: a Google Sheet, an Excel 365 table in SharePoint, or a Power BI push dataset.

  4. 4

    An agent compares today's figures with yesterday's and writes a short, factual summary — total overdue, biggest movers, anything above a threshold — to the team channel with a link to the sheet.

  5. 5

    If the transaction fails (locked user, changed screen, SAP down), the bot captures the screen and the workflow posts a failure with the screenshot instead of silently skipping the day.

Limits — what this does not do

  • Bots run on Windows; a Linux-only estate needs a Windows VM for the runner.
  • SAP GUI scripting must be enabled on the client for the fastest path; the UI-driven path works without it but is slower.
  • This is an export use case; writing data into SAP by bot is a separate, reviewed build.

Questions about this process

  • There are BAPIs, OData services and third-party connectors; they need an SAP project, Basis time and authorizations. The bot uses the transaction and the user the analyst already has, which is why it is live in days.

  • With SAP GUI for Windows, yes, for ECC and S/4HANA. Fiori apps are automated as web applications.

  • The bot is deterministic: it stops at the first changed element and reports. The fix is a selector update in Studio, retested on the next run.

Related use cases

Systems without an API

AS/400 green-screen inquiries answered in Teams or Slack

Systems without an API

A web portal without an API, scraped to Sheets on a schedule — with change alerts

Systems without an API

Data entry into a Citrix-hosted application from a SharePoint list

Build this on your systems in a guided sandbox.

Tell us the process; after a 30-minute call the sandbox is ready from 24 hours, and we build the first run with your team.

Request a sandboxHow pricing works