S/4 Public Cloud

Use abap2UI5 for on-stack extension scenarios in S/4 Public Cloud. It uses only released APIs and is fully compatible with the ABAP Cloud language version, satisfying SAP's "clean core" cloud extension requirements.

To install abap2UI5 on S/4 Public Cloud, follow these steps:

1. Install abap2UI5 with abapGit

S/4 Public Cloud supports only the ADT abapGit version. abap2UI5 contains only classes, interfaces, and tables, so you can pull it without issues.

Use the standard installation process with abapGit for Eclipse.

You'll see the pull operation running:

After a moment, the installation completes:

2. Mass Activate the Imported Artifacts

When installing repositories with ADT abapGit, all artifacts arrive inactive. Activate them manually. The simplest approach: create a dedicated inactive/active folder tree for the abap2UI5 project:

You'll see that all artifacts are inactive:

When activation completes, refresh the folder tree:

Now you'll see that all artifacts are active:

3. Set Up the HTTP Service

Build an HTTP handler manually or use the cloud branch of the frontend repository.

Important: In S/4 Public Cloud, accessing the HTTP endpoint needs S_DEVELOP authorization. This is the quickest way to test in development environments, but makes the scenario unfit for production.

For production, finish the frontend deployment and tile configuration in the steps below.

4. Deploy the UI5 App (Optional)

Since ADT abapGit doesn't support UI5 apps (BSPs) directly, deploy the app manually:

1. Download the app folder from the frontend repository
2. Deploy it to your system with the SAP deployment guide

5. Configure Launchpad and Tiles (Optional)

Set up the Fiori Launchpad, pages, sections, and tiles for the abap2UI5 apps:

1. Follow the SAP Launchpad configuration guide
2. Configure tiles for business users and manage permissions

BTP ABAP Environment

BTP ABAP Environment shares the same technical base as S/4 Public Cloud. The instructions above work for both systems.