// DEEP DIVE | LEGACY INTEGRATION
SAP Automation and AI Integration: The Side-by-Side Approach
SAP AI integration works without touching the standard. Instead of Z-code, modifications, or customizing, the AI logic runs outside the SAP core and orchestrates processes through documented interfaces: BAPIs, IDocs, OData. The core stays clean, the extension happens side-by-side. Upgrade capability and vendor support remain fully intact.
THE PROBLEM
SAP is powerful, but rigid
Anyone running SAP knows the tension: the system is the backbone of operations, but every adaptation takes time, costs money, and risks shooting itself in the foot at the next upgrade. Z-code destroys standards. Every modification either gets overwritten by the next patch or blocks it entirely.
At the same time, manual processes drag operations down because the SAP standard cannot cover them: orders from PDFs get typed in by hand, invoices get reviewed manually, master data gets synced between systems. Classic AI providers often recommend solving the problem with SAP BTP or a full S/4HANA migration. That means years and millions.
The pragmatic answer is different: AI does not live inside SAP. It sits in front of it and behind it. Through official interfaces, processes are orchestrated without anyone reaching into the core.
BAPIs, IDocs, and OData: we speak SAP
Depending on your SAP version we take the right door. For R/3 and ECC we use RFC, IDoc, and BAPI. For S/4HANA we go through OData, REST APIs, and SAP-certified BTP integrations. Important: we do not simulate user input (no pure screen scraping) and we do not write blindly into the database. We post on the business object level using the methods SAP itself documents. That is the difference between hacking and integration.
Four use cases we automate in production
/ OUR APPROACH
01
Step 01
SD - Sales Order Entry (VA01)
PDF order comes in by email, the Xanevo AI extracts position, quantity, and delivery date, matches the customer against the SAP customer master, and creates the order via BAPI_SALESORDER_CREATEFromDAT2. The document number is returned. Zero typos, on average 70 % less processing time per order.
02
Step 02
MM - Invoice Verification (MIRO)
Automatic 3-way match between purchase order, goods receipt, and invoice. If everything aligns, the system posts via MIRO unattended. If there are deviations, accounting receives a structured proposal with reasoning instead of a raw alert list. Finance gains time, not risk.
03
Step 03
Master Data - Material Master Creation
New articles arrive from supplier feeds, PIM systems, or catalogs. The AI extracts material attributes, enriches them, and creates the material master in SAP (BAPI_MATERIAL_SAVEDATA). Classification by ECLASS or ETIM happens automatically. What used to take hours of manual maintenance per article now runs through the pipeline.
04
Step 04
Authorization Concept and Security
We work with a dedicated technical user who has only the permissions needed for the defined use cases. No SAP_ALL, no modifications to the role concept. Every transaction is auditable with document number, user ID, and timestamp.
Clean core without Z-code
SAP has been recommending the clean core strategy for years: no custom modifications to the standard, all extensions side-by-side. That is exactly what we do. The SAP core stays in delivered state, AI logic runs on the Xanevo platform and communicates through standard interfaces. When SAP releases an update, we do not have to check whether our modifications survive. They survive because there are none.
70 %
less processing time per automated SAP order
Measured at a mid-market B2B distributor that previously entered orders manually in VA01. After the Xanevo bridge went live, 85 % of orders run unattended. Only edge cases land on the sales rep's desk.
Which SAP version do we support?
System
Integration method
Status
SAP R/3 (4.6c bis ECC 6.0)
RFC, BAPI, IDoc
Fully supported
SAP S/4HANA (On-Premise)
OData, CDS Views
Fully supported
SAP S/4HANA (Cloud, Public Edition)
Whitelisted APIs
Fully supported
SAP Business One / ByDesign
SOAP, REST
On request
Three questions SAP owners ask
No. The Xanevo bridge runs standalone but can be connected to BTP if you already run it in production. For companies without a BTP investment, this is not a blocker.
Because we use only documented standard interfaces (BAPIs, IDocs, OData), SAP updates are typically uneventful. For major version jumps (such as ECC to S/4HANA) we adjust the connector layer. The AI module and workflow logic stay untouched.
Minimal. We need a technical user with defined permissions and a firewall opening for our connector component. Both can usually be arranged with your internal SAP Competence Center. External consultants are only required for special constellations.
Related deep dives
AS/400 and Mainframe
Modernization for IBM i systems via terminal emulation and validated write paths.
// SAP INTEGRATION
Let's review your
SAP setup.
Which SAP version are you on, which modules are in use, which processes would you automate? We review your version, release level, and authorization design and give you a clear yes or no on feasibility. One hour, no sales pitch.