XM Connectorfor SAP S/4HANA

XM Connector for SAP S/4HANA

SAP work, done by your AI assistant. Approved by you.

The XM Connector lets your AI assistant work directly in your SAP system. It studies your configuration and code, proposes a plan, and once you approve it, carries out the configuration, development or testing itself, then shows you exactly what changed.

Connected · S4D
read-only

Request: Customers on credit hold still get their orders delivered. Why, and what's the least change to stop it?

Worked in S4D · 4 steps

  1. Reading credit management for sales area 1710/10/00
    check runs when the order is saved
  2. Reading delivery type LF
    credit group for deliveries: not set
  3. Following delivery creation through the code
    no credit check without a credit group · no custom logic
  4. Checking last month's deliveries
    37 deliveries to 12 customers over their limit

Why it happensCredit is checked when an order is saved, but delivery type LF has no credit group, so deliveries are never checked. Orders released earlier, or changed after the limit was reached, go straight through.

Least-change solutionAssign the delivery credit group to delivery type LF and activate the check for sales area 1710/10/00. Two settings, no code.

Impact checkedFrom then on, deliveries for customers over their limit are blocked at creation. 4 open deliveries would be blocked today; returns are not affected.

Ready to prepare as a configuration plan for your approval
Illustrative exampleEvery call logged

The difference

Why it's different

It works in your system, not around it.

Most AI assistants can only describe what to do in SAP and leave the screens, the code and the testing to you. Connected through the XM Connector, the assistant does that work itself, in your development system, signed in as you.

It knows your system before it answers.

It reads your actual configuration, code and data dictionary first, so its explanations and fixes fit your release and your customizing rather than a textbook example.

You stay in charge of every change.

Nothing changes until you've seen the plan and approved it. If a step fails, everything is put back automatically, and you can return to the previous state whenever you like.

It respects your SAP security.

Every action runs as the person's own SAP user, with their own authorizations, never in production, and every call is recorded.

Four steps

How a change happens

Every change follows the same four steps, so you always know what the assistant is about to do.

  1. 01You

    You ask.

    Describe what you need in plain words: a new setting, a fix, a development or a test.

  2. 02Your AI assistant

    It plans.

    The assistant studies your system and lays out exactly what it will do: the settings with their before and after values, the code it will write, or the test steps with their expected results.

  3. 03You

    You decide.

    Adjust the plan, ask questions, approve it or drop it. Nothing happens until you say so.

  4. 04Your AI assistant

    It does the work.

    The assistant carries out the plan, checks every step and reports what changed. If you change your mind later, it puts things back.

You ask · It plans · You decide · It does the work

The comparison

Same question. Two very different answers.

Without a connection, an assistant can only guess from public material. With one, it checks your actual system before it answers, and can then do the work.

Without the XM Connector

Guesses from public information

  1. 01You describe your system and ask
  2. 02A plausible answer from public sources
  3. 03You check it in the system yourself
  4. 04It doesn't match your setup

↺ Back to 01, with more context. Again.

With the XM Connector

Answers from your actual system

  1. 01You ask
  2. 02It reads your configuration and ABAP code
  3. 03It follows the logic to a conclusion
  4. 04An answer from your system

→ One pass. Usually right the first time.

Capabilities

What it does for your team

Configure.

Describe the setting you need, and it prepares every table entry as one plan, then applies it once you approve.

Develop.

It designs the class, report or enhancement, waits for your go, then builds and checks it on your own transport.

Test.

It runs a business process end to end, from order to invoice, checks every result against what you expected and hands you a report.

Troubleshoot.

It follows an error through configuration, code and logs to the real cause, and proposes the smallest fix.

Explain.

It answers "how does this work here?" from your own system, not from generic documentation.

Everything it can do →

How it works

Behind the scenes, the connector keeps the assistant inside the rules your company sets.

  1. 01Your choice

    Your AI assistant

    You sign in with your usual company account.

  2. 02Hosted

    XM Connector

    The connector checks your role, your licence and your company's limits.

  3. 03Your landscape

    Your SAP Cloud Connector

    The request reaches SAP through your own Cloud Connector, as your SAP user.

  4. 04Your landscape

    Your SAP system

    The result comes back to your assistant, and nothing from SAP is stored.

Security

Built to pass a security review

Each person works as themselves in SAP, with no shared logins and no stored passwords. The connector works only in non-production systems, never releases transports or touches security settings, and records every call without keeping any of your data.

Who it's for

Built for SAP teams

Consulting firms delivering S/4HANA projects, and client teams who run their own development and configuration. It works with S/4HANA and SAP ECC on NetWeaver 7.40 or later, on premise or in a private cloud, and with the AI assistant your company already uses, such as Claude or Microsoft Copilot.

Talk to us

See what it can do in your system.

We'll walk you through it on a real S/4HANA system and talk about what it would take to connect yours.

contact@xmconnector.ai · Pricing on request