SAP BTP | Technical Training — David Ollero Montes

What BTP actually is

BTP is not a single product but an umbrella of services running on Cloud Foundry or Kubernetes: databases (HANA Cloud), application runtimes, integration tools, low-code tools and AI services. For an ABAP/Fiori developer, the two services used daily are the ABAP Environment (Steampunk) and Cloud Application Programming Model (CAP).

ABAP Environment (Steampunk)

A cloud-hosted, restricted version of ABAP where only released, Clean-Core-compliant APIs are allowed. RAP, CDS and Fiori Elements work exactly as on-premise, but direct table access or unreleased function modules are blocked by design — forcing extensions that survive an S/4HANA upgrade.

ABAP CDSextension-scenario.ddls

// A BTP ABAP Environment extension reads S/4HANA data
// only through a released remote API — never a direct table join
@AbapCatalog.sqlViewName: 'ZIEXTCONTRACT'
define view entity ZI_EXT_CONTRACT
  as select from API_CONTRACT_MANAGER // released remote API
{
  key ContractId,
      ContractManager1
}

Cloud Application Programming Model (CAP)

CAP is BTP's alternative stack for building services in Node.js or Java, using the same CDS language for data modelling that RAP uses on the ABAP side — the same mental model, a different runtime. It's common in greenfield BTP projects that don't need ABAP at all.

CDSschema.cds

entity Contracts {
  key ID          : String;
      manager     : String;
      amount      : Decimal(15,2);
      status      : String enum { active = 'A'; pending = 'P'; };
}

Integration and extensibility services

SAP Integration Suite — connects S/4HANA with third-party systems (iFlows, APIs, EDI) without custom ABAP interfaces.
SAP Build (formerly Business Application Studio) — the browser-based IDE used to develop RAP, CAP and Fiori extensions in the cloud.
SAP Build Work Zone — the modern launchpad that aggregates Fiori apps, BTP apps and external content in a single entry point.

Why it matters for a career: companies moving to S/4HANA Cloud increasingly forbid custom code inside the core system. Knowing how to build the same functionality as a BTP side-by-side extension is what makes a Fiori/RAP developer future-proof.

Transport and CI/CD on BTP

Steampunk doesn't use the classic ABAP transport requests you'd recognise from on-premise. Changes travel between systems via the ABAP Transport Management Service (cTMS), and pipelines are typically driven from SAP Continuous Integration and Delivery or a standard git-based CI tool — much closer to how any modern cloud application ships code.

Career angle: this is often the biggest adjustment for developers coming from a pure ECC background — the mental model shifts from "one shared dev system with SE80" to "git branches, pipelines and short-lived cloud systems." Getting comfortable with that shift is as valuable as the ABAP syntax itself.