DSAG Technology Days & TechXchange 2026

Table of contents

• Day 1 - Technology Days
• DSAG Keynote
• Keynote SAP
• Guest Talk by CCC
• SEW Eurodrive 
• Netze BW
• Day 2 - Technology Days
• Softway
• Bearing Point
• Jungheinrich
• Day 3 - TechXchange
• Mastering RAP
• Joule for Developers
• Community
• Conclusion

This article contains some impressions of the past few days in Hamburg, the event, and the various topics.

 

Day 1 - Technology Days

The first day in Hamburg was characterized by the keynotes in the first part, the presentations from the committees, and various other formats. This year, the winners of the hackathon were announced directly, and there was no audience vote. This resulted in a change to the overall program.

 

DSAG Keynote

This year, the DSAG keynote was given by the new board member for technology, making it his first real test. This year's motto was "Lights on Layers - Design by Clarity," which was presumably intended to bring more clarity to the various levels and challenges. The opening remarks included a comparison of the current state of technology: storage capacity and computing power are currently growing exponentially on Earth, and have long ceased to be linear. Looking at AI, this can have a positive effect, as AI primarily needs data to learn from, and increased computing power is advantageous for its use.

This time, the focus was on three different layers: AI, data, and security. These layers are interdependent to function effectively and generate sufficient added value:

• AI - AI will primarily change the fundamental structure of infrastructure within companies. Where and how do agents operate within the network, and which systems and processes do they have access to? These points will continue to change within the company. It was also stated that the multi-LLM strategy and the agents at SAP are viewed positively, as they offer a certain degree of security and further development. However, there was also criticism that this technology has not yet reached customers; marketing is clearly taking precedence over technology. Currently, some companies are implementing their own solutions outside the SAP ecosystem. In the future, there will likely need to be onboarding processes for AI and agents, just as there are for new employees today.
• Data - The current reality in the data is primarily hybrid, fragmented, and ambiguous, which is not ideal for good results from AI models. At the current stage, this tends to lead to failures in the use of AI. Nevertheless, data remains a valuable asset and must be better utilized in the future to generate genuine added value. Therefore, SAP is also being asked to move from data chaos to the new world.
• Security – more data, more interfaces, more agents, and thus a larger attack surface for companies. The landscape of the future will not become simpler, but rather more complex and difficult to manage. The demands on IT continue to rise; everything is supposed to be faster and more secure, but this is equally difficult to implement.

 

It was emphasized once again that all three points must always be considered together in order to do justice to the different layers of the architecture and to derive the greatest added value and benefit from them. Following the keynote address, there was a panel discussion with speakers from various fields to gather perspectives from the different working groups and committees:

• AI - Generally speaking, AI is not yet fully integrated into business processes. However, in frontend development with MCP and Joule, development is already working very well. The general consensus was to take your time when implementing solutions and to consider various aspects such as security and compliance. A key requirement remains the availability of Joule for on-premises customers. If SAP fails to address this, customers will seek alternative solutions and companies.
• Data - 88% of projects fail at the outset due to data issues. Therefore, data quality simply must be improved. Likewise, the provision of data is too narrowly defined, as it primarily considers customers from the public and private cloud.
• Security - From a security perspective, the various areas such as ABAP and HANA already look very good; some other systems are out of scope, or at least it feels that way. Patch management is not always so easy, as it affects existing processes and applications and therefore must be tested just as thoroughly. And in the future, security should not only be the responsibility of SAP Basis, but other parties, such as development, should also be involved.

 

Keynote SAP

Basically, everyone wants to do AI right now, so began the SAP keynote. However, there are still numerous challenges, such as legacy systems, undocumented code, and high technical debt. The goal is to transform a "System of Record" into a "System of Context" so that AI can better integrate with existing systems. SAP is providing more new and integrated scenarios. SAP-RPT1 is also now available for processing and analyzing analytical scenarios. Contrary to the opinion of the DSAG, SAP's CTO expressed a more proactive view, stating that companies should definitely engage with AI. A reference was also made to Gartener, who noted that the gap between provision and actual output is widening, necessitating further reductions in this area.

The first step towards achieving this should be implemented today. The goal is not reaching the summit, but rather taking the various intermediate steps. Each step can generate real added value. This is precisely how SAP envisions the work and delivery of its various AI products and iterations, ensuring added value with each delivery. Currently, the question of "buy or build" is also being raised, with many customers primarily focusing on building their own solutions. This is currently a positive approach and is moving customers forward with their projects. However, in the future, these solutions should be replaced by stable "buy" models.

Finally, there was an insight into the use of AI and SAP's own products. The same products are used, but there are also various transitional solutions, such as the vacation request, which currently switches from Joule to the corresponding Fiori application. This already generates value while the actual modernization is still underway. Furthermore, "ABAP AI as a Service" will also be made available by the 2021 release, even though Joule for Developers is still only offered to private cloud customers. SAP and DSAG also plan to collaborate on the "AI-Native Northstar Architecture."

 

Guest Talk by CCC

The Chaos Computer Club presented a guest post this time. It focused on security, especially in the age of AI. Various solutions already used by companies, such as automated application processes, were discussed. However, prompt injection attacks later resulted in the theft of large amounts of application data, which was then used for phishing. AI systems also help to simplify, automate, and professionalize personal phishing attacks on individuals. However, phishing is not the only real problem; the increased number of deepfakes of well-known personalities or individuals about whom a lot of public information is available is also a concern. Other attacks on LLMs include:

• Evade Attack
• Poisoning Attack
• Prompt Injection
• Information Leakage

 

Particular attention should currently be paid to young students and trainees. They are currently learning how to execute and generate code on LLMs, but not yet a deep understanding of code or how to handle errors. This could mean a generation of lost talent for the future.

 

SEW Eurodrive 

The first presentation from the Development working group focused primarily on the topic of Clean Core and the introduction of ABAP Cloud. The company started with the principle of "Start Green," i.e., with a greenfield approach. The first step involved bringing everyone to the same level to ensure they were all moving in the same direction (greenfield instead of brownfield). This primarily means training developers in current technologies and promoting an understanding of Clean Core. In the second step, the company naturally wants to know: How clean are we, really? The measurability of Clean Core and the technical debt should be visualized. To do this, the colleagues used Teamscale for visualization and also conducted a software audit to investigate this question. Likewise, sustainable measures should be introduced to improve overall quality:

• Introduction of three feedback loops
• A static code analysis for the developer
• The code review (What has changed, What has been tested)
• To the development team (various trends and insights, such as duplicates or authorization checks)

 

Finally, feedback from the teams on the measures was also gathered to provide evidence of their benefits within development.

 

Netze BW

Netze BW was the second customer to take part in the Clean Core event. The focus here was primarily on brownfield migration, not greenfield. The company had 25 years of source code with various interdependencies that were difficult to manage. The initial goal was standardization to achieve scalability. The old Teck stack in SAP was very broad, especially considering the UI options. The framework and technology needed to be standardized to RAP and true software engineering. Standard tools like unit testing and code quality assurance were also to be used. Various internal training programs were implemented. Several experts were developed who could then serve as central contacts and multipliers. An important aspect was also the inventory of existing solutions, in order to gain a better understanding of the existing solutions and technologies, but also a good starting point for possible modernizations.

 

Day 2 - Technology Days

The second day then focused primarily on presentations and various impressions from the community.

 

Softway

Already familiar faces with their product, Softway AG this time focused on the implementation of the Global E-Invoice Cloud at a customer site. The main impressions gained here were how quickly and easily a SaaS solution can be implemented today when there are no transports or dependencies on the customer system. The colleagues also let us run a performance test on their system, which ultimately resulted in 38,000 invoices being created. However, the ABAP environment had no problem processing this.

 

Bearing Point

The colleagues from Bearing Point were already present at last year's congress and told us about the migration of their solution from Funding Management. What's exciting about the implementation is the strict adherence to Domain-Driven Design in their solution, as well as the considerable thought they put into the implementation. The respective business object is at the heart of the development and is divided into different layers:

• Presentation
• Business Context
• Persistence

 

Services and interfaces are located far outside this layer, and the actual logic of the exchange takes place at the business context level. The actual integration into RAP occurs only at the level of an unmanaged business object. This ensures that every object has an identical structure, which simplifies reuse and usage, as well as the onboarding of new employees and the creation of new objects. Here, too, the principle of standardization applies, even if the actual stack looks quite complex at first glance.

 

Jungheinrich

On the second day, there was another session on Clean Core and ABAP Cloud, this time from Jungheinrich. SAP had to take on the role of the customer, as a presentation was not possible due to illness. Here, insights were provided into the structure and use of ABAP Cloud in a greenfield scenario. The 3-tier model was introduced quite early on, which actually meant a shift towards the Clean Core level concept later on. In most cases, TIER 2 and a corresponding naming convention were introduced, which makes a change possible, but not always 100% consistent. The transformation also focused on upskilling development, still a very important topic for most companies. A key focus was creating more guidance for development and the process, not least through the introduction of the ABAP Test Cockpit.

 

Day 3 - TechXchange

The third day, which is actually a separate event, is being held in conjunction with the TechEd-on-Tour, so you'll also find formats like the Developer Garage. The day is usually conducted in English, which distinguishes it from the other two days and always represents something new within the DSAG, as it addresses more than just the German-speaking community. This year there were even more diverse formats than last year. Feedback was taken into account more, and in addition to all the hands-on sessions, there were also familiar formats for simply listening to information.

 

Mastering RAP

The solution walkthrough was very entertaining and included many points, best practices, and demos on the topic of modern development with RAP. Various aspects were highlighted, such as the use of BAPIs and released interfaces in development. There was also a further overview of BAPIs, their structure, and their use within ABAP Cloud. Since BAPIs will remain relevant for years to come, this is a very valid point. Besides BAPIs, the focus was also on RAP objects and their various phases. Understanding these different phases and using BAPIs within them is crucial for providing good, error-free business objects. If you'd like more information or to enjoy a consultation in the future, the team at Brandeis has also opened the RAPotheke. You can find more information via the link, which will certainly be a good opportunity to get answers to complicated questions and remains a service by and for the community.

 

Joule for Developers

Demos don't always work flawlessly and sometimes lead to challenges in planning and execution. Even the SAP colleagues once had to deal with systems that weren't 100% functional. Despite all the problems with Joule and system availability that day, numerous questions were answered, and part of the hands-on demonstration worked. Otherwise, the next opportunity for VS Code and Joule will be at the following ABAP Development Days.

 

Community

Community and exchange are all the more important these days. Learning from the mistakes of others, inspiration for one's own company, or exchanging information on the current state of development. The three days were full of all this. Occasionally, however, well-known figures want to leave the SAP ecosystem because they have reached the end of their tenure. For example, Karl Kessler will be leaving us at the end of the year, and many ABAP developers will still remember him from the ABAP Platform and/or Product Management. He has participated in numerous events, webinars, and presentations on all kinds of ABAP topics and worked at SAP for a very long time. This year, he is making his farewell tour of the community and will be appearing one last time at the ABAP Development Days.

 

Conclusion

The days were once again packed with exchanges within the community, impressions from the trade fair, company reports, and countless memories. The SAP world never stands still, and so should we, as we engage with new and established technologies every day.