PLATFORM / HOW IT WORKS

From your question to an SAP result,
within your authorizations

You ask in Claude Code, Codex, SAP Fiori, SAP GUI or Flow Builder. NeKu AI picks the right SAP tool, runs it with your SAP authorizations and returns a table, a summary or a change that waits for your approval.

Request a demo ↗
NEKU AI / 2026ACTIVE
AI / SAP
  1. 01ASK
  2. 02RUN
  3. 03VERIFY

01 / FLOW

How a question becomes an SAP answer

01

Ask in the tool you already use

Ask from the Claude Code or Codex terminal, the app.neku.ai chat, the chatbot inside SAP Fiori and SAP GUI, or a Flow Builder agent. Write the question the way you would ask a colleague.

02

The agent calls the right SAP tool with your authorizations

It uses SAP Data for business data, SAP Actions for ABAP, transports, dumps and jobs, and SAP Docs for documentation and release information. Each call names its target system and runs with your SAP user's authorizations.

03

Review and verify the result

The answer arrives as a table, a summary or a change awaiting approval. Objects it could not access and missing data are stated in the answer, so you can compare the result with the SAP screen.

02 / FOUR SERVERS

Four servers, split by type of work

Reading, querying and changing need different permissions. NeKu AI therefore splits access across four MCP servers, and your organization picks the ones it needs.

SAP DATA

Read-only business data

Reads sales, purchasing, inventory and production data from the OData services your organization exposes. Functions that change data are not exposed.

  • Open sales orders and late purchase orders
  • Inventory by plant
  • Queries run under the user's own SAP identity
SAP ACTIONS

ABAP and system tasks

Works with ABAP objects, transports, dumps, background jobs, authorizations and cross-system comparison.

  • Dump summaries and failed jobs
  • Transport comparison between QAS and PRD
  • Read-only, development or full-control mode
SAP DOCS

SAP documentation with sources

Searches SAP documentation, SAP Community, SAP Discovery Center and ABAP release availability, and cites the source of each answer.

  • How to build RAP and CDS
  • ABAP release checks
  • Read-only
YARGI

Turkish legal research

Runs independently of SAP. Researches court and regulatory decisions with source references.

  • Court of Cassation, Council of State and Constitutional Court decisions
  • KİK, Competition Authority, KVKK, BDDK and GİB sources
  • Read-only

03 / CONTROLS

Four controls on every tool call

Whichever tool you ask from, every call to SAP passes through the same controls.

01

Named SAP systems

DEV, QAS and PRD are defined as separate connections. Every call states which system it targets.

02

SAP identity assigned per user

The SAP connection is assigned to the user. Credentials stay in the connection layer and are never passed to the model or the client.

03

Access mode

Read-only, development or full-control mode determines which tasks SAP Actions can run. SAP Data only reads in every mode.

04

Audit and masking

Tool calls can be audited. Sensitive fields and technical secrets can be masked in the output.

04 / WHERE TO USE IT

The same SAP access, where your teams already work

MCP

Claude Code and Codex

Once your organization approves access, both clients connect to the same SAP MCP servers with the same boundaries.

APP

app.neku.ai

Ready SAP workflows and Digital SAP Consultant run in the NeKu AI chat.

SAP

SAP Fiori and SAP GUI

The NeKu AI workflow you choose opens as a chatbot inside the SAP screen, so users ask without leaving it.

AGT

Flow Builder

Build custom agents that combine SAP data, models and approval steps.

05 / GETTING STARTED

Start with one task on a test system

The first evaluation runs on a test system with a single task that does not change SAP data. Once the result holds up, you widen the scope step by step.

01

Choose the task and the system

Pick one read task, such as explaining an ABAP object or listing open orders, and one test system.

02

Define the user and the access mode

Decide with your SAP and NeKu AI owners which SAP user and which access mode the task will use.

03

Verify the result and the boundary

Compare the answer with the SAP screen. Then request an object the user is not authorized for and confirm that the system refuses it.

06 / FREQUENTLY ASKED QUESTIONS

Short answers about the SAP connection

01Can the agent see SAP data that I cannot?

No. SAP authorizations apply to every call. SAP Data queries run under the calling user's own SAP identity, so the agent cannot return a record you are not authorized to see in SAP.

02Can NeKu AI change data in SAP?

SAP Data only reads. Changes through SAP Actions are possible only in an access mode that allows changes and only within the connected user's SAP authorizations.

03Are SAP credentials sent to the AI model?

No. SAP credentials are kept in the connection layer and are never passed to the model response or the client.

04Can it connect to more than one SAP system?

Yes. Systems such as DEV, QAS and PRD are defined as named connections, and every tool call selects its target system explicitly.

05Which SAP releases are supported?

SAP ECC EHP8, SAP S/4HANA 1809 and SAP S/4HANA 2023 are supported connection targets.

06Does it work with Claude.ai or ChatGPT?

Hosted connectors inside Claude.ai and ChatGPT are not supported at the moment. Claude Code and Codex are the supported SAP MCP clients.

07Can NeKu AI run in the cloud and on-premise?

Yes. You can choose a managed cloud service or an on-premise deployment; the MCP layer sits inside the deployment model you choose.

LET'S DESIGN YOUR PROCESSES TOGETHER

Make your enterprise workflows autonomous.

Request a demo ↗
NEKU/SEARCH

Search the NeKu AI knowledge network