abap-cloudlisted

# ABAP Cloud / Steampunk Complete reference for the **ABAP for Cloud Development** language version — the restricted ABAP dialect mandatory on SAP BTP ABAP Environment, SAP S/4HANA Cloud Public Edition, and recommended for clean-core on-premise via embedded Steampunk. Covers the dual-pillar restriction model (syntax subset + released-API whitelist), the release-contract system (C0-C4), object-type and statement allowlists, migration from classic ABAP, and integration with ZROUTER's ADT toolchain. ## Why This Matters SAP enforces a strict boundary between custom code and SAP core in cloud ABAP systems. Developing with the **Standard ABAP** language version on a cloud system produces a hard syntax error at activation time. The restriction is enforced at two independent levels: 1. **Syntax restriction** — only a defined subset of ABAP statements is valid. 2. **Released-object check** — every external repository object reference (class, function module, CDS view, DDIC element, BAdI, table, structure, type pool, etc.) is validated against SAP's whitelist at syntax-check time. There is no escape hatch. The language version is a property of the ABAP object itself and is automatically set at creation time in cloud systems. It cannot be overridden retroactively on SAP BTP ABAP Environment. On S/4HANA on-premise with embedded Steampunk, developers can choose the language version per object, but once chosen, changing it requires a formal object deletion and recreation. ## AB