SAP Flow

Business Add-Ins are SAP enhancement technique, based on ABAP Objects. They can be inserted to accommodate user requirements, too specific for a standard delivery. All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.

Pros:
BADIs can be used any number of times, whereas USER-EXITS can be used only one time.
BADIs are based on Object-Oriented-Programming with fixed structure -> Therefore SAP guarantees
the upward compatibility of all Business Add-In interfaces.

Cons:
It’s difficult to say, when using a transaction, whether BADI is used or not.

Solution:

1, Go to transaction SE37 and put a breakpoint on function SXV_GET_CLIF_BY_NAME.
2, Set a breakpoint on a call of the only function included.
3, Open another session and set YOUR transaction. The debugging mode opens with info
on BADIs. Name = BADI, Clif = implementation of a BADI.


FUNCTION sxv_get_clif_by_name .
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(NAME)
*" VALUE(PREFIX) TYPE SEEX_CLIF_PREFIX
*" EXPORTING
*" VALUE(CLIF) TYPE SEOCLSNAME
*"----------------------------------------------------------------------
CALL FUNCTION 'SXV_ADD_PREFIX'
EXPORTING
name = name
prefix = prefix
IMPORTING
new_name = clif.
ENDFUNCTION.