#32Cloud-Ready Is a Property of Your App
The framework is ABAP Cloud compliant, and that says nothing about the app - cloud-readiness is decided in the SELECT, a released CDS view against a database table.
2 min read · 32 of 42
The framework is ABAP Cloud compliant. It is written in the ABAP for Cloud language version, it calls released APIs only, it modifies no standard SAP code, and it installs on BTP ABAP Environment and S/4HANA Public Cloud.
None of that says anything about the app somebody builds with it.
ABAP Cloud is a restricted language version, and the restriction that matters most on a screen is this one: no direct access to SAP database tables. The Virtual Data Model — the CDS views SAP publishes and maintains as an API — is the way in, and that is exactly what keeps an app upgrade-stable when the tables beneath it change.
The released view is the shape SAP keeps stable across the upgrade.
Two lines decide it. Here is cloud-ready:
" cloud-ready: a released CDS view
DATA t_orders TYPE STANDARD TABLE OF i_salesorder WITH EMPTY KEY.
SELECT FROM i_salesorder
FIELDS salesorder, salesorganization
INTO CORRESPONDING FIELDS OF TABLE @t_orders
UP TO 10 ROWS.
and here is the same screen, not cloud-ready:
" not cloud-ready: a database table read directly
DATA t_orders TYPE STANDARD TABLE OF vbak WITH EMPTY KEY.
SELECT FROM vbak
FIELDS vbeln, vkorg
INTO CORRESPONDING FIELDS OF TABLE @t_orders
UP TO 10 ROWS.
Same screen. Same framework. Same UI, down to the pixel. One of them survives the next upgrade and can move to a cloud system, and the other cannot — and nothing about the user interface is involved in the difference.
In short: a compliant framework does not make an app clean core. Clean
core is a property of what the application reads and writes, and it is decided
in the SELECT.