AI for SAP ECC and On-Premise S/4HANA. No RISE. No BTP. No Waiting.
The SAP Data Problem
Your business runs on SAP. But to access your own data, you need to:
Learn table names (EKKO, BSIK, LFA1…)
Know which fields to join
Wait 3 days for IT to run a report
Export to Excel and VLOOKUP everything
Just Ask
| Vendor | Name | City | Invoice | Amount | Due Date |
|---|---|---|---|---|---|
| 1000001 | Acme Corporation | Madrid | 5100000234 | €78,500.00 | 2025-01-20 |
| 1000015 | Beta Industries | Barcelona | 5100000301 | €125,000.00 | 2025-01-25 |
| 1000023 | Global Supplies | Valencia | 5100000412 | €52,300.00 | 2025-02-01 |
Every query runs under the user’s own SAP authorizations. If you can’t see it in SAPGUI, you can’t see it through ABAPilot.
SAP said ECC customers should wait. You don’t have to.
At Sapphire 2026, SAP announced that Joule AI agents would finally reach ECC and on-premise S/4HANA — but only for customers who commit the majority of their landscape to RISE with SAP and purchase the Max Success Plan. SAP’s own ABAP MCP Server now ships inside ADT — Eclipse and VS Code — as a developer tool whose capabilities depend on the ADT services your system exposes; it offers no business-user query layer.
If you run ECC or on-premise S/4HANA and don’t plan to sign a cloud commitment to get AI, ABAPilot exists for you. It’s a pure-ABAP add-on in a customer-owned namespace, plus an MCP server that connects your system to the AI model of your choice — today, on the system you already have.
Why ABAPilot
Deploy in 2 Hours
Single SICF node and handler class. No Gateway, no BTP, no ADT, no RISE. Works on any ABAP-based SAP system — ECC 6.0, S/4HANA, and beyond.
Natural Language Queries
Ask questions in plain English or Spanish. ABAPilot understands your SAP table structures and joins them automatically.
Works Where SAP's AI Doesn't
No RISE commitment. No Max Success Plan. No cloud migration prerequisite. ABAPilot is built for the systems SAP’s AI roadmap leaves behind.
Bring Your Own Key
True MCP Server
Zero Additional SAP Licensing
What Can You Ask?
Finance
-
“What’s our open AP by company code?” -
“Show me invoices pending approval over €25,000” -
“Which vendors have we paid twice for the same invoice?”
Purchasing
-
“Show me POs without goods receipt” -
“Purchase orders created on weekends” -
“Contracts expiring in the next 30 days”
Audit & Compliance
-
“Who changed vendor bank details in the last 6 months?” -
“Show me all master data changes by user X” -
“Failed background jobs this week”
Developer & Implementation Tools
AI Code Review
Auto-Documentation
Agent-Driven Development
Multi-agent workflow to create ABAP reports: planning, design, implementation, review, and deployment.
Code Generation
How It Compares
| Feature | ABAPilot | SAP Joule / ABAP MCP Server | SAP Gateway/OData | SAP BTP |
|---|---|---|---|---|
| ECC 6.0 Support | ✓ Full | Conditional — requires RISE commitment | Requires add-on | Limited |
| Prerequisites | ABAP transport + MCP server | RISE with SAP + Max Success Plan | Gateway license | BTP subscription |
| Setup Time | 2 hours | Migration-dependent | Days to weeks | Weeks to months |
| Data Stays On-Premise | ✓ Yes (local model option) | Cloud-connected | ✓ Yes | Cloud required |
| AI Model Choice (BYOK) | ✓ Claude, OpenAI, Gemini, Bedrock, Ollama | SAP-managed only | Not available | Via AI Core |
| Dynamic Queries | Any WHERE clause | Pre-defined agent scenarios | Pre-defined only | Pre-defined only |
| ABAP Dev Tooling for ECC | ✓ Built-in | Via ADT only (Eclipse / VS Code) | — | — |
Enterprise-Grade Security
SAP Authorizations, Always
Every query executes with the SAP user’s own permissions — S_TABU_DIS, S_DEVELOP and the rest are enforced by the standard authorization model, not reimplemented.
Full Audit Trail
Every request is logged to /ABAPILOT/AUDIT with user, timestamp, and parameters. Complete visibility for compliance and internal audit.
Endpoint Whitelist
The /ABAPILOT/CONFIG whitelist table defines exactly which operations are exposed. Nothing outside the whitelist is reachable — a hard security boundary you control in your own system.
Read-Only by Default, Local by Choice
Queries are read-only unless explicitly configured otherwise. Run the AI model locally on your network for zero-data-retention deployments.
ABAPilot runs as in-system ABAP in a customer-owned namespace — aligned with SAP’s API policy, not working around it.
Frequently Asked Questions
Does ABAPilot work on SAP ECC 6.0?
Yes. ABAPilot runs on any ABAP-based SAP instance — ECC 6.0 and above, on-premise S/4HANA, and other NetWeaver-based systems — with no BTP, Gateway, or ADT dependency.
Is ABAPilot an MCP server?
Yes. ABAPilot includes a Model Context Protocol server that connects your SAP system to Claude, ChatGPT, or any MCP-capable client, backed by ABAP components inside your system.
Do I need RISE with SAP or the Max Success Plan to use ABAPilot?
No. ABAPilot has no cloud commitment prerequisites. It installs as an ABAP transport plus a local MCP server.
Which AI models can I use?
Any: Claude, OpenAI, Gemini, Amazon Bedrock via your own API keys, or fully local models via Ollama.
Does my SAP data leave my network?
Only if you choose a cloud AI provider — and then only the query context you allow. With local models, nothing leaves your network.
How is access controlled?
Standard SAP authorizations apply to every query, an endpoint whitelist limits what’s exposed, and every request is written to an audit log.