Build transactional SAP Fiori elements-based Apps with nominated APIs using Tier 2 extensibility model in ABAP RESTful Application Programming Model (RAP)

When you are developing an RAP Application in SAP S/4 Private Cloud Edition and you identify a artifact like BAPI which has a missing C1 released artifact but you find it as nominated API , you mitigate the situation by creating a Tier 2 wrapper

You can have a brief understanding on: ABAP Cloud - How to mitigate missing released SAP APIs in SAP S/4HANA Cloud, private edition and SAP S/4HANA – The new ABAP Cloud API enablement guide

Level: Intermediate

Introduction

Description This repository contains the material for the Devtoberfest 2024- Clean Core Extensibility with ABAP Cloud in SAP S/4HANA Cloud Private Edition & SAP Teched 2024- AD106 | Clean core extensibility of SAP S/4HANA Cloud Private Edition with ABAP Cloud.

🔎Overview

This repository is all about how to build wrapper around nominated APIs and use it as RAP BO ; especially about how to use when building greenfield implementations.

📋 Requirements

^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 release 2023 of SAP S/4HANA Cloud Private Edition and SAP S/4HANA.

Click to expand!

The requirements to follow the exercises in this repository are:

1. Install the latest Eclipse platform and the latest ABAP Development Tools (ADT) plugin
2. Understand the sample scenario how to mitigate a missing released SAP API (Read Step 4 for technical requirements)
3. Create software component using ABAP For Cloud as ABAP Language Version
4. You have created an ABAP Project in ADT that allows you to access your Application Server as mentioned above. Your log-on language is English.
5. You have downloaded and installed the zabapgit_standalone report. Make sure to use the most recent version as indicated on the installation page.
6. You have installed the certificate files for github.com, see abapGit Documentation.

ABAP Platform

Choose this if you are working on SAP S/4HANA, on-premise edition or SAP S/4HANA Cloud, private edition. To import the reference scenario into your ABAP system, follow the steps in the relevant README file and download the sources from the branch corresponding to your your backend version:

• README of branch ABAP-platform-2023-Classification-Maintenance (Application Server ABAP 7.58)
• README of branch ABAP-platform-2023-Product Classification Assignment (Application Server ABAP 7.58)

📹Recording

^Top of page

For a compact overview of this repository , watch the session replay from SAP Devtoberfest 2024 (gated content) & SAP Teched 2024 (gated content):

⏺ Clean Core Extensibility with ABAP Cloud in SAP S/4HANA Cloud Private Edition - Youtube Video

⏺ AD106 | Clean core extensibility of SAP S/4HANA Cloud Private Edition with ABAP Cloud

Note:
The code available in this repository is slightly different from these recording.

Known Issues

No known issues.

ℹFurther Information

^Top of page

You can find further information on the ABAP RESTful Application Programming Model (RAP) here:

• 📃 State-of-the-Art ABAP Development with RAP | SAP Community- A collection of diverse getting started materials.
• 📃 ABAP Cloud API Enablement Guidelines for SAP S/4HANA Cloud, private edition, and SAP S/4HANA.
• 📃 The list of available S/4HANA Cloud Private Edition Classic APIs
• 📃 Understand the sample scenario how to mitigate a missing released SAP API- A collection of diverse getting started materials.
• 📄 ABAP Cloud – SAP S/4HANA extensibility – May 2023 update | SAP Blogs
• ❓ Most frequently asked questions: RAP FAQ
• 🛠 Develop and Run a Fiori Application with SAP Business Application Studio | SAP Tutorials
• 🛠 Landing page with various hands-on workshop materials on ABAP Cloud, including RAP and embedded analytics

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.

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.