Debugging material needed

[Former Member]

HI

I am working as a SD/CRM functional consultant, since many times i used to get bog down in some of the program while debugging. I am able to analyse the code with F5 and F6 for any Zreports where as for Stnd SAP reports it's becomign a night mare, hence taking help with my abaper for each issue.

Can some one pl drop links or send me good and easy document to get expertise to debug any stnd sap codes?

My email id shankar1242@yahoo.co.in

Cio

shankar1242

[former_member673464]

hi..

Check these links.It may help you.

Debugging Document.

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

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

regards,

veeresh

[Former Member]

HI Veerah

Your first and third links are not working.

As you know help.sap.com/debug material is too lenghty and sometimes perplexing for a poor tech guy like me.

Thats why requested some of you can have some documents for a easy make.

Cio

Shankar1242

[former_member673464]

hi shan..

You can go through documentation about break points and watch points which help you in debugging .It is always difficult to debug SAP standard programs for anyone.

regards,

veeresh

[Former Member]

Hi Shankar,

Debugging throgh the standard SAP code is always a night mare for everyone, even abapers

There is no as such standard way. You can only understood over a period, with experiance.

One easiest way is when you debug a standard code, you should not go into the code of any FM in the first place, see if all the variables you require has the proper values and which FM is changing the parameters you looking for. Once you are able to find out the same now just look at the code of that FM, which internally may be calling few more FM/subroutines. In this way you need to go down..

Hope you understood it. Revert back if further query.

Reward points if useful.

Regards,

Atish

[Former Member]

Hi,

Check your mail id.

Thanks,

Anitha

[Former Member]

I normally gets confused that whenever SY-SUBRC =4 program is failed in that step but i observed its not the case always..

Anitha

Not received any mail from you..

Sorry guys for posting all my silly doubts but they mean alot for a fun consultnat..

Cio

Shankar1242

[Former Member]

Hi Shankar,

SY-SUBRC = 4, means the last step, which ever is, is failed. It varies on place on place.Lets say FM returned with sy-subrc = 4 that means it has not performed the task it is meant for.

Regards,

Atish

[Former Member]

hi,

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.

debugging procedure:

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

if helpful reward points

[Former Member]

Hi,

For Debugg:

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.

For SQL Trace:

check the following link:

http://www.sapbrain.com/TOOLS/SQLTRACE/SQL_TRACE.html

For Runtime Analysis:

check the following link:

http://www.sapbrain.com/TOOLS/RUNTIMEanalysis/SAP_runtime_analysis.html

Regards,

Bhaskar