T.Code for ABAP Debugger

[Former Member]

hi experts,

is there any tcode for abap debugger...................

[p291102]

Hi,

/H

Is the tcode for abap debugger

Thanks,

Sankar M

[Former Member]

Just execute '/h' in the command prompt. It will start debugging.

[Former Member]

Hi,

Use <b> \h</b> as tcode for debugging.

Reward points if helpful.

Regards,

Hemant

[Former Member]

hi Ramakrisha,

You can debug a report by setting the breakpoint in you report or buy just typing (/h) in the command window while in the selection screen.

Also some hints or you can say useful question in debugging,

<b>what is the use of calls and overview tab in debugger</b>

When you are debugging a program or function module then the tabs call and overview explains as follows.

Call Tab - This explains the function module or programs from where it is called and at which stage it has reached.

for eg .if you are in the form xyz called by function abc then in the call tab you will get

Subroutine XYZ

Function ABC

This indicates that subroutine xyz is being called from Function ABC.

Overview tab - This give slist of programs and function modules link to program or function you debugging.

Regards,

Jayant

[Former Member]

Hi Ramakrishaa,

Use <b>/h</b> not \h as i have written bymistake in previous thread.

Regards,

Hemant

[Former Member]

Hi,

U can use /H for activate Debugger

These r some Tcode for specific purpos.

TPDA_START Start Master of TPDA Debugger

TPDA_START_VERI Start the TPDA Debugger (VeriMode)

TPDA_START_WDA Start the TPDA Debugger (VeriMode)

TRSA S-API Debugger

Regards

Gaurav

[Former Member]

Hi

There is no Separate TCODE for debugging.

1. Use '/H' in the command line and execute the report/program, so that it goes to debugging mode

2. keep a hard coded break point in the code like BREAK-POINT and it stops there.

3.From the program Menu, Keep the Soft Break-points and do the debugging.

see the links

Refer to this thread

http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

Check these documents.

http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc

http://help.sap.com/saphelp_nw04/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc

http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm

http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm

http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34

Look at the SAP help link below

http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

Reward points if useful

Regards

Anji

[former_member196299]

hi Ram ,

use /h for going from program to debugging mode .

use F5, F6, F7 function keys for executions of statements.

Reward if helpful !

Regards,

Ranjita

[Former Member]

when we working in the prograsm we can give directly \h....I dont know other than this there is a code

[Former Member]

hi,

go to se38->give ur program name-.execute->give /h at command prompt->execute->now debugging will start->

f5-used for line by line debugging

f6-used for directly executing function modules or performs i.e. control won't go into that block.

f7-run to cursor

f8-direct executing.

fileds: here we can check fild values.

click fileds option and double click on the filed or type the filen name beside filed

tables : here we can check the data in the internal table.

click tables option and double click on the internal table.

Break points:

if you want to debug a particulr part you can use this.

place the cursor at any perform click breakpoint or double click on that line.it will be set.

if /h from report statement it will debug,so for debugging from particular point we will use break points.use f7 to traverse between multiple break points.

Watch-points: In some cases we need to check the data populated in the internal table for eample if we want to check the data of internal table record belongs to 100th vendor we will create watch point for this goto->breakpoints->create watch points->give filed itab-lifnr->=->100.

if helpful reward points.