Cutting through the tech mambo Jambo of BTP. CAP, RAP, CPI, UI5. Developers just can’t explain anything visually with examples.
Q: Why both CAP (Cloud Application Programming) and RAP (REST Application Programming)? Why not a unified development approach analogous to good old ABAP’er doing everything?
A: CAP happened because SAP needed their own ‘full stack’ platform similar to the likes of Microsoft Power Platform and Google Firebase. This will result in a developer economy distinct from SAP core. A parallel universe’ where developers need not bother about the database and applications of SAP but still figure out a way to extend capabilities of SAP on Cloud. e.g. by developing APIs that freely integrate SAP with third party non-SAP applications.
RAP is another name for core ABAP report programming. You simply use SAPs APIs to manipulate data in database.
Analogy – mnemonic
CAP ~ The old SAP Webdynpro, Business Server Pages, SOAMANAGER, SICF, RFCs, IDOCs. Workflow
RAP ~ The old SAP Data Dictionary, BAPIs, FM, BADIs, User Exits, SAP Gateway (for exposing data)
Example Developments on CAP (that cannot be done with RAP)
– Workflow applications that transcends multiple systems
– Integrate SAP S/4HANA with Workday or IoT devices (or anything external)
– A dashboard that needs data from SAP, Amazon and Air Traffic Control.
– A self-service customer ordering portal.
– Mobile app for bar code scanning in warehouse (without connection)
– Supplier self-service applications
– Think of building something like Ariba without paying for Ariba licenses.
Example Developments on RAP (that cannot be done with CAP)
– Add custom fields in apps, reports in S4HANA.
– Change business logic in S4HANA
Q2: Isn’t the new development on BTP bad labor economics? Now you need 4 special skills – CAP, RAP, CPI, Data Engineer as they seem to evolve in different directions from a learning and career guard perspective. or will someday down the line developers will master all these skills?
A2: Yes bad economics because of learning curves but eventually the developers will be expected to be fluent with CAP, RAP, UI5, Fiori and CPI. Because the customers do not really know what they want. Not upfront. Developers need to suggest ideas.
Q3: What broad learning paths might evolve on SAP BTP as the developer ecosystem matures?
A3: (Views are mine)
Application developers – CAP, RAP, Fiori, CPI, API Developers – SAP to SAP. SAP to non-SAP
Analytics/AI/ML/IoT – They will eventually get subsumed under functional consultants in some broad areas of Finance or Operations in Core ERP. It doesn’t make sense to pay for “Analytics Experts” for whatever limited appetite that Businesses have to consume Analytics.
Automation – They will exist for some more time until it’s all subsumed as part of core ERP.
Security- This is purely because its labor intensive. They will continue to be separate.
