Exciting developments were shared regarding SAP’s extensibility strategy, especially around SAP BUILD and ABAP Cloud. Here are some key takeaways from Day 1:
SAP has clarified the extensibility portfolio, offering flexibility for both low-code and pro-code developers across different environments. Here’s a breakdown of the approach:
1.1 SAP BUILD + ABAP CLOUD
Perhaps the most exciting development is inclusion of ABAP CLOUD into the SAP BUILD Family. The inter operability is going to open up so many gates for developments are these bridges are getting built between low code and pro code methods.
SAP BUILD Architecture Diagram ( I feel Joule Studio needs to be part of this, I hope SAP takes a note of this and updates this diagram)
1.2 INTEROPERABILITY /FUSION DEVELOPMENT
An emerging trend to watch is the fusion between low-code and pro-code environments. The ability to seamlessly integrate both worlds opens new possibilities for SAP users. Here are a few examples:
- CAP backend services: Developed using SAP Build Code, these services can be consumed by low-code applications such as SAP Build Apps.
- Automations triggered by SAP S/4: SAP S/4 events can trigger automations residing in SAP BTP.
- ABAP Functions in Fiori UI: ABAP functions wrapped and consumed within Fiori elements can be enhanced using Build Code.
Going forward, SAP BUILD is set to become the default option for any extensibility, whether it’s for ABAP or Build environments.
1.3 JOULE STUDIO:
Another exciting development is Joule Studio, a quick-to-implement platform allowing users to build AI agents and integrate them into SAP’s Joule. The studio is designed for AI-driven scenarios, such as document understanding APIs, and is expected to expand further in 2025.
Now you will see a fourth option when creating a new project -Joule Skill.
Example Service now Ticket Generation Flow in Joule Studio
However, for me personally some confusion remains as Joule Studio offers business rules and decisions, overlapping with capabilities found in SAP Build Process Automation, which already supports workflows. It will be interesting to see how these tools evolve and differentiate over time. Stay tuned.
