User Exit BADIs - aidamate13/AMS-Knowledge-Base GitHub Wiki

How to find a User Exit or BADI from debugger.

When we are trying to find a User Exit or a BADI, we can use some features of the debugger.

On top menu, we click: Breakpoints -> Breakpoint at -> Breakpoint at Statement

image

On the below popup, on ABAP Cmnds

image

We can put breakpoints on the followings statements:

  • User exits: CALL CUSTOMER-FUNCTION
  • BADI: CALL BADI

Also, for the BADI we can insert on the second tab

image

the following class that is triggered before the call of the BADI’s.

  • Class name: CL_EXITHANDLER
  • Method Name: GET_INSTANCE

[!NOTE] The use of CL_EXITHANDLER-GET_INSTANCE is for Classic BADI.

The use of CALL BADI is for Kernal BADI.

Classic BADI:

  • Interface name automatically generated
  • Implementing class name automatically created
  • Uses proxy class (CL_EXITHANDLER)
  • Not using Fallback Class
  • Implementation done in SE19

Kernal BADI:

  • We have to create interface
  • Implementing class name, we need to give
  • Not uses proxy class
  • Execution time less
  • Uses Fallback Class