An AI Agent That Calls Live SAP Data — and Fixes It in ABAP
· 8 min read
← Part 1: Your SAP Data Is Already Real-Time
In Part 1, a mid-size manufacturer's forecasting team got a live, validated, DuckDB-native view of their SAP order and customer data — fresh within five minutes, anomalies caught at the gate, no warehouse in the middle.
This post is Part 2. It answers the next two questions: how does the AI agent actually reach that data, and what happens when the data is wrong?
The short version: we publish the view as a REST endpoint and an MCP tool with flAPI so the agent can call it, and when the agent finds a bad number it reads the ABAP behind the view, writes a patch, and files a transport with erpl-adt.