ABAP Cloud – Mitigate missing released SAP APIs in the 3-tier extensibility model: a tutorial how to wrap a BAPI and integrate it into a custom RAP business object

Alexander Rother announced the ABAP Cloud API Enablement Guidelines for SAP S/4HANA Cloud, private edition, and SAP S/4HANA in his ABAP Cloud – How to mitigate abap exextemissing released SAP APIs in SAP S/4HANA Cloud, private edition and SAP S/4HANA – The new ABAP Cloud API enablement guide blog post.

To become an expert on that topic, you may have been searching for an end-to-end example on how to mitigate a missing released SAP API – either to understand the concept in more detail, or to play it through yourself. Therefore, I am happy to announce that SAP has provided the Mitigate Missing Released SAP API in the 3-tier Extensibility Model tutorial group.

The tutorial group shows how to wrap the BAPI_PR_CREATE function module (BAPI) in tier 2, how to release it for consumption in tier 1, and then how to consume it from an Online Shop RAP business object in tier 1. Moreover, it also shows how to handle non-released authorization objects that may be checked by the BAPI.

Sample Scenario

The tutorial group uses the BAPI_PR_CREATE function module as an example. Please note that SAP indeed provides the released I_PurchaseRequisitionTP business object interface and you would use the released business object interface in your implementation project instead. The example was chosen deliberately so that you can compare both approaches: the Integrate released purchase requisition API into Online Shop Business Object tutorial shows how to consume the I_PurchaseRequisitionTP business object interface from the Online Shop business object.

Now it’s time to get your hands dirty and play through the Mitigate Missing Released SAP API in the 3-tier Extensibility Model tutorial group. Enjoy.