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.
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.
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.
- 01You
You ask.
Describe what you need in plain words: a new setting, a fix, a development or a test.
- 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.
- 03You
You decide.
Adjust the plan, ask questions, approve it or drop it. Nothing happens until you say so.
- 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.
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.
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.
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.
How it works
Behind the scenes, the connector keeps the assistant inside the rules your company sets.
- 01Your choice
Your AI assistant
You sign in with your usual company account.
- 02Hosted
XM Connector
The connector checks your role, your licence and your company's limits.
- 03Your landscape
Your SAP Cloud Connector
The request reaches SAP through your own Cloud Connector, as your SAP user.
- 04Your landscape
Your SAP system
The result comes back to your assistant, and nothing from SAP is stored.
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