Break points and watch points

Hi all
Can anybody help me using break points and watch points.what do they exactly do as well..
Thanks
abap user

Hi
Breakpoints
Instead of starting an ABAP program directly in the Debugger, you can also debug a program by creating one or more breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
Directly-set
dynamic breakpoints Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoint
at statement The Debugger stops the program directly before the specified statement is executed.
Breakpoint at subroutine The Debugger stops the program directly before the specified subroutine is called.
Breakpoint at function module The Debugger stops the program directly before the specified function module is called.
Breakpoint at method The Debugger stops the program directly before the specified method is called.
Breakpoints at system exceptions The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
Use
Static Breakpoints
Static breakpoints are not normally user-specific. Once a user has inserted a BREAK-POINT statement in an ABAP program, the system always interrupts the program at that point. You should only use static breakpoints during the development phase of an application. You should set static breakpoints whenever more than one programmer is working on the same program and you always want to stop the program in the same place.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. You should, therefore, use them when you only want the program to be interrupted when you run it yourself. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages:
 You do not have to change the program code
 You can set them even when the program is locked by another programmer
 You can define a counter (for example, only activate the breakpoint after it has been reached five times).
Special Dynamic Breakpoints
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the program code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger.
Transferring Breakpoints to HTTP and Update Sessions
If an HTTP or update session is called from a Logical Unit of Work (LUW), new work processes are started for these new sessions. Breakpoints that were defined beforehand in the calling LUW are copied to these sessions where they can be displayed under breakpoints.
If, for example, the update module func is called via CALL FUNCTION func IN UPDATE TASK, the new work process is displayed in a second window if Update debugging was selected under Settings in the debugging mode. All the breakpoints that were set in the calling LUW can then be processed here.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC <> 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities  Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
1. Position the cursor on the line of the source code at which you want to set the breakpoint.
2. Choose Utilities  Breakpoints  Set or the Stop icon. The system confirms that the breakpoint has been set.
To display a list of all dynamic breakpoints in a program, choose Utilities  Breakpoints  Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program.
Setting Dynamic Breakpoints in Debugging Mode
To set a dynamic breakpoint in the Debugger:
1. Position the cursor on the line in which you want to set the breakpoint.
2. Select the line by double-clicking it or choosing Breakpoint  Set/delete.
The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted.
When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.

Breakpoints at Statements
You can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at an ABAP statement:
1. Choose Breakpoint  Breakpoint at  Statement...
2. Enter the ABAP statement.
The system sets a breakpoint at all points in the program at which the ABAP statement occurs.
3. Choose ENTER.
The breakpoint applies to all lines containing the specified statement.
Result
The system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Breakpoints at Subroutines
You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a subroutine:
1. Choose Breakpoint  Breakpoint at  Event/Subroutine.
2. Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.
3. Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
Breakpoints at Function Module
You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a function module:
1. Choose Breakpoint  Breakpoint at  Function module...
2. Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.
3. Choose ENTER.
Result
If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.
Breakpoints at System Exceptions
You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at a system exception:
Choose Breakpoint  Breakpoint at  System exception.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.
Saving Breakpoints
If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.
To save the breakpoints that you have set in the Debugger:
Choose Breakpoint  Save.
The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.
You can also delete breakpoints that you have saved:
 By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.
 By choosing Breakpoint  Delete all. In this case, the system deletes all dynamic breakpoints.
Managing Dynamic Breakpoints
The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto  Control debugging  Breakpoints.
Functions
This display mode contains the following functions for breakpoints:
Breakpoint Display
The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.
Counter
In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.
Deleting Breakpoints
Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint  Set/delete. To delete all breakpoints, choose Breakpoint  Delete all.
Activating and Deactivating Breakpoints
Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint  Activate/deactivate.
Watchpoints
Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
Use
You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
Features
 You can set up to five watchpoints in a program.
 You can also specify the conditions on which a watchpoint is to become active.
 You can specify logical conditions between up to five conditional watchpoints.
 You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.
 You can change and delete watchpoints.
Setting Watchpoints
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.
Procedure
To set a watchpoint, start the Debugger and proceed as follows:
1. Choose Breakpoint  Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears.
2. Decide whether you want to set a local or global watchpoint.
3. Enter the program and the name of the field for which you want to set the watchpoint. In the Program field, the name of the program currently running is always defaulted.
4. If you want your watchpoint to be activated each time the contents of the field change, the definition is now complete, and you can return to the Debugger by pressing ENTER .
5. To create a conditional watchpoint, that is only activated when a particular situation arises, choose one of the following relational operators.
Operator Meaning
< Less than
<= Less than or equal
= Equal
<> Not equal
>= Greater than or equal
> Greater than
6.
7. You can use the Comparison field option to specify whether the comparison is to be carried out with a value that you specify or with the contents of another field. Depending on your choice from step 6, enter a value or a field for the comparison.
Result
The system confirms the watchpoint and adds it to the list in the display. When you finish your debugging session, the watchpoint is automatically deleted unless you have explicitly saved it.
Specifying Logical Links
If you have more than one conditional watchpoint, you can specify a logical link between them:
OR Only one of the specified conditions must be met
AND All of the conditions must be met.
To create a logical link between watchpoints:
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to open the watchpoint display.
2. Set the Logical operator between watchpoints option.
The default value is always OR .
Changing Watchpoints
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
2. Choose the pencil icon in the line containing the watchpoint you want to change.
3. Change the watchpoint attributes in the Create/Change Watchpoint.
3. Choose ENTER .
Deleting Watchpoints
You cannot delete watchpoints by choosing Breakpoint  Delete or Breakpoint  Deactivate/activate. Instead, proceed as follows:
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
2. Choose the trashcan icon in the line containing the watchpoint you want to delete.
Memory Monitoring with Watchpoints
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables. By placing an ampersand (&) in front of the object name, you can display the reference in question in hexadecimal format. With internal tables, you can also display the table header by placing an asterisk (*) at the beginning of the name.
Reward ifusefull

Similar Messages

What is the utility of watch point and break point in ABAP DEBUGGING !

What is the utility of watch point and break point in ABAP DEBUGGING !
PLEASE TELL ME IN DETAILS AND IF POSSIBLE WITH SCREEN SHOTS !

Hi,
Breakpoints, Watchpoints, and Checkpoints
Summary
The standard Breakpoints tool is always located on the Breakpoints desktop. With this tool, you can manage breakpoints, watchpoints and checkpoints. In addition, you can monitor the current status of the different breakpoint types.
Detailed Description
Breakpoints
In the Breakpoints area, you will see a list of all the breakpoints set so far. If one of the breakpoints has just been reached, this is marked with a yellow arrow. The visibility (Debugger, session, user) and type (line, ABAP command, ) is displayed for each breakpoint.
If you double click the Navigation() column, the system will display the breakpoint in the respective source code.
The visibility of a breakpoint can be changed through the dropdown list. To change the visibility of several breakpoints, mark them and select the pushbutton Save as Session Breakpoint or Save as User Breakpoint.
You can change the visibility of all Debugger breakpoints using the menu path Breakpoints-> Save Debugger BPs as -> ....
In addition, you have functions for creating, changing, activating and deactivating breakpoints at your disposal.
Watchpoints
In the Watchpoints area, you will see a list of all the watchpoints set so far. The watchpoint last set is highlighted with a yellow arrow.
For each watchpoint you will see not only the current value but the value before the last changed. (Technically speaking, each time you create the watchpoint and each time the watchpoint variable is changed, a clone of this variable is created.)
In this way, you can always determine what changes have been made to the monitored variable. For complicated data structures, such as internal tables or structures, select the pushbutton Compare Variables( ) and choose the Diff tool to compare the old and new variable values.
In addition, you have functions for creating, changing, activating and deactivating watchpoints at your disposal.
Checkpoints
In addition, you can edit conditional and unconditional checkpoints using the Breakpoints tool. This function is provided in the new Debugger only. Conditional checkpoints are set first in the source code using the ASSERTstatement; unconditional checkpoints are set using the BREAK-POINT statement. These have the effect that programs will be continued only if a preset condition is fulfilled. In the following window, these checkpoints can be searched for, activated, or deactivated.
Pls refer to :
http://help.sap.com/saphelp_nw70/helpdata/en/e2/5f5a42ed221253e10000000a155106/frameset.htm
Regards,
Renjith Michael.

What is utility of watch points and break point in ABAp debugging !

What is utility of watch points and break point in ABAp debugging !

Hi,
Breakpoints, Watchpoints, and Checkpoints
Summary
The standard Breakpoints tool is always located on the Breakpoints desktop. With this tool, you can manage breakpoints, watchpoints and checkpoints. In addition, you can monitor the current status of the different breakpoint types.
Detailed Description
Breakpoints
In the Breakpoints area, you will see a list of all the breakpoints set so far. If one of the breakpoints has just been reached, this is marked with a yellow arrow. The visibility (Debugger, session, user) and type (line, ABAP command, ) is displayed for each breakpoint.
If you double click the Navigation() column, the system will display the breakpoint in the respective source code.
The visibility of a breakpoint can be changed through the dropdown list. To change the visibility of several breakpoints, mark them and select the pushbutton Save as Session Breakpoint or Save as User Breakpoint.
You can change the visibility of all Debugger breakpoints using the menu path Breakpoints-> Save Debugger BPs as -> ....
In addition, you have functions for creating, changing, activating and deactivating breakpoints at your disposal.
Watchpoints
In the Watchpoints area, you will see a list of all the watchpoints set so far. The watchpoint last set is highlighted with a yellow arrow.
For each watchpoint you will see not only the current value but the value before the last changed. (Technically speaking, each time you create the watchpoint and each time the watchpoint variable is changed, a clone of this variable is created.)
In this way, you can always determine what changes have been made to the monitored variable. For complicated data structures, such as internal tables or structures, select the pushbutton Compare Variables( ) and choose the Diff tool to compare the old and new variable values.
In addition, you have functions for creating, changing, activating and deactivating watchpoints at your disposal.
Checkpoints
In addition, you can edit conditional and unconditional checkpoints using the Breakpoints tool. This function is provided in the new Debugger only. Conditional checkpoints are set first in the source code using the ASSERTstatement; unconditional checkpoints are set using the BREAK-POINT statement. These have the effect that programs will be continued only if a preset condition is fulfilled. In the following window, these checkpoints can be searched for, activated, or deactivated.
Regards,
Renjith Michael.

What is watch point and break points?what are there types?

what is watch point and break points?what are there types?

Static Breakpoints
Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages:
· You do not have to change the program code.
· You can set them even when the program is locked by another programmer.
· You can define a counter that only activates the breakpoint after it has been reached.
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Watch point are used to put logical break point for a certain condition..Example..If you want to know when the internal table is getting append..Then you have to give the program name and the internal table in the watch point..
Steps to create a watch point.
Start debugging '/H'.
In the debugging screen press the create watch point button in the application tool bar..
In the program give the program name..
in the field give the field name.
In the relational operator given '='
In the comp. field/value give the value ..
Hope this helps..
Regards,
Parvez.

How many break points and watchpoints are allowed in ECC 6.0

Hi,
Can any one say how many break points and watchpoints are allowed in ECC 6.0

Hi ,
A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.Max 30 breakpoints we can use.
There is a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change ie...Watchpoints allow you the option of monitoring the content of individual variables.The Debugger stops as soon as the value of the monitored variable changes.You can use max of 5 watchpoints.
Difference
1. Break Point.
At particular LINE of SOURCE CODE,
the system will STOP there.
2. Watch Point.
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
(For this, we have to give some
VARIABLE NAME & VARIABLE VALUE - with relational operator)
When this CONDITION gets satisfied,
(anywhere during the execution of the program),
the system will AUTOMATICALLY STOP THERE.
(EG when the value of matnr reaches the specified value)
That is the purpose of WATCHPOINT
(the system will WATCH it, like a dog)
Please go through this link:
Watchpoint Vs breakpoint
http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm
Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger. Watchpoints allow you the option of monitoring the content of individual variables.
The Debugger stops as soon as the value of the monitored variable changes.
In addition, conditions can be specified. The Debugger also checks whether such a condition is fulfilled.
For more details...
http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cd9e68c11d2b2ab080009b43351/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/f1/792442db42e22ce10000000a1550b0/frameset.htm
If satisfied, rewards me..
Kind Regards
Yogesh

Break Point in Webdynpro JAVA and SAP

Good Morning.
I am creating a development for web dynpro Java using Function Module RFC in ABAP.
I want know how can put a break point in the system SAP ERP (Backend) and run an application in web dynpro java?
I did this steps:
1.) SE37--->name RFC
2) button Display
3) Set/Delete external Break point.
4) In the SAP Netweaver Developer Studio >Name of project>Webdynpro>Applications>Name Appplication-->deploy new archive and run.
But this not stop.
The question is :
How can do this?
Kind Regards

Hi,
Refer this article: [Debugging ABAP Code from within Web Dynpro Application|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/0e9a9d90-0201-0010-478e-991dbea73a30&overridelayout=true].
I hope it helps.
Regards
Arjun

How to debugg and put a break-point in End Routine

Hi all,
Can anybody suggest how to put a break point in Endroutine in BI.7
Thanks
DB

Hi Bhanu,
Please go through these links:
How to debug abap code in update rules...routine?
debug abap routine in infopackage
Debugging of global transfer and update routine
Debugging Start/Transfer routine
And have a look at this demo video to know how to set up break points and how to debug an ABAP program in NW2004s:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9cbb7716-0a01-0010-58b1-a2ddd8361ac0?prtmode=navigate
Hope it helps..
Cheers,
Habeeb

Bitrate and break point problems

Hello All,
I am trying to create a dual layer dvd containing 37 chapters (all average 3 min. a piece) and 2 audio tracks (one with commentary) with DVD studio Pro 3. On my first build, the disc meter was 7.6 GB large. On a dual layer this should fit with no problems, right? The build got to muxing and cancelled saying "the video bitrate is too high". I read somewhere on these posts that this doesn't matter too much if you're planning on burning to Toast, which is what I was going to do. So I tried formatting and I keep getting the "can't find a suitable break point error". I then tried making several of the chapter markers break points but it didn't like any of them and I still keep getting the same error message on formatting. Any help is greatly appreciated!

Carson:
Wellcome to the forum!
High bitrate
First at all, you probably are using AIFF audio (uncompressed). If that's the case encode your audio to Dolby 2.0 (AC·) and you'll get a lower total bitrate and more free space.
You must look for A.Pack app in your applications folder to encode to AC3. You can take a look to this tutorial about Encoding AC3 with A.Pack (from KenStone site).
You didn't mention your MPEG2 encoding settings, did you used any standard Compressor preset?
37 chapters x 3 min means less than 120 minutes. Encoding your audio to AC3 and using the 120 Min Compressor preset will let you fit your project in a DVD5.
Hope it helps !
Alberto

Break points not working on copy and paste

It looks like copy and paste is not a good option between break points, is that right?

Copy and paste (as well as duplicate) should work across breakpoints. When you select something it will copy all the styles in all the breakpoints for just that object. For example if you have a page with two breakpoints you have an object that is different in both of them, then when you copy that object and paste into a new page you should get both breakpoints. However if you have a document with two breakpoints and you have an object that is the same in both of them, then when you copy and paste into a new page you won't get one of the breakpoints because that object didn't need it. If this is not what you are seeing then it could be a bug. To tell for sure you can post more steps and details about what you are trying to do.
Hope that helps and thanks for using Reflow!
Chris

Export data in Excel file - Debug and Break Point

In the program RFUMSV00 the data been displayed on the screen with the function REUSE_ALV_LIST_DISPLAY.
With "Cntrl + Shift + F9" I exported the list of data in an Excel file.
How can I see, with Debug, where the program RFUMSV00 passed the data to Excel File? I can indicate the point, In the program, where I need to set the break point?
Thanks,
Serena

Hi,
This download functionality has nothing to have with program RFUMSV00. It is actually processed by REUSE_ALV_LIST_DISPLAY fm, which calls fm LIST_COMMAND which finally calls fm LIST_DOWNLOAD, where you will actually find the downloading part (in fact in another fm, DOWNLOAD_LIST)...
to resume: REUSE_ALV_LIST_DISPLAY->LIST_COMMAND->LIST_DOWNLOAD->DOWNLOAD_LIST
so I would put the break-point in the last one..
Kr,
Manu.
correction: I made a mistake, the break-point should be set in LIST_DOWNLOAD...where you will find the call to fm LIST_CONVERT_TO_DAT which is responsible of the download...
Edited by: Manu D'Haeyer on Dec 9, 2011 1:46 PM

Reg usage of break point in debug mode

Dear experts,
I want to know how to go to a particular line in debugging mode. Suppose for example, if a program contains main program and includes. I want to go to a particular line in debugging mode in the includes. How can i go? kindly help me.
tks

Hi Prabhakar,
Using break points you can stop the execution control at that break point.
If you use only F5, F6, F7 for debugging you don't need of break points.
But if you want to stop at particular statement while running the report (using F8) you should use Break Point. Ofcourse you can use watchpoints also.
Watchpoint --- If you put watch point execution control stops at the particular statement when the value of watchpoint is reached.
Reward If Helpful.
Regards
Sasidhar Reddy Matli.

Find break-points source code (update rules, transfer rules)

Hi all,
Is there any effective and efficient way to find (active) break-points in source code, more specfic update rules, transfer rules or other objects where custom code is implemented? Or in other words look for strings in source code or programs.
I looked and searched everywhere but could not find any answer.
RSRSCAN1 (does not work)
RPR_ABAP_SOURCE_SCAN (does not exist)
We are on SAP BW 3.5 with SAP Basis 640.
Thanks all.

Hi,
Try this
1) if you're checking any program from SE38 ..goto Utilities -> find in the source code-> give breakpoint and search.
2) else. load data , Goto details tab in the monitor and right click on any of the data packages.
Simulate update -> choose transfer rules or update rules for debuging.-> It will take you debuging screen. -> Create a watch point with key word "break-point" and execute (F8).
It will go and stop where there is "break-point"

DL Break Point - Problem/Question

Recently I've been getting some complaints from my customers that there DVD starts to Pixelize / Break-up on the point the DVD switches layers. Some people even claim the DVD stops all together at the break point.
Not all of the DVD - 9's I sell do this. But it does seem like the complaints have increased.
Is this a problem with my Software (DVDSP 3) or the Replicator im using?
I master all the DVD's on DLT, and than send those to the Replicator. I also chose my own breakpoint.
Could it maybe be the brand of the DVD player having trouble reading the switch? I've asked that they send the problem DVD back to me and it plays fine on my Sony DVD Player.
Anyone else have problems with DVD 9's?
Thanks,
Mike A.

Eric,
You should not be saying that DVD SP is not a good pre-mastering tool, like you're saying here, and have been saying on boards elsewhere over the last period.
It's not true. Actually, the exact opposite is true - tests show DVD Studio Pro has the best pre-mastering formatter on the market; MUCH better than Scenarist and Creator, Encore, and even the vaunted Toshiba DVD Authoring system. And yes, better than even DVDAfterEdit Mastering Edition.
Just run any of the above formatters' DDP output through EclipseSuite 5.0, like I have, and look at all the UDF errors you'll find in all of them - except DVD Studio Pro's output; it's the cleanest.
Maybe what you meant is that ALL authoring systems can hand you your you-know-what in a can, if you don't watch it. That's true.
When I pre-master for a studio running DVD SP, I ALWAYS have the good folks send me a DDP Image on hard drive. And if I'm not adjusting the Image with DVDAfterEdit, I'll format their DVD SP DDP Image straight to tape (after extracting the VIDEO_TS folder for rounds of tests including the DVD Forum's MEI DVD-Video Verifier, and even burn a disc from it for player bank testing).
True, their are at times something wrong with the DVD SP DDP Image that I find with the EclipseSuite; allot of these warnings and errors have to do with project settings (true, some of them shouldn't be there or initially set that way). But if you know what you're doing, and have some guidance when needed (which I provide my clients), then most of the time DVD SP will come through, beautifully.
Since, DVD SP 2.0 when the new Spruce Maestro code set was introduced, things vastly improved. When was that, 4 years ago? Now, I find DVD SP very reliable, with most of the mistakes coming in the authoring and/or how the project was first submitted, before it came to me.
So anyway, please, keep to the facts in the future.
Thanks,
Trai
Trai Forrester
TFDVD Research Labs
<edited by host>

Break points

hai gurus...
how many watch points and break point can be used in each program...
types of watch points and break points....
Thanks
Pavan

Hi
a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
Use
You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
Features
· You can set up to five watchpoints in a program.
See also Setting Watchpoints.
· You can also specify the conditions under which a watchpoint is to become active.
· You can specify a logical link for up to five (conditional) watchpoints.
See also Specifying Logical Links.
· You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in
the specified program.
· You can change and delete watchpoints.
See Changing Watchpoints
· You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.
See Memory Monitoring with Watchpoints
Breakpoints
Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For more information, refer to the chapter Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.
Directly set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statements
The Debugger stops the program immediately before the specified statement is executed.
Breakpoints
at subroutines
The Debugger stops the program immediately before the specified subroutine is called.
Breakpoints at function modules
The Debugger stops the program immediately before the specified function module is called.
Breakpoints at methods
The Debugger stops the program immediately before the specified method is called.
Breakpoints at exceptions and system exceptions
The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages:
· You do not have to change the program code.
· You can set them even when the program is locked by another programmer.
· You can define a counter that only activates the breakpoint after it has been reached.
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
we can keep them at :
Statements
Subroutines
Function Module Calls
at Methods
System Exceptions
break point :
we can start debugging from that point or if we keep break point at some place we can directly got ot htat point using f6.
watch point: for example if we have to check the output for 4000 records based on a field value i.e.for vendor number 'in'we have to check then we will create watchpoint on field LIFNR value '2000'. then we can directly go to vendor whose numbe ris 2000
Regards,
Sree

Break points are not triggering in RFC from portal application

Helllo,
I am running Biller Direct application from portal, which is triggering a standard SAP RFC FM back end, am trying to debug my execution from portal, for this i put the External Break point, Session break-poiint at the beginning of this SAP RFC FM, but, its not stoppping at ll, here the user is a Web user, not dialog user.
How can i stop my execution in this SAP RFC FM to check how the structures are populated?
Thank you

Hi Raju,
Please try the below way and check if it works.
Open the RFC in R/3 i.e.
SE37 -> give FM NAME -> DISPLAY.
Click on UTILITIES -> SETTINGS -> CLICK THE TAB debugging.
In the screen against the field users : give the value 'WEBLOGIN'.
Uncheck the FLAG 'IP MATCHING'.
And at the bottom check the check box against the field
'Session Break Point Activate Immediately'.
Save these settings.
Then go to the line at which you want to debug the code and put an external break point over there.
But, please take care of one thing as we are giving it as a WEBLOGIN, when ever some logs in, it will reach the brteak point and stop there. We have to click F8 to continue. Or else, the portal will be hanged for them.
Thanks & regards,
Y Gautham

Break points and watch points

Similar Messages

Maybe you are looking for