topic Re: script in Application Development and Automation Discussions

script

Former Member — Fri, 17 Aug 2007 07:00:18 GMT

Hi,

In script when we debug what is the use of F5,F6, F7,F8 ?

Thank you

ASHOK KUMAR

Re: script

Former Member — Fri, 17 Aug 2007 07:02:25 GMT

f5 step by step execution

f6 block execution

f7 to leave block from middle

f8 to move across break ponts and direct execution

regards

sandhya

Re: script

amit_khare — Fri, 17 Aug 2007 07:03:19 GMT

The function keys F5, F6 , F7 and F8 serve the same purpose as they do in Report Debugging...

Regards,

Amit

Reward all helpful replies.

Re: script

Former Member — Fri, 17 Aug 2007 07:04:03 GMT

Utilities --> Activate Debugger on the initial screen of SAP Script i.e. SE71...

The function keys F5, F6 , F7 and F8 serve the same purpose as they do in Report Debugging...

When you debug the script, you will see following information being displayed:

1. Page

2. Window

3. Function ( OPEN_FORM, WRITE_FORM, CONTROL_FORM, etc)

4. Event ( If blocks, paragraph & character formats, field values etc)

5. Element ( Elements defined in the windows)

Try and identify which element is giving you the erroneous data and rectify it...

Re: script

Former Member — Fri, 17 Aug 2007 07:04:21 GMT

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

http://www.sappro.com/downloads/Settings&SystemAreas.pdf

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

https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=3187106

https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=850453

https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=1546485