Home - Workshops about the ABAP RESTful Application Programming Model (RAP)
This repository contains the material for the hands-on session RAP120 - Build SAP Fiori Apps with ABAP Cloud and Joule for developers💎.
Table of Content
- Requirements for attending this workshop
- Overview
- Exercises
- Recordings
- Solution Package
- Known Issues
- How to obtain support
- Further Information
To complete the practical exercises in this workshop, you need the latest version of the ABAP Development Tools for Eclipse (ADT) on your laptop or PC and the access to a suitable ABAP system* that is connected to the SAP AI Core.
The appropriate flavor of the ABAP Flight Reference Scenario must be imported into the relevant system.
(*) SAP BTP ABAP environment and SAP S/4HANA Cloud Public Edition - as of release 2502 - are currently supported.
→ A dedicated ABAP system for the hands-on workshop participants will be provided.
→ Access to the system details for the workshop will be provided by the SAP instructors during the session.
🔵Click to expand!
The requirements to follow the exercises in this repository are:
In this hands-on session, you will learn how to use ABAP capabilities in Joule for Developers, including predictive code completion, unit test generation for ABAP CDS and ABAP code, and code explanation to speed up your development with ABAP Cloud.
🔵Click to expand!
This hands-on workshop dives into creating and testing a transactional SAP Fiori elements app with Joule, using the ABAP RESTful Application Programming Model (RAP) and its UI services.
You will build a simple transactional app to manage travel bookings based on a managed business object (BO) with a single node Travel.
ABAP Cloud is the development model for building clean core compliant apps, services, and extensions on SAP S/4HANA Cloud, SAP S/4HANA, and SAP BTP ABAP environment. ABAP Cloud covers different development scenarios such as transactional, analytical, intgeration, and enterprise search scenarios. RAP ist at the heart of ABAP Cloud for building transactional SAP Fiori apps, OData-based Web API, local APIs, and business events.
The resulting app will look like this:
Follow these steps to build a SAP Fiori App with Joule in ABAP Cloud
Exercises | -- |
---|---|
Exercise 6: Utilize the ABAP AI SDK powered by Intelligent Scenario Lifecycle Management (ISLM) | -- |
Exercise 7: Add a determination and enhance it with the ABAP AI SDK powered by ISLM | -- |
You can import this solution package
ZRAP120_SOL
into following ABAP systems:
- SAP BTP ABAP environment
- SAP S/4HANA Cloud Public Edition
- SAP S/4HANA Cloud Private Edition and SAP S/4HANA as of Release 2022.
The ABAP Flight Reference Scenario must be available in the relevant system before importing the solution package.
Click to expand!
Follow the instructions provided below to import the solution into your publc cloud system - i.e. SAP BTP ABAP environment and SAP S/4HANA Cloud Public Edition.
- Install the abapGit plugin in your ABAP Development Tools (ADT) for Eclipse if you have not already done so.
- In ADT, create the ABAP package
ZRAP100_SOL
in your system. - Open the abapGit Repositories view in ADT and follow the steps below.
- Create a link to the repository using the Link abapGit Repository window.
📤 Git repository URL:https://github.com/SAP-samples/abap-platform-rap100
- Now pull/import the solution implementation using the context menu Pull....
- Activate the imported development objects (Ctrl+Shift+F3).
No known issues.
Create an issue in this repository if you find a bug or have questions about the content.
For additional support, ask a question in SAP Community.
You can find more information about the generative AI in ABAP, ABAP Cloud, RAP here:
- Generative AI in ABAP Cloud
- ABAP Cloud Roadmap Information - GenAI
- ABAP AI Strategy Frequently Asked Questions
- ABAP Cloud development model
- Getting Started with ABAP RESTful Application Programming Model (RAP)
Copyright (c) 2025 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.