Dear Developers,
Developers follow where customers lead. As of 2026, S/4HANA on-premise and legacy ECC systems still dominate the landscape, keeping the focus primarily on ABAP and RAP.
The "cloud native" wave aims to keep the SAP core clean while evolving rapidly, allowing customers to build side-by-side on BTP—the core of the CAP narrative. As developers, we have our hands full; we must rewrite legacy code using RAP while transitioning to BTP, where building from scratch with CAP offers significant merit.
While the developer community remains heavy on ABAP—positioning them as the next generation of RAP developers—Fiori (JavaScript) and Java developers, as well as customers integrating non-SAP systems, can leverage CAP. A strong community push is essential for this developer ecosystem to thrive.
Despite these advancements, SAP GUI remains the primary interface for most customers. A new stable ground is open for competition: which side are you on, the RAP way or the CAP way?
Developers follow where customers lead. As of 2026, S/4HANA on-premise and legacy ECC systems still dominate the landscape, keeping the focus primarily on ABAP and RAP.
The "cloud native" wave aims to keep the SAP core clean while evolving rapidly, allowing customers to build side-by-side on BTP—the core of the CAP narrative. As developers, we have our hands full; we must rewrite legacy code using RAP while transitioning to BTP, where building from scratch with CAP offers significant merit.
While the developer community remains heavy on ABAP—positioning them as the next generation of RAP developers—Fiori (JavaScript) and Java developers, as well as customers integrating non-SAP systems, can leverage CAP. A strong community push is essential for this developer ecosystem to thrive.
Despite these advancements, SAP GUI remains the primary interface for most customers. A new stable ground is open for competition: which side are you on, the RAP way or the CAP way?
Want More to read : Check this on SAP community ✅
