RAP630 - Cloud ERP Extensibility

https://github.com/SAP-samples/abap-platform-rap630/tree/main

Description

This repository contains the material for the RAP hands-on workshop called RAP630 - Use ABAP Cloud for developer extensibility where Developer Extensibility is used.

Developer extensibility as defined by SAP basically encompasses two activities

Develop custom code to implement your own business logic.

Here you can make use of existing API's from SAP that have been released for that purpose.
Extend an existing RAP Business Object so that additional business functionality is added.

Such an extensible RAP business object will usually reside in another software components or it is an existing extensible RAP BO that has been delivered by SAP or a SAP partner.
By extending the funcitionality of an existing RAP Business object its functionality can be adapted to your specific business requirements.

Overview

This session introduces attendees to the ABAP Cloud programming model and how this can be leveraged how

to build extensions (own code) in SAP S/4HANA BTP, ABAP Environment and
to extend an existing RAP Business Object using the ABAP Cloud programming model.

📋Requirements for attending this workshop

^Top of page

You need the latest version of the ABAP Development Tools for Eclipse (ADT) on your laptop or PC as well as the access to an appropriate ABAP system* to carry out the practical exercises of this workshop.
(*) The supported ABAP systems are SAP BTP ABAP Environment, SAP S/4HANA Cloud, Public Edition.
In order to run the workshop on an on prem system use the on-prem branch.
The openSource RAP Generator must be imported into the relevant system.

In the SAP ABAP Environment Trial systems the RAP Generator has already been imported for your convenience.

Click to expand!

The requirements to follow the exercises in this repository are:

⚠ Exception regarding SAP-led events such as "ABAP Developer Day" and "SAP CodeJam":
→ A dedicated ABAP system with pre-generated packages for the hands-on workshop participants will be provided.
→ Access to the system details for this on-site workshop will be provided by the instructors during the session.

Slides

Presentation

🛠 Exercises

^Top of page

Exercises

In the Getting Started section you will generate

two exercise packages and
an extensible managed Business Object (BO) with one entity Shop with generic transactional behavior - i.e. CRUD: Create, Read, Update, and Delete.

The first aspect of developer extensibility is how to use RAP business objects that have been C1-released by SAP or SAP partners for the use in ABAP Cloud development.

In Exercise 1 you will learn how you can leverage the released RAP business object I_BankTP. You will learn how you can use a new wizard in ADT that lets you generate a custom UI on top of a released RAP business object without having to write a single line of code. An additional (optional) task is to call the same released RAP business object from within a class which shows how released RAP business objects can also be used in application jobs.

The second aspect of developer extensibility is the option to extend an extensible RAP business object that has been delivered by SAP or a SAP partner.

In Exercise 2 you will extend the behavior of the base RAP business object that has been generated in the Getting Started section. You will learn how extend the behavior of the base RAP BEO by validations, determinations and side effects.

In Exercise 3 you will then continue to extend the data model with additional fields.

Since with the latest release 2408 an Extension Field Wizard has been delivered we have to different scripts for ABAP Environement systems and on premise systems (SAP S/4HANA 2023).

In Exercise 4 you will continue to extend the behavior of the base RAP business object by adding an action. Since actions can only added via an extension to fields that have been added itself via an extension, adding an action via an extension must be performed after Exercise 3.

So let us start and have a look at the Getting Started section.

Getting Started - Generate starter package

You can the continue and build custom code that leverages released API's

Exercise 1 - New App on stack (Developer Extensibility)

Finally you will learn how to extend a RAP Business object

Exercise 2, 3 and 4 - Extend a RAP business object (behavior and data model)

Online Help

https://help.sap.com/docs/abap-cloud/abap-rap/develop-rap-extensions https://help.sap.com/docs/SAP_S4HANA_CLOUD/6aa39f1ac05441e5a23f484f31e477e7/1b345c53060846b091f55ea901e21ae7.html

Download and Installation

The packages ZRAP630_SOL and ZRAP630_SOL_EXT that contain the solutions of this workshop can be downloaded via abapGIT into an SAP BTP, ABAP Environment system or into the SAP S/4HANA Cloud, ABAP environment system.

Please note that these packages have already been installed in the SAP BTP, ABAP Environment Trial systems !
So there is no need to install them on an ABAP Environment trial system.

Click to expand download and installation steps.

The steps to download and install the package of the base RAP business object can be found here:

Create a package 'ZRAP630_SOL' with 'ZLOCAL' as the superpackage.
Link this package with the URL of the RAP630 GitHub repository https://github.com/SAP-samples/abap-platform-rap630.
Use the branch main.
Pull changes.
Use mass activation to activate the objects that have been imported in step 3.
Publish the service binding ZRAP630UI_SHOP_O4_SOL.

After you have performed the aforementioned steps you can continue to download the solution package of the extension project ZRAP630_SOL_EXT.

Since these are stored for technical reasons in another Github repository abap-platform-rap630-ext you have to to download the source from that repository 'https://github.com/SAP-samples/abap-platform-rap630-ext'.

Known Issues

How to obtain support

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.

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.

Code of Conduct

Please read the SAP Open Source Code of Conduct.

SAP-samples/abap-platform-rap630