What an ABAP developer needs, with AI
Map by Damir Majer · 2026 · 37 tiles · SAP Inside Track Munich
What changes with AI
The map without AI groups 22 tiles into five areas. This one has 37 tiles in seven areas. Damir identifies eleven new skills, eight that gain importance and four tasks done less often by hand. Tile sizes reflect his judgment.
ABAP Unit, code review and knowledge of business processes gain weight. The question in Damir’s accompanying post is how the developer defines a correct result before an agent starts work.
Read the map as a list
New with AI
- Decide what correct means
- Know when to stop the agent
- Review more than you type
- Explain the business domain
- Measure before and after
- Teach the juniors
- Check the API Policy first
- Give the agent context
- Know where the code goes
- Keep the agent secure
- Build AI into your apps
The craft
- Modern ABAP and OO
- Clean ABAP · More important
- ABAP Unit and test doubles · More important
- Packages and design
- Reading legacy code · More important
The domain
- Business process knowledge · More important
- Talk to the business
- Know the SAP standard
- Custom code to S/4HANA
Your stack
- ABAP Cloud
- CDS and code pushdown
- RAP business objects
- Clean core levels A to D
- ADT in Eclipse or VS Code
Around the code
- ATC and static checks · More important
- Code review in pull requests · More important
- Git for ABAP
- Released APIs only · More important
- Secure by design · More important
People
- Lead developer as multiplier
- Keep learning
- Work in a mentored team
Less by hand
- Typing RAP scaffolding
- Looking up syntax and docs
- First drafts of documentation
- Test skeletons by hand
Cite this
Majer, D. (2026). What an ABAP developer needs, with AI [Map]. Damir’s Notebook. https://damirmajer.com/maps/abap-developer-2026-with-ai/
