To know the name and the definition corresponding the transaction code and it's functionality.
There are multiple ways of searching for BADI.
- Finding BADI Using CL_EXITHANDLER=>GET_INSTANCE
- Finding BADI Using Repository Information System (TCODE- SE84)..
- Finding BADI Using SQL Trace (TCODE-ST05).
First Method
Finding BADI Using CL_EXITHANDLER=>GET_INSTANCE
Go to the Transaction, for which
we want to find the BADI,
Get the Program Name of Corresponding
Transaction.
(Click on System->Status. Double
Click on Program Name)
Once inside the program search
for ‘CL_EXITHANDLER=>GET_INSTANCE’.
Make sure the radio button “In
main program” is checked.
A list of all the programs with
call to the BADI’s will be listed.
The export parameter ‘EXIT_NAME’
for the method GET_INSTANCE of class CL_EXITHANDLER will have the user
exit assigned to it.
The changing parameter ‘INSTANCE’
will have the interface assigned to it.
Second Method
Finding BADI Using Repository Information
System (TCODE- SE84).
Go to “Maintain Transaction” (TCODE-
SE93).
Enter the Transaction VD02 for
which you want to find BADI.
Click on the Display push buttons.
Get the Package Name. (Package
VS in this case)
Go to TCode:
SE84->Enhancements->Business Add-inns->Definition
Enter the Package Name and Execute.
Third Method
Using SE19, where we have to write the code to call that Badi, either it call automatically .
SE19 is to implement a BADI, it is the only place where we write the code. BADIs are automatically called from the corresponding transaction, for which you need to write a BADI. We can call a particular BADI in any other program as we can call a FM, but BADIs are used only to enhance a standard functionality according to user requirement.
