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

Familiarize yourself with the clean core extensibility model by reading the SAP blog ABAP Extensibility Guide – Clean Core for SAP S/4HANA Cloud - August 2025 Update.

Learn the concept how to mitigate missing released SAP APIs by reading the official guidelines ABAP Cloud API Enablement Guidelines for SAP S/4HANA Cloud, private edition, and SAP S/4HANA.

A user can launch the custom online shop application to order gadgets. When gadgets are ordered, a purchase requisition is automatically created in the S/4HANA system.

In this scenario you have a Shopping Cart RAP Business Object for an online shop application in ABAP Cloud Development. You then want to be able to create purchase requisitions for the shopping cart entries. In an ideal case, this could be achieved by making use of a released API. In this tutorial group we show how to deal with the case in which no convenient released API is available to create purchase requisitions: you will find a suitable unreleased SAP API to use as an alternative to a released API, you will wrap it in a Custom Wrapper and then release the wrapper for consumption in ABAP Cloud Development. You will then integrate this wrapper in your Shopping Cart RAP BO. As a final product, you will have a RAP BO in ABAP Cloud Development that will consume the released wrapper to create purchase requisitions for your Shopping Cart RAP BO entries.

This tutorial group follows the assumption that there is no suitable released API to create purchase requisitions, and we therefore need to find and wrap an unreleased API as a suitable alternative. Please be aware that we follow this assumption simply for illustrative purposes, as SAP does indeed provide a released API to create purchase requisitions (see Integrate released purchase requisition API into Shopping Cart Business Object).

For productive use, you would develop your RAP BO in the productive package ZCUSTOM_DEVELOPMENT in your SAP S/4HANA system as suggested in the Developer Extensibility guidelines Create Structure Package, and you would develop the wrapper in a dedicated package of software component HOME, for instance ZAPI_DEVELOPMENT. For the scope of this tutorial group we will follow a simplified approach, and you will use local packages ZLOCAL and $TMP rather than productive packages.

The following requirements are needed for this tutorial group:

• In this tutorial series, it is assumed that your system is running on the SAP S/4HANA 2023 release with feature pack stack 3 installed.
• You are connected to your SAP S/4HANA system in the ABAP Development Tool (ADT) in Eclipse
• You have a user in the system with full development authorizations.
• You have set up developer extensibility as described in the official documentation Set Up Developer Extensibility. In particular: the ZLOCAL structure package is available and you have set up an ABAP Test Cockpit check variant as described in chapter 5.1.2 and installed SAP Note 3565942 (we will refer to this as ‘ATC Check Variant’ throughout the tutorial group).
• Please read the following ABAP Test Cockpit (ATC) recommendations carefully and create a check variant for Clean Core Extensibility as described.

We suggest to follow this tutorial group using a Fully-Activated Appliance (Current Version: SAP S/4HANA 2023 FPS03) in SAP Cloud Appliance Library for an easy start without the need for system setup, as the ZLOCAL structure package is automatically available, as well as the needed ATC check variant and the material used for the gadget shopping cart entries.