XM Connector for SAP S/4HANA
You decide what changes in SAP. Your AI assistant does the work.
The XM Connector for SAP S/4HANA connects your AI assistant (Claude, Microsoft Copilot and others) to your SAP development systems, so it can do the work itself. It researches your system and proposes a plan; you review it, adjust it and approve it; then it carries the plan out: configuration applied, code built and checked, processes tested end to end, with a report of what it did. Every action runs as the person's own SAP user, inside limits your company sets, and every call is recorded.
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
- Reading credit management for sales area 1710/10/00check runs when the order is saved
- Reading delivery type LFcredit group for deliveries: not set
- Following delivery creation through the codeno credit check without a credit group · no custom logic
- Checking last month's deliveries37 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.
Request: Block outbound deliveries without a carrier: add a check in the BAdI.
Worked in S4D · 4 steps
- Reading BAdI LE_SHP_DELIVERY_PROCDELIVERY_FINAL_CHECK can stop the save via CT_FINCHDEL
- Checking existing implementations1 active, method unused · plan: a separate one
- Preparing the design for package ZSD_SHIPPINGimplementation ZEI_LE_CARRIER_CHECK · class ZCL_LE_CARRIER_CHECK · approved package
- Checking the planned code with a syntax checkpassed · no errors, no warnings
PlanBAdI implementation ZEI_LE_CARRIER_CHECK for LE_SHP_DELIVERY_PROC, method DELIVERY_FINAL_CHECK, on your transport S4DK900412.
LOOP AT it_xlikp INTO DATA(ls_likp).
CHECK ls_likp-vbtyp = 'J'. " outbound only
IF NOT line_exists( it_xvbpa[ vbeln = ls_likp-vbeln
parvw = 'SP' ] ).
APPEND VALUE #( vbeln = ls_likp-vbeln msgty = 'E'
msgid = 'ZSD' msgno = '042' ) TO ct_finchdel.
ENDIF.
ENDLOOP.EffectAn outbound delivery without a carrier (partner function SP) gets error ZSD 042 and cannot be saved.
Request: Set up order type ZEX for express orders, like OR, with its own number range, item categories and copy control to delivery and billing.
Worked in S4D · 4 steps
- Reading order type OR and its item category assignmentsOR · 9 item categories
- Reading copy control OR → LF and OR → F22 headers · 14 item entries
- Preparing one plan with before and after values41 changes across 9 tables · 0 changes to SAP standard
- Checking the plan with SAP's own checksno errors
PlanOrder type ZEX as a copy of OR, with number range 22. Item category assignments for ZEX (9). Copy control ZEX → LF and ZEX → F2 (16 entries). ZEX allowed in sales area 1710/10/00.
Instead ofDozens of SPRO screens and copy-control entries by hand: one plan you review, applied automatically after your approval.
SafeNo SAP standard entries change. If any step fails, everything is put back automatically, and the previous state can be restored later.
Request: Analyze this morning's short dump in delivery creation.
Worked in S4D · 4 steps
- Reading today's short dumpsGETWA_NOT_ASSIGNED · 07:42 · job SD_VL10_DAILY
- Following the call stack from SAPMV50AUSEREXIT_SAVE_DOCUMENT_PREPARE in MV50AFZ1
- Reading customer include ZSD_DLV_SAVE_CHECK, line 48field symbol <ls_lips> used without a check
- Checking recent changes to the includechanged 3 days ago · transport S4DK900388
Root causeIn customer include ZSD_DLV_SAVE_CHECK, called from USEREXIT_SAVE_DOCUMENT_PREPARE, READ TABLE xlips … ASSIGNING <ls_lips> has no sy-subrc check. When the item is not in the delivery, the field symbol stays unassigned and the save dumps.
Introduced byTransport S4DK900388, imported three days ago.
FixGuard the access, then rerun the delivery job:
READ TABLE xlips ASSIGNING <ls_lips>
WITH KEY posnr = lv_posnr.
IF sy-subrc = 0.
" existing check on <ls_lips>
ENDIF.Request: Run the approved order-to-cash test plan for the new ZEX order type before go-live.
Worked in S4D · 5 steps
- Running your approved test plan: 6 scenariosstandard · rush · partial delivery · free goods · credit hold · return
- Creating 6 sales orders, sales org 1710orders 2001905 to 2001910
- Creating deliveries, picking, posting goods issue5 deliveries · 5 goods issues posted
- Billing and checking prices and tax5 invoices · pricing and tax as expected
- Comparing every result with its expectation5 passed · 1 failed
Result5 of 6 scenarios passed. Partial delivery failed: the second delivery was not created, because copy control ZEX → LF does not allow partial deliveries.
| Scenario | Document | Expected | Actual | Result |
|---|---|---|---|---|
| Standard | 90004512 | Invoiced | Invoiced | PASS |
| Rush | 90004513 | Invoiced | Invoiced | PASS |
| Partial delivery | 80001241 | 2 deliveries | 1 delivery | FAIL |
| Credit hold | 2001909 | Blocked | Blocked | PASS |
NextA one-entry fix is ready as a configuration plan. After your approval, the failed scenario runs again automatically.
What changes for your team
From advice to done, with you in charge of every change.
From advice to done.
A generic assistant hands you instructions and leaves the SPRO screens, the code and the test runs to you. Connected, the assistant does that work for you, and you stay in charge of every change: nothing happens in SAP until you have seen the plan, adjusted it if needed and approved it, and everything it changes can be put back.
Answers from your system, not from guesswork.
The assistant reads your actual code, configuration and data dictionary before it answers, so explanations and fixes match your release and your customizing.
Changes you approve, and can undo.
Configuration changes are prepared for you as one plan with before and after values, then applied automatically once you approve. If any step fails, everything is put back automatically, and you can restore the previous state at any time.
Governed like any SAP user.
Your SAP authorizations decide what each person can do. The connector only narrows them, never widens them, and it never touches production.
How a change happens
You decide. It does the work. You see the result.
- 01You
You ask.
Describe the change, the problem or the test in your own words.
- 02Your AI assistant
It plans.
The assistant reads your system and proposes exactly what it will do: the settings with before and after values, the code, or the test steps with expected results.
- 03You
You decide.
Review the plan, ask for changes, approve it, or drop it.
- 04Your AI assistant
It does the work and reports.
Applied, built or tested automatically, every step checked, with a report of what changed. Changed your mind? It puts things back.
Why it's different
Generic AI guesses. Connected AI looks.
A generic assistant answers from public information, so you end up checking its answer in the system yourself and going round again. Connected to your SAP system, the AI reads what is actually there and follows the logic to a conclusion.
Guesses from public information
- 01You describe your system and ask
- 02A plausible answer from public sources
- 03You check it in the system yourself
- 04It doesn't match your setup
↺ Back to 01, with more context. Again.
Answers from your actual system
- 01You ask
- 02It reads your configuration and ABAP code
- 03It follows the logic to a conclusion
- 04An answer from your system
→ One pass. Usually right the first time.
Through the connector, the AI
- Reads the actual configuration, ABAP code and, where allowed, business data
- Changes configuration (tables, number ranges, BRFplus rows, TM settings) on your own customizing request, after you approve the plan
- Builds ABAP changes after you approve the design, and runs syntax, ATC and ABAP Unit checks
- Restores the previous configuration on request, and verifies each restore
- Diagnoses dumps, logs, traces, authorization problems and change impact
- Records values at chosen lines while you reproduce an issue, for your user only; nothing stops
- Shows what really travels with a transport and where it overlaps with colleagues' open requests
- Follows XpertMinds' way of working: evidence from your system first, then the least change
- Plans a test; after your approval, runs the business process as your own SAP user, checks the results and gives PASS/FAIL with a report for sign-off
How it works
From your assistant to your development system, through your own gateway.
The XM Connector for SAP S/4HANA is hosted. It reaches your SAP system only through your SAP Cloud Connector, so the link is yours to open and close.
- 01Your choice
Your AI assistant
Your team signs in with their usual company account (single sign-on).
- 02Hosted
XM Connector for SAP S/4HANA
The connector checks their role, licence and your company's limits. It records every call and stores no SAP passwords.
- 03Your landscape
Your SAP Cloud Connector
The request reaches your SAP system through your own SAP Cloud Connector, as that person's SAP user. Switch it off at any time.
- 04Your landscape
Your SAP system
S/4HANA and SAP ECC on NetWeaver 7.40 or later, on premise or private cloud. The answer returns to their assistant; the connector keeps no copy of your SAP data.
- Single sign-on with your company account
- Each person works as their own SAP user
- Your SAP authorizations apply
- Development, test and sandbox systems only
- Clients 000 and 066 are never changed
Your AI assistant
Works with the AI assistant your company already uses.
Which assistants, and how they compare for SAP work: see the FAQ.
Why the XM Connector
Your rules, your authorizations, your off switch.
Reading code with an AI assistant is easy. Doing real SAP work with one, safely and as a team, takes more: who acts in SAP, what it may reach and change, who approved it, and what is recorded.
Each person acts as themselves.
SAP sees the real person's own SAP user, with their own authorizations, on every call. No shared logins, no passwords stored anywhere.
Safe by design.
Non-production systems only, approved packages only, and fixed limits no role can lift: no transport releases, no security or Basis changes, no credential tables.
Configuration, automated.
Describe the change; the assistant prepares every table entry as one plan with before and after values, applies it automatically after your approval, and puts everything back if any step fails.
Testing, automated.
Business processes tested end to end: the plan is built and checked in SAP, run automatically after approval, every step verified, and a report ready for sign-off.
A proven way of working.
Evidence from your system first, the least change that solves it, your standards before ours, and approval before any change.
Every call recorded.
An audit log of who did what, kept 90 days, with none of your SAP data in it.
Nothing to install or maintain.
Managed by XpertMinds: updates tested before they reach you, support included, and it works in the browser, on the desktop and on mobile.
Your off switch.
The link runs through your SAP Cloud Connector. Disconnect it there and everything stops at once.
Who it's for
Built for SAP teams.
Consulting firms delivering S/4HANA projects, and client IT teams running their own development and configuration.
Answers from your own system, for the whole team.
Developers, functional analysts and support work with an assistant that reads what is really there.
- DevelopersApprove the design, and the assistant builds the ABAP changes with syntax, ATC and ABAP Unit checks in approved packages, on your own transports. See what really travels before release.
- Functional analystsGet answers from the actual configuration, followed through the code. Approve a configuration plan, and it is applied on your own request.
- SupportTrace dumps to their root cause through logs, traces and recorded runtime values, check change impact and look at real documents where data access is allowed.
Work in client systems, with the client in control.
Your consultants bring the AI into each client's SAP system on the client's terms.
- Client's authorizationsEach consultant works as their own SAP user in the client system.
- Client's access controlThe client decides who has access in its own company sign-in and can switch the link off at its SAP Cloud Connector.
- Client's releaseAnswers are checked against the release and settings of the system you are working in.
S/4HANA and SAP ECC on NetWeaver 7.40 or later, on premise or private cloud.
See it at work
Talk to us about the XM Connector for SAP S/4HANA.
Tell us about your SAP landscape and the assistant you use, and we'll show you the connector at work. Pricing on request.
hello@xmconnector.ai · opens your email app