The New Concept of ERP Freedom: The Autonomous Enterprise
As AI (artificial intelligence) agents become more involved in ERP (enterprise resource planning), companies are facing a new challenge: how do you give AI enough freedom to act while still maintaining control over critical business processes? In his September 2026 post, E3 Magazine’s Publisher and Editor-in-Chief Peter M. Färbinger examines SAP’s vision of the “Autonomous Enterprise” and questions whether today’s ERP environments are ready for truly autonomous AI. Färbinger’s main concern is the difference between ERP’s deterministic nature and AI’s probabilistic nature. Traditional ERP systems are designed to produce predictable results, while AI can generate different answers based on probabilities. Giving AI agents the ability to execute transactions or make operational decisions therefore introduces new risks if their actions aren’t properly controlled.
There’s another problem: the ERP environment itself may not be ready for autonomy. Many SAP customers have decades of customizations, fragmented systems and inconsistent master data. Färbinger argues that putting autonomous AI on top of that complexity could simply make existing problems happen faster. The article also raises concerns about vendor dependence, AI costs, licensing and governance. Färbinger questions whether companies could become too dependent on external AI models and SAP’s infrastructure, while unpredictable AI usage could create unexpected costs. He also points to the need for human oversight and clear accountability when AI agents are making decisions. His proposed answer is greater digital sovereignty: maintaining control over data and business processes through more modular, vendor-neutral architectures. The takeaway is that autonomous ERP may offer significant possibilities, but AI readiness starts with the underlying ERP environment, data and governance—not simply adding AI agents to the system.
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.



