SAP Logistics Copilot
Paste an SAP export. Get the root cause in seconds.
Diagnostic skills for SAP logistics power users, key users, and process owners. The IDoc skill is live today; four more are planned. The free version runs in Claude Code with Anthropic's cloud model — try it on sample or redacted data. In production, aplexio deploys the Copilot into your cloud tenant or on-prem environment, on open-weight models under your control; aplexio never sees the data.
One live, four planned
What each skill resolves.
Available now
1. IDoc errors
Paste a failed IDoc from WE02 or WE05. Returns the concrete root cause — missing prerequisite MATMAS, wrong partner function, status-handler misrouting — and the exact fix.
Planned
2. Delivery blocks
Paste a delivery-block list export. Returns a prioritised remediation order: credit-release candidates first, then material availability, then picking-complete dependencies.
Planned
3. Stock discrepancies
Paste an MMBE or LX03 discrepancy report. Returns the likely movement-type error, the posting that needs reversal, and the reconciliation steps.
Planned
4. Freight-cost variances
Paste a TM freight-cost export. Returns the variance driver — rate-table mismatch, route determination, volume-weight conversion — and whether it's carrier-billable.
Planned
5. Open-invoice issues
Paste an open-invoice aging report. Returns which invoices are stuck on posting errors vs. credit memos vs. pricing disputes, and the next action per bucket.
Every skill in this pack answers in the same format: a one-line summary, a per-item analysis with cause and recommended action, then three to five next steps — each naming the concrete transaction, e.g. WE20 or VKM1. Learn the shape once, recognize it everywhere.
Today the Copilot works on the export you paste — a live connection to your SAP system is in development. Why the skills are built narrow, and what the agent projects that reach production have in common, is in the blog: Exception-shaped agents →
SAP Joule
Joule Work is rolling out. The Copilot runs on the SAP you have.
SAP began phased general availability of Joule Work and Joule Studio in October 2026 (SAP). The native path remains SAP's cloud portfolio. Selected AI scenarios for ECC and on-premise S/4HANA carry a separate condition: a commitment to transition most of the landscape to SAP Cloud ERP. If that is not your path, the SAP Logistics Copilot offers bounded diagnosis on the exports you already use — without waiting for a cloud programme. Our SAP AI update explains the new rollout and its limits →
If you do run Joule, we don't replace it. SAP now describes governed third-party agent access through A2A and MCP (SAP Architecture Center); the right integration depends on your estate and licences. Our Copilots remain available for narrowly scoped work that must stay on your own infrastructure, with no aplexio backend in the loop.
Private AI
Deployed by aplexio. Runs on your infrastructure.
aplexio deploys the Copilot into your cloud tenant or on-prem environment. Open-weight models (Llama, Qwen, DeepSeek) run under your control — no phone-home, no telemetry, no vendor lock-in. aplexio never receives the SAP data, never stores it, never trains a model on it.
# Input — inbound IDoc 0000004711 · DESADV / DELVRY07 · status 51 E1EDL20 VBELN 180000123 E1EDL24 MATNR MAT-100 WERKS 1000 Status text: material MAT-100 not maintained in plant 1000 # Copilot output Root cause: The material in segment E1EDL24 is not maintained for the receiving plant 1000. The MATMAS IDoc that extends it had not been posted when this IDoc arrived. Fix: Post the pending MATMAS IDoc (or extend the material to the plant), then reprocess this IDoc in BD87.
Test it on a redacted export from your system.
Try the free version on sample or redacted data first; for production we install the Copilot in your environment. You see the output before we see a contract.