SAP S/4HANA Key User Extensibility powered by Embedded Steampunk: How to debug Key User Extensibility extensions (e.g. Cloud BAdI’s) in client 100

SAP S/4HANA Cloud Key User Extensibility powered by Embedded Steampunk:
How to debug Key User Extensibility extensions (e.g. Cloud BAdI’s) in client 100

Before the introduction of Embedded Steampunk it was not possible within SAP S/4HANA Cloud to debug any Key User coding, e.g. Custom Logic.
This has changed now with the general availability of Embedded Steampunk, which adds a new powerful option to the In App extensibility portfolio of SAP S/4HANA Cloud. E.g. ABAP Development Tools (ADT) as a powerful development environment and with that also the possibility to debug custom code.

This debug option is not only available for the code developed with ADT in Embedded Steampunk in client 080, but also for coding developed with the Key User tools in client 100.

Do you want to know how you can debug Key user coding working in client 100? In case your answer is yes, then this blog post is the right one for you.

In order to be able to debug in the Key User tool client 100 the following prerequisite needs to be fulfilled:

Your user in client 100 needs to have a business role assigned, which contains the business catalogs

  • SAP_A4C_BC_DEV_SUP_PC (“Development – Analysis and Support”) and
  • SAP_A4C_BC_DEV_OBJ_DIS_PC ( “Development – Development Objects Display”).

As soon as this is the case within ADT you create a new “ABAP Cloud Project” and enter the URL for client 100 as “ABAP Service Instance URL”.

As soon as you have done that, you can log into this ADT ABAP Cloud Project with a user having the aforementioned business catalog assigned.
Now let us assume for a moment that you created a Cloud BAdI implementation via the Key User tool “Custom Logic” with the implementation name “YY1_CALCULATEDFIELD”. This custom logic is executed whenever a Key User Custom Field is calculated.
Within ADT we do now click on the “Open ABAP Development Object” button and as search term we enter the name of the Cloud BAdI implementation “YY1_CALCULATEDFIELD”.

We are then navigated to our Key User BAdI implementation. There we can set the breakpoint exactly at that position we are interested in.

When we now start the triggering application, e.g. in our SAP Fiori UI in client 100, the ADT debugger jumps in and stops at exactly the position we marked.

With this you are done! Congratulations!

Feedback, Comments, or Questions

You’re cordially invited to provide them in the comments section below.