Directly on your real system

The ABAP and Fiori agent that connects directly to your SAP system

MobiusX AI finds the object, reads the source, patches it with a syntax check, activates it and puts it on a transport. It also writes Fiori apps, prepares the OData service and deploys to SAP. Not a chatbot that pastes code; a developer that connects directly to your system.

Workflows

Turn your SAP processes into workflows that run themselves

Build the workflow in the drag-and-drop editor, or describe what you want and let AI build it. When the trigger fires, the workflow does the work in SAP and your other systems for you.

Purchase order approvalActive
  1. ScheduleEvery workday at 08:00
  2. SAP ERPFetches orders awaiting approval
  3. AI AgentFlags the risky ones
  4. TeamsAsks the manager to approve
  5. SAP ERPApproves the order
  • Workflows from one sentence

    Type "Send orders awaiting approval to Teams every morning"; the workflow arrives with its nodes, ready to adjust in the editor.

  • Triggers

    A schedule, webhook, email, Teams, Slack, Telegram or an incoming e-invoice can start a workflow.

  • SAP and beyond

    Connects to SAP via OData and BAPI; works with Teams, Slack, Jira, Outlook, databases, e-invoice providers and SMS services.

  • Approvals and AI Agent

    A workflow can wait for a manager's approval. The AI Agent node reads the data, decides, and calls other tools when needed.

How it works

Three steps, on your own system

  1. 1

    Connect your SAP system

    Your server address, client and SAP user are all it takes. Systems behind the corporate network connect through an enterprise VPN.

  2. 2

    Ask in plain language

    "Find the root cause of this dump", "Clean up the ATC findings in ZMM_*", "Build a Fiori app for purchase order approval".

  3. 3

    The agent does it on your system

    Every step is in the transcript: which object was read, what changed, whether the check passed. Write tools stay off until you turn them on.

Capabilities

Everything you do in Eclipse and the Fiori tools, from chat

Each card maps to a tool that really runs on the system. The agent does not guess code; it reads from the system and writes to the system.

  • Search and read

    Classes, programs, function groups, CDS, tables, behavior definitions. Reads source, structure and where-used lists.

  • Version history

    Reads an object's revision history: which change landed when, and on which request.

  • Create new objects

    Classes, CDS views, behavior definitions, service definitions and bindings, packages. In the customer namespace, on a transport.

  • Transport management

    Lists, creates and releases transports. Never writes to a transportable package without a transport number.

  • ATC and unit tests

    Runs the ATC variant and ABAP Unit tests, then points each finding at the source line.

  • Dump analysis

    Reads the ST22 feed, finds the offending line in the source and explains the root cause.

  • Data queries

    Reads tables and runs Open SQL queries, so it reasons about code and data together.

  • OData publishing

    Publishes or unpublishes a service binding as V2 or V4 and reports its state.

  • Fiori app creation

    Sets up a running SAPUI5 app: manifest, views, controllers and i18n files, wired to an OData service.

  • Fiori app editing

    Pulls the app from SAP into a working copy and shows every change line by line. If someone changed it in SAP meanwhile, it won't overwrite.

  • Deploying Fiori apps to SAP

    Uploads the app to SAP's UI5 repository on a transport and builds the preload file itself. Undeploys when needed.

  • Fiori launchpad and services

    Writes the backend service with RAP or classic Gateway; defines the launchpad catalog, tile and target mapping.

Trust

Why let an agent write to SAP at all?

Because the write path goes through SAP's own rules, and every step is on record.

  • Read-only by default

    A new system opens with read tools only. Write tools are never handed to the model until you enable them.

  • The agent needs a transport too

    Writing to a transportable package requires a transport number in SAP, and that rule applies to the agent. Scratch work stays in $TMP.

  • Checked before saving

    Every patch passes a syntax check first. On any error the object is left untouched.

  • Only your system

    Connections open only to the SAP host you defined; SAP credentials are stored encrypted.

  • Every step visible

    Which object was read, what changed, which test ran: all of it in the transcript, shareable with your team.

In the cloud or on your own infrastructure

Same product, two deployments. The difference is not in features but in where your data lives.

  • Setup

    Cloud: Minutes: sign up and connect

    On-premise: On your server, with Docker

  • SAP access

    Cloud: Direct or via enterprise VPN

    On-premise: Internal network, no egress

  • System definition

    Cloud: Users add their own systems

    On-premise: Basis / IT defines them in the platform console

  • Code and data

    Cloud: Encrypted, in region

    On-premise: Never leaves the company

  • Pricing

    Cloud: Credit-based, monthly or yearly

    On-premise: Annual license

Use cases

What teams hand over in the first week

  • Understanding legacy code

    Have a ten-year-old report explained in minutes, together with the functions it calls.

    What does ZFI_AGING_REPORT do and which tables does it write to?

  • S/4HANA readiness

    Clean up ATC findings package by package; each fix is its own patch with its own check.

    Fix the S4HANA_READINESS findings in package ZSD

  • RAP development

    CDS, behavior definition, service definition and binding: a working OData service from scratch.

    Create a managed RAP object and a V4 service for ZI_SALESORDER

  • Dump root cause

    Finds this morning's dump down to the line, proposes the fix and writes it once you approve.

    Find the source of the CX_SY_ZERODIVIDE dumps from the last 24 hours

  • Documentation

    Reads the source and writes the technical design document; the draft is yours, the code is from the system.

    Write a technical document for ZCL_PRICING_ENGINE

  • Fiori app

    From a request to an app opening in SAP: service, screens, deployment and a launchpad tile.

    Build a Fiori app that lists open purchase orders and lets managers approve them

Our products

Two more products from the MobiusX family

Alongside the SAP agent, we build applications for warehouse operations and master data quality. Both connect to your existing systems through a REST API, webhooks and role-based access.

  • WMS

    WareTwin

    Warehouse management built on a 3D digital twin

    Track racks, pallets, forklifts and docks in a live 3D twin of each warehouse, and create tasks right from the twin.

    • Multi-warehouse map with occupancy, task and alert summaries
    • Status, ABC, ageing, expiry and empty-slot views with slotting suggestions
    • Warehouse designer: draw the plan in 2D, preview in 3D, rack addresses generated automatically
    • Per-product packaging design; loads on the racks are drawn with it
  • MDG

    Tekil

    Master data deduplication and golden records

    Finds duplicate person and organization records across ERP, CRM, e-commerce and the call center, merges them and picks the most trusted value for every attribute.

    • Turkish-aware matching: phonetic keys, name variants, national ID and tax number validation
    • Rule engine with a simulator that measures precision before you publish
    • Explainable machine learning and an AI assistant that justifies its decisions
    • Match queue, reversible merges and data change requests

Frequently asked questions

Which SAP releases does it work with?+

Any ABAP system with SAP's development services enabled: NetWeaver 7.5x, S/4HANA on-premise and BTP ABAP Environment. If you can connect to it from Eclipse, so can MobiusX AI.

What do I need to install on the SAP side?+

Nothing. SAP's development services just need to be active. Your existing authorization model applies unchanged.

What do Fiori apps need?+

No extra tooling; the app is deployed to SAP's own UI5 repository. If your front-end server (Fiori hub) is separate, you connect it as a second system. Registering the service on the front end and role authorizations stay with your team as usual.

What can the agent write, and when?+

Only on systems where you enabled write mode, only in the customer namespace, and in transportable packages only with a transport. Every patch passes a syntax check first.

My SAP system is behind the corporate network. How does it connect?+

In the cloud edition you can connect through an enterprise VPN tunnel. If nothing may leave your network, the on-premise edition runs on your own server.

How does my code reach the model?+

The agent reads only the source of the relevant object and sends it to the model to produce the answer. Source code is never used for training. In the on-premise edition you choose the model endpoint yourself.

How are credits spent?+

Each message consumes credits in proportion to the source read and the answer produced; a measured average task is 2 to 3 credits. Keeping a system connected or reading transcripts costs nothing.

Connect your first system today

Start in read-only mode, watch how the agent reads your code, and enable writing when you are ready.