Skip to content

ABAP Cloud ​

ABAP Cloud is the development model of the BTP ABAP Environment and of S/4 Public Cloud: code in the language version ABAP for Cloud Development, using released APIs only. abap2UI5 runs there as an ordinary ABAP Cloud development - classes, interfaces and one table, no BSP, no function group. This page collects what is different there and links the pages that cover each step in detail.

I want to…Section
know what is differentWhat Differs
install itInstallation
write the handlerThe Handler
know why the page loads UI5 from ui5.sap.comThe UI5 Bootstrap
call an external service, a language modelOutbound HTTP
know what does not work thereWhat Is Not Available
put an app in front of business usersLaunchpad and Work Zone

What Differs ​

Standard ABAPABAP Cloud
installabapGit, the report or ADTabapGit for Eclipse (ADT) only, then a mass activation
endpointan ICF node in SICF, handler on if_http_extensionan HTTP service, a development object in ADT, handler on if_http_service_extension
who can open the endpointevery user with the authorization you give the nodedevelopers: the service needs S_DEVELOP; business users come through a tile
default UI5 bootstrapsdk.openui5.org (OpenUI5)ui5.sap.com (SAPUI5)
outbound HTTPCL_HTTP_CLIENT, an SM59 destination or a URLCL_WEB_HTTP_CLIENT_MANAGER, a communication arrangement, a BTP destination or a URL
stateful sessionsavailablenot available: set_session_stateful( ) compiles and does nothing
transportthe package travels in a transport requestthe package belongs to a software component, which travels

Your apps are a separate question. The framework runs on both, and an app runs on ABAP Cloud when the app itself uses released APIs only: a SELECT on a released CDS view, not on a classic table.

What the framework decides at run time ​

The framework is one code base for both. Where the two differ it asks z2ui5_cl_ui5_util_context=>check_abap_cloud( ), which answers abap_true when the classic table T100 cannot be described by RTTI - which is the case under ABAP for Cloud Development. Four things depend on the answer:

  • The default bootstrap of the user exit: ui5.sap.com instead of sdk.openui5.org (below).
  • The outbound HTTP client: CL_WEB_HTTP_CLIENT_MANAGER instead of CL_HTTP_CLIENT (below).
  • Finding the classes of an installation: the user exit and the roundtrip monitor are found as implementations of an interface, through the XCO library (XCO_CP_ABAP) instead of the classic class repository.
  • The start page shows the answer in its ABAP for Cloud checkbox.

Every class the framework needs on one platform and that is missing on the other is named dynamically, so the framework activates on both.

Installation ​

The steps, in order - each one is shown with screenshots on S/4 Public Cloud, which covers the BTP ABAP Environment as well:

  1. Pull with abapGit for Eclipse. Pull the newest release tag without a suffix, X.Y.Z, into a package of your own. Folder logic PREFIX, and a short package name: the sub-packages are derived from it, and a package name has 30 characters at most (S/4 Public Cloud).
  2. Mass-activate. ADT abapGit pulls every object inactive. Activate them all, and repeat until nothing is left inactive.
  3. Create the handler class and the HTTP service in ADT (below). Open the service URL: the start page of abap2UI5 appears, with ABAP for Cloud ticked.
  4. For business users: deploy the frontend app and put a tile in front of it (Launchpad and Work Zone).

What travels to the next system, and in which order, is on Transport, Landscape.

The Handler ​

The handler implements if_http_service_extension and hands the request and the response to the framework:

abap
CLASS zcl_my_abap2UI5_http_handler DEFINITION PUBLIC.
  PUBLIC SECTION.
    INTERFACES if_http_service_extension.
ENDCLASS.

CLASS zcl_my_abap2UI5_http_handler IMPLEMENTATION.
  METHOD if_http_service_extension~handle_request.
    z2ui5_cl_ui5_http_handler=>run( req = request res = response ).
  ENDMETHOD.
ENDCLASS.

run( ) with req and res takes the ABAP Cloud path: z2ui5_cl_ui5_http_handler=>factory_cloud( ) wraps the two objects, which is also the call for a handler that needs the instance itself. The HTTP service that names this class is created in ADT as a development object of the package; SAP's tutorial Create an HTTP Service shows the dialog. Everything else about the endpoint - the user exit, the CSP, the authorization of apps - is the same as on Standard ABAP (Security, Authorization).

The UI5 Bootstrap ​

ABAP Cloud answers every HTTP service with a Content Security Policy header of its own, next to the one abap2UI5 writes, and the browser enforces both. The platform's script-src trusts the SAP hosts only. The OpenUI5 CDN, the default everywhere else, is refused there, and the page stays blank.

So from abap2UI5 1.149.0 on, the default bootstrap on ABAP Cloud is https://ui5.sap.com/resources/sap-ui-cachebuster/sap-ui-core.js - SAPUI5, the latest release. An exit that sets cs_config-src itself is not touched. To bootstrap from another host, set it in the exit and add it to the trusted sites of the system: app Maintain Protection Allowlists, tab Content Security Policy (Bootstrapping). The same holds for a custom theme on another host (Theme).

Outbound HTTP ​

The framework's outbound HTTP - z2ui5_cl_ui5_util_http and through it the language model providers of z2ui5_cl_ui5_llm (create_claude( ), create_openai( )) - uses CL_WEB_HTTP_CLIENT_MANAGER on ABAP Cloud. The destination parameter is read in three ways:

destinationWhat the framework creates
emptya destination from the URL itself - the host then needs an outbound communication arrangement
SCENARIO/SERVICE_ID or SCENARIO/SERVICE_ID/COMM_SYSTEMa destination from a communication arrangement - the slash tells it apart
any other namea destination of the BTP destination service, used as the system, not as the user in front of the screen

The key, the model and the endpoint come from the app; nothing is written into the framework. A request that could not be sent, or got no answer in time, can be retried on ABAP Cloud as on Standard ABAP; a missing or forbidden destination cannot (Release Notes).

What Is Not Available ​

What ABAP Cloud does not release is not there for an app either. The cases the pages of this site meet:

  • Stateful sessions. The released HTTP interface has no stateful mode, so set_session_stateful( ) does nothing and every roundtrip lands in a fresh session. An enqueue lock does not survive to the next click (Statefulness, Lock).
  • Classic APIs. cl_bcs and its kin are not released: mail goes through cl_bcs_mail_message (Send by Mail). Spreadsheets go through XCO_CP_XLSX (Spreadsheet), data element texts through XCO_CP_ABAP_DICTIONARY instead of the classic DDIC reads (Translation), and the classic form runtime is not released for PDF forms (Print Forms as PDF).
  • Selection screens, WRITE lists, CL_SALV_TABLE. None exists. The add-on behind Apps Written Like Reports gives the same shape as an abap2UI5 app.
  • Parts of add-ons. An add-on is ABAP Cloud ready where its README says so, and some say partly. The popups add-on: transport requests work on-premise only, and the search help does not run on ABAP Cloud yet. The table content loader: XLSX upload and download are not ready there. The SQL console: the native SQL console is Standard ABAP; the Open SQL console runs on ABAP Cloud. The full list is on Add-ons.
  • BSP applications in the Excel add-in. The host page is served from an approuter instead (Excel Add-in).

Launchpad and Work Zone ​

The HTTP service needs S_DEVELOP, so a business user reaches an app through a tile. That takes two things:

  • The frontend app, deployed from VS Code with the SAP Fiori tools - one of the branches cloud, cloud_v2 or cloud_new of the frontend repository (Deployment Scenarios, S/4 Public Cloud).
  • The chain of objects behind a tile: launchpad app descriptor item, IAM app, business catalog, business role, then space and page (S/4 Public Cloud).

To show the apps in SAP Build Work Zone instead, a BTP destination points at the HTTP service and a connector app forwards to it (Build Work Zone). What an app can do inside a launchpad

Operations ​

  • Draft cleanup and the Admin Cockpit. The draft table cleans itself on every app start, as everywhere. The Admin Cockpit runs on ABAP Cloud, and its housekeeping is an application job there (Monitoring).
  • Compression. On ABAP Cloud the platform compresses the responses (Basis Runbook).
  • Upgrades. Pull the next tag with abapGit for Eclipse and activate what arrives inactive; with the cloud_new frontend branch the deployed app needs no new deployment (Versioning, Upgrade).