SAP-samples/abap-platform-rap640

RAP640 - Using ABAP Cloud to Build Extensions for SAP S/4HANA Cloud, Private Edition - Mitigating missing released SAP APIs

Description

This repository contains the material for the hands-on session RAP640 - Mitigating Missing Released SAP APIs which is about mitigating missing released SAP APIs when building apps, services, and extensions with the ABAP Cloud development model on SAP S/4HANA Cloud Private Edition and SAP S/4HANA.

Table of Content

• Requirements for attending this workshop
• Overview
• Exercises
• Solution Package
• Known Issues
• How to obtain support
• Further Information

📋Requirements for attending this workshop

^Top of page

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 - i.e. at least release 2022 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. Adapt the Web Browser settings in your ADT installation

System access (workshops provided by SAP)

ℹ️ Regarding SAP-led events such as "ABAP Developer Day" and "SAP CodeJam":
→ 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 instructors during the session. With these system details you can connect via ADT to the system as described in the following how-to-guide.

How to connect with ADT to a preconfigured appliance system

🔎Overview

^Top of page

Learn about the current business scenario and the clean core extensibility model based on the clean core level concept

Click to expand!

About the Business Scenario

In this hands-on workshop, we will guide you through the development of a custom wrapper for the ABAP Cloud enablement of an classic API (a BAPI) for creating purchase requisitions, then a custom RAP BO and UI service on top of it to develop a transactional, design-capable, Fiori Elements-based list report app using RAP. Finally, you'll use your custom API wrapper in your custom RAP BO to integrate your custom app with the standard professional SAP Purchase Requisition app.

The resulting app will look like this:

To set the business context, the scenario is the following: This demo scenario shows a custom and SAP Fiori elements-based shopping cart app built on-stack with RAP. The custom app is integrated with the standard Purchase Requisition app in SAP S/4HANA Materials Management using a custom wrapper on top of the classic API BAPI_CREATE_PR.

About building custom wrappers

You will learn how to apply the ABAP Cloud API Enablement Guidelines for SAP S/4HANA Cloud Private Edition and SAP S/4HANA to consume a classic API. You will learn how to mitigate missing released SAP APIs when working with ABAP Cloud on these two products.

Learn more: Understand the sample scenario how to mitigate a missing released SAP API

🛠Exercises

^Top of page

Follow these steps to build a custom wrapper for the ABAP Cloud enablement of an non-released SAP API for creating purchase requisitions, then a custom RAP BO and a UI service on top of it for a transactional, draft-enabled Fiori Elements list report app. Finally, you'll use your custom API wrapper in your custom RAP BO to integrate your custom app with the standard professional SAP Purchase Requisition app.

Main Exercises

Exercises	--
Exercise 1 - Implement a Wrapper for the "Create Purchase Requisition" (BAPI_PR_CREATE) function module	--
Exercise 2 - Create a Shopping Cart Business Object	--
Exercise 3 - Create Value Help, Enhance the Behavior Definition and Behavior Implementation of the Shopping Cart Business Object	--
Exercise 4 - Integrate the Wrapper into the Shopping Cart Business Object	--
Exercise 5 - Integrate with classic BOR events	--

Optional Exercises

Exercises	--
Exercise 6 - Provide Authorizations to Users for Non-Released Authorization Objects checked by the "Create Purchase Requisition" (BAPI_PR_CREATE) function module	--

📤Solution Package

^Top of page

You can import the solution package ZRAP640_SOL into your system* - i.e. at least the release 2022 of SAP S/4HANA Cloud Private Edition and SAP S/4HANA.

ℹ️ Regarding SAP-led events such as "ABAP Developer Day" and "SAP CodeJam":
The solution package ZRAP640_SOL is already imported into your dedicated system used during these events.

🚧 More information coming soon

🔁Recordings

^Top of page

Watch the replay of a webcast on cloud API enablement held during SAP's Devtoberfest in 2023.

📹 Cloud API Enablement on SAP S/4HANA and SAP S/4HANA Cloud Private editions

⚠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

You can find further information here:

• Blog Post on how to mitigate missing released SAP APIs in SAP S/4HANA Cloud | SAP Community
• Detailed document on ABAP Cloud API Enablement Guidelines | Guide
• ABAP RESTful Application Programming Model (RAP) | SAP Community page
• Most frequently asked questions: ABAP Cloud FAQ | RAP FAQ
• RAP640 Tutorials Group: Mitigate Missing Released SAP API in the 3-tier Extensibility Model | SAP Developers' Center
• Various hands-on workshop materials on ABAP Cloud, including RAP and embedded analytics

License

Copyright (c) 2024-2026 SAP SE or an SAP affiliate company and abap-platform-rap640 contributors. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file; you may not use any file of this project except in compliance with the License.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the LICENSE for the specific language governing permissions and limitations under the License.