Scope
- Domain model (CDS), service layer, events
- Approuter, XSUAA, destinations, connectivity
- HANA Cloud or S/4 remote service
- Fiori Elements UI (list / object) on BTP
- CI/CD skeleton, mta.yaml, env split (dev/test)
SAP CAP
Cloud Application Programming Model: CDS services on BTP, Node.js (Java when needed), Fiori Elements or SAPUI5, S/4 consumed as a remote API. This is our default way to write process logic without putting Z-code in the core.
CAP is not RAP
If data and behaviour stay on S/4 released objects, we write SAP RAP. CAP is where the process lives on BTP. We record the decision in discovery; we do not mix both in the same sprint.
Platform: SAP BTP. Package: BTP Extension Factory.
Who it is for
Teams with Node.js / BTP skills who want to consume S/4 APIs instead of growing a Z-program stockpile. If the work belongs in the ABAP core, we steer to RAP.
Related: SAP Cloud · BTP consulting