RAP120 - Build SAP Fiori Apps with ABAP Cloud powered by Joule's ABAP developer capabilities

Description

This repository contains the solution packages for jump-start session called AD180 - Build SAP Fiori Apps with ABAP Cloud powered by Joule's ABAP developer capabilities at SAP TechEd Virtual 2024.

ABAP Cloud is the development model for building clean core compliant business apps, services, and extensions on SAP S/4HANA Cloud, SAP S/4HANA, and SAP BTP ABAP Environment. ABAP Cloud covers different development scenarios, i.e. transactional, analytical, and integration scenarios, including enterprise search capabilities. The ABAP RESTful Application Programming Model (RAP) ist at the heart of ABAP Cloud for building transactional SAP Fiori apps, OData-based Web APIs, local APIs, and business events.

In this hands-on tutorial, you will learn how generative AI can support the development of clean core compliant draft-enabled transactional SAP Fiori elements apps with the ABAP RESTful Application Programming Model (RAP) as well as read-only SAP Fiori elements apps in ABAP Cloud. You will also learn how to define and raise business events in RAP-based applications that can be consumed locally or remotely via SAP Event Mesh for loosely coupled integration scenarios.

Solution Package

^Top of page

You can import the solution package ZRAP120_SOL and its sub-packages ZRAP120_AGENCY_SOL and ZRAP120_EMPLOYEE_SOL into your system.

The supported ABAP systems are SAP BTP ABAP Environment, SAP S/4HANA Cloud Public Edition, or at least the release 2023 of SAP S/4HANA Cloud Private Edition and SAP S/4HANA.

The appropriate flavor of the ABAP Flight Reference Scenario must available in the system before importing the solution package.

Follow these steps to import the solution packages into your system:

1. Install the abapGit plugin in your ABAP Development Tools (ADT) for Eclipse if you have not already done so.

2. Create the ABAP package ZRAP120_SOL in ADT in the relevant system.

   • Package Name: ZRAP120_SOL
   • Description: RAP120 - Solution Packages
   • ✅ Add to favorites packages
   • Superpackage: ZLOCAL

3. Open the abapGit Repositories view in ADT

4. Create a link to the rap120 abapGit repository by clicking on the + icon and maintaining the required information in the Link New abapGit Repository... window:
   📤 Git repository URL: https://github.com/SAP-samples/abap-platform-rap120
   👤 Credentials: Enter your user and either your password or personal access token.
   📦 Package: ZRAP120_SOL

5. Now pull/import the FULL solution implementation using the context menu Pull....

6. Activate the imported development objects (Ctrl+Shift+F3) and publish the local service endpoint of the service bindings ZUI_AGENCYSOL_O4 and ZUI_EMPLOYEESOL_O4 to view the service URL, entity sets and associations.

Known Issues

^Top of page

No known issues.

How to obtain support

^Top of page

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.

Further Information

^Top of page

• ABAP RESTful Application Programming Model (RAP) | SAP Community page
• Modernization with RAP | SAP Blogs
• ABAP Cloud Roadmap Information | SAP Help Portal
• Explore the interactive SAP BTP ABAP Environment road map | SAP Road Map Explorer
• RAP100 Tutorials Mission on SAP Developers Center | SAP Tutorials
• Create an SAP Fiori elements app with SAP Business Application Studio and deploy it to the SAP BTP ABAP Environment | SAP Tutorials

Contributing

If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.

License

Copyright (c) 2024 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.