It is commonly believed that SAP modules are static elements that take years to implement. But while the market was living with this stereotype, a quiet revolution took place within the system.
The system architecture has changed and the term has taken on a life of its own: it is no longer tied to its ‘German parent,’ and the very concept of SAP has scaled up. Today, it is no longer a monolithic ERP element, but an independent service and a global synonym for corporate standards. It is flexible, cloud-based, intelligent, and integrable with business processes and data through APIs, microservices, and AI agents.
If you still perceive this system as just software, you are missing the essence of its evolution. Grymaxion Plovdiv develops custom SAP extensions, applications, integrations, and configurations. Working with real projects, we see this transformation from the inside. The theory from the 2010s textbooks no longer works. Let’s take a look at how the focus has shifted and why the old approaches can no longer be used.
Classic SAP modules and what has changed
Traditionally, the SAP system was rigidly divided into functional blocks: FI and CO (finance, control and accounting), SD (sales and logistics), MM (purchasing), PP (production and planning), QM (quality), PM (equipment maintenance). These were parts of a unified but unwieldy ERP core that relied on a technical basis – the HANA platform and ABAP code.
Today, the very concept of a ‘module’ is outdated. The modern SAP module is no longer a piece of code tied to the core, but a standalone cloud service. It is a flexible tool that connects via API and is managed by Fiori. The service uses AI agents (SAP Joule) and extends any process – from ESG analytics to logistics – without interfering with the core S/4HANA. There is no longer any need to stop processes for updates.
New principles: the end of boxed licences
The module is no longer static. Changes in architecture have led to changes in licensing. The old model has lost its meaning. SAP is moving from the classic “licence per module” model to a consumption-based model with tariffs and metrics. In 2026, companies will pay for the volume of operations and intensity of use: API calls, AI agent activity, or cloud service consumption.
This also changes the logic of development, according to experts at Grymaxion business solutions. Now code is a direct expense. Developers are forced to create modules that not only work but also optimise resources. Hybrid scenarios arise: heavy analytics go to the cloud, while operational logic remains on edge devices (in production or in the warehouse) to avoid overpaying for traffic and speed.
From ‘refinement’ to digital product: SAP modules for business
SAP module development has transformed from writing code to creating a product. Whereas previously a module was simply a linear extension of ERP, in 2026 it will be a standalone digital product. It may consist of several related components: a microservice on BTP, a Fiori application, an AI script, an API gateway, an analytical model or an edge service, all working as a single entity.
What does this offer businesses?
Firstly, the “construction principle”: systems are no longer monolithic, but are assembled from independent blocks for specific tasks.
Secondly, “seamless updates”: changes to one module can be made without the risk of disrupting the entire platform.
Thirdly, ‘time-to-market’: the speed of implementation has increased significantly. To launch an ESG tracking or demand forecasting service, there is no need to change the entire ERP system.
In fact, companies that create SAP modules design a digital business contour where AI and analytics are built into every process by default.
The future of SAP modules after 2026
The trends are already clear, according to managers at Grymaxion Ltd. Modules will increasingly use predictive models and generative AI to forecast deliveries, analyse finances, and identify bottlenecks in production. Architecture will continue to move towards microservices, and ERP will become fully composable (Composable ERP).
Cross-domain processes will emerge, in which AI agents will coordinate the work of different modules, and the boundaries between financial, logistics, and HR systems will gradually disappear.
ESG modules will become standard, and hybrid cloud-edge solutions will be used in manufacturing, transport and energy: decisions are made ‘on devices,’ and only analytics go to the cloud.
GRYMAXION Ltd. (Bulgaria) creates external extensions on SAP BTP, Fiori applications, microservices, and API layers. GRYMAXION developers focus on ready-made industry standards, but at the same time create modules that precisely replicate the customer’s business processes. AI agents are embedded in procurement, finance, logistics, and inventory planning processes.