# #28 Cloud-Ready Is a Property of Your App 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. Now the uncomfortable part: 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: ```abap " 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 TABLE @t_orders UP TO 10 ROWS. ``` and here is the same screen, not cloud-ready: ```abap " 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 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. That is worth saying plainly, because a framework's badge is easy to mistake for a guarantee, and vendors are not always in a hurry to correct the mistake. Clean core is not a property a dependency grants an application. It is a property of what the application reads and writes, and it is decided in the `SELECT`. A cloud-ready framework does not make a cloud-ready app. It just stops being the reason one is not.