How to debug BDC , Dialog program and Script

[Former Member]

Hi all,

Please let me know, how to debug BDC , Dialog program and Script

Thanks&Regards

Devi

[Former Member]

Hi,

Place a breakpoint by selecting the line and breakpoint button from the application toolbar.

USe F5 key,F6, F7 and F8 Key for Processing

double click on the variable to view the contents

Regards

Arun

[Former Member]

Hi,

bdc will be just like the reports

/h is one method

and in the call transaction

put mode 'A'

this is all screen mode

you can see each and every entry and screen by screen

dialog prgoramms also by /h or puting break-points

scripts by activating the debugger inthe

se71 transaction

give your script name

and utilities -- activated debugger

reward points if helpful,

thanks & regards,

Venkatesh

[Former Member]

BDC: you should choose DISMODE = 'A'.

Dialog: '/H'.

Script: i think you should print test and test,

[Former Member]

Hi Rama,

For BDC Debug, Refer the foll.thread,

To debug Script, foll. the links,

http://www.geekinterview.com/question_details/1489

http://searchsap.techtarget.com/tip/0,289483,sid21_gci1066270,00.html

[Former Member]

<b>SCRIPT DEBUGGING</b>

When we want to debug the SAPSCRIPT, we need to first activate the debugger, we have 2 ways to activate the Debugger.

1) Execute the program RSTXDBUG

2) Go to SE71, from the initial screen enter the form name and press Utilities --> Activate Debugger

When we are in the Debug screen,

3.1) F5 will be debug filed by field, that means if a single line is having 5 fields, if we press the F5 this will do field by field,

3.2) F6 will be line by line, that means when we press the F6, it will debug the line and it will go to the next line. F7 also do the same way

3.3) F8 will be very useful when we have any include statement in the SCRIPT, if any include is there and we press the F5 or F6 then this will go that Include (normally SO10 or any transaction text), then if we want line by line debugging then we can press the F5 or F6, or if you want to execute that in a single shot then press the F8, then the debugger will be executed that include and come back to the Script debugging.

Some times in the script, we may right lengthy lines, if we want to debug that whole line, we have an option called Left/Right, this we will find the Debug screen of the script, there is a Push button, we can make use this button to debug.

We can put the breakpoints in the SCRIPT DEBUGGER also, just press the BREAKPOINT Pushbutton from the debugging screen or press EDIT --> Breakpoint

If we want to debug the print program from the SCRIPT DEBUGGER, just press SHIFT+F7 or EDIT --> ABAP Debugging

If we want to see the Windows which are defined in the forms, just press the Go to --> Form --> Windows .if we want to see the pages go to --> Form --> pages. Here we have an option to see the page wise window also go to --> Form --> page Windows

If we want to see the paragraphs which are defined in that script, press go to --> Styles --> paragraphs.

If we want to see the Character formats which are defined in that script, press go to --> Styles --> Character Strings.

If we want to see the Page formats which are defined in that script, press go to --> OTF --> Page.

If we want to see the Elements which are used in the Script, then press go to --> Text Elements --> Form Elements.

If we want to see the commands which are used in the script, press go to --> Commands --> List

Finally, if we want to exit from the SCRIPT DEBUGING, simply press Debugger --> Exit

<b>DEBUG BDC</b>

ust go into debugging mode and do the BDC step by step, when it comes to the Call Transaction line, check the mode which will be 'N'....Now, overwrite this with 'A' and execute the BDC...It will run in All Screens Mode....

As suggested above the MODE 'A' will do the trick as it takes you to all screens.

Normally MODE N will be defaulted as it will be used for background processing,

Here is a simple tip,

This will be the call transaction part of the program,

CALL TRANSACTION 'IW32' USING BDCDATA MODE 'N'

MESSAGES INTO MESSTAB.

I would suggest you to make it like this,

DATA: V_MODE TYPE C VALUE 'N'.

*<In debug mode set V_MODE = 'A' for debugging>

CALL TRANSACTION 'IW32' USING BDCDATA MODE V_MODE

MESSAGES INTO MESSTAB.

This will be very useful because you just need to change the value of the V_MODE at runtime as A for debugging besides it has N which is the default to be used. (i.e. you need not change the code again and again).

This will be very useful when you have to debug some program in QA or PRD servers.

regards,

srinivas

<b>*reward for useful answers*</b>