Badi's Debug

[Former Member]

Hi Experts,

How to Debug Badis can any one explain step by step?

Thanks,

[Former Member]

Debugging the badi:

keep a break point in badi implementation and run the tcode.

it automatically trigger ur badi implementation

how to find badi in debug mode :

1. Open the class CL_EXITHANDLER in transaction se24.

2. In the class open the method GET_INSTANCE by double clicking on it.

3. In the method set a breakpoint in the statement CALL METHOD cl_exithandler=>get_class_name_by_interface

After doing the above steps execute the transaction for which you need to know the BAdIs. When the application stops at the breakpoint check the value in the CHANGING parameter EXIT_NAME in the debugger. This will contain the BAdI name.

The advantage with this way of searching for the BAdI is that you get to know at which point in time of the application the BAdI is called and how many times the BAdI is called. You can also find out BAdI at certain events, say, when you save or press enter in the transaction.

[matt]

Some good advice here. I'd add one more point. If you find the breakpoint doesn't trigger, deactivate then reactivate the BADI

matt

[Former Member]

hi chalapathi,

Debugging of badis can be done in two ways

thery are

first method is by,

1. Open the class CL_EXITHANDLER in transaction se24.

2. In the class open the method GET_INSTANCE by double clicking on it.

3. In the method set a breakpoint in the statement CALL METHOD cl_exithandler=>get_class_name_by_interface

After doing the above steps execute the transaction for which you need to know the BAdIs. When the application stops at the breakpoint check the value in the CHANGING parameter EXIT_NAME in the debugger. This will contain the BAdI name.

and

Second method is

go to se84 in that open enhancements->business addins->defintions

in that give the package of the transaction for which you want to find the list of badis the package can be found by going to system status and then copy it

and you will find all teh list of badis and user exits in that you can identify it by reading teh documentation or just by keeping the break point in the particular badi and runnig it in teh debugging mode.

you can find all the badi triggering for for that particular badi.

I think the explanation is clear to you .

if you have any doubts feel free to reach me .

<REMOVED BY MODERATOR>

Thanks and regards,

A.kalyan.

Edited by: Alvaro Tejada Galindo on Apr 15, 2008 4:34 PM